@database 082a7b10-0 @$VER: 1.0 @author "Alessandro Pedretti" @(c) "" @index Main @node "Main" "xFX - Guide" # # # ## ### ##### # ### ####### Release 1.0 ######## # © 1997, Alessandro Pedretti ####### # ######### English documentation by ###### ### # Alessandro Pedretti & Steve Peruzzi ### ### # # # # # # ########################### @{" 1.  Introduction.      " link "Cos'è" 0} ########################### # # # @{" 2.  Requirements.      " link "Requisiti" 0} # # # # # @{" 3.  Installation.      " link "Installazione" 0} # # ### # @{" 4.  Use of xFX.        " link "Utilizzo" 0} ##### # # @{" 5.  Note.              " link "Note" 0} ## ##### @{" 6.  Bugs.              " link "Bugs" 0} # # @{" 7.  Future.            " link "Futuro" 0} # # # ### @{" 8.  Development tools. " link "Strumenti" 0} #### ###### ### ########## @{" 9.  Thanks.            " link "Ringraziamenti" 0} ### ######## # ########### @{" 10. Copyright.         " link "Copyright" 0} ######## ############ # ######### ### ######## ## # ###### #### @{" 11. History            " link "Storia" 0} ### # # # @endnode @node "Cos'è" "1. Introduction" xFX is a program that has some features of an old and very usable utility called DMS. Using some emulators (ShapeShifter, AmiMSX, fMSX, Speculator, etc.), the Author found many disk problems that have been solved with this utility. In other words, xFX is a tool to create disk images (packed or unpacked) from whatever storage medium in order to transfer (modem, E-Mail, etc.) or simply to archive. A little problem is the manipulation of Macintosh HD floppies. xFX is able to use many device drivers that are compatible with trackdisk.device (e.g. mfm.device, scsi.device, fmsdisk.device, ramdrive.device, etc.). This feature is usable to read and write file-disks, and so, to obtain security-only disk copies. This performance is very useful to copy the Mac HD disks, because xFX is much faster then ShapeShifter (with most probability the very slow disk copy operation is a problem of MacOS and not of the wonderful ShapeShifter). All file-disks generated with xFX (included packed files) do not make usage of a proprietary format and thus they can be used with other software without any limit. This feature allows to unpack a file-disk with any utility that fully supports XPK format. @endnode @node "Requisiti" "2. System requirements" - CPU 68000 or better. - Kickstart 2.0 (V37) or better. - XPK libraries (optional). - rexxsyslib.library (optional). - reqtools.library (optional). - Any storage driver, like: floppy driver (3.5" DD, 3.5" HD, 5.25"), hard disk, ZIP, JAZ, floptical, CD-ROM, LS-120, etc. - Correspondent device drivers. xFX allocates dynamically all resources but only when needed. If the file-disk compression is not used, the XPK libraries aren't used (and not opened). If rexxsyslib.library is not installed in your Amiga, the ARexx port is not usable when xFX is running from Workbench. @endnode @node "Installazione" "3. Installation" To install xFX, you can copy manually all files on your hard disk, otherwise you can use the included installer script. @endnode @node "Utilizzo" "4. Use of xFX" At the present time, xFX can be invoked from shell or Workbench (via tooltypes or drag-&-drop). A built-in ARexx port can be used to control xFX from other programs. @{" 4.1 Shell use.         " link "Shell" 0} @{" 4.2 Workbench use.     " link "Workbench" 0} @{" 4.3 Use of ARexx Port. " link "ARexx" 0} @{" 4.4 Hints.             " link "Consigli" 0} @{" 4.5 Error messages.    " link "Errori" 0} @endnode @node "Shell" "4.1 Shell use" Using xFX from the shell is the easiest way (at this time) to let it show all its power. All commands available from a shell, are also available trough ARexx port with identical syntax. Synopsis: xFX COMMAND/A,DEVICE/A,TO/K,FILE,DISKBUF/K,PACK/K,PASSWD/K, START/K/N,END/K/N,MOUNTLIST/K,ADDICON/S,VERIFY/S,NOEJECT/S,QUIET/S You can call the extended-help to have a small command list, this is the output: xFX V1.0 - © 1997, Alessandro Pedretti COMMAND = COPY, READ, WRITE, CHECK, INFO DEVICE = Device name (AmigaDOS or DEVICE.device:UNIT) TO = 2nd device for copy FILE = Input/output file for READ/WRITE commands DISKBUF = Disk buffer path for COPY PACK = Xpk compression for WRITE (SUBLIB.METHOD) PASSWD = Password for Xpk en/decoding START = Start cylinder (default 0) END = End cylinder (default last) MOUNTLIST = Create a mountlist with fmsdisk.device (READ) ADDICON = Add icon to disk image (READ) VERIFY = Verify cylinders during writing operations NOEJECT = Inhibit auto disk ejecting QUIET = Suppress messages * COMMAND: select the xFX run mode. CHECK = surface disk error checker. READ = read a disk and save it into a file (you must specify it). WRITE = Write a file-disk to disk. COPY = Copy a disk. INFO = Display disk geometry. * DEVICE: device name to execute the selected command. You can use the AmigaDOS device name or directly the device driver with unit number. In this case, the correct syntax is: DEVICE_DRIVER:UNIT. The extension ".device" is optional. You can use with identical result: DF0:, trackdisk.device:0, trackdisk:0 * TO: second device name. This option is usable only with two-devices disk copy. In all other cases, this option is ignored. The correct syntax is identical to DEVICE option. * FILE: file name to read or write. This option is only usable with READ and WRITE commands. * DISKBUF: temporary buffer path. When the free memory is too little, this option allows to execute a single device copy. All temporary data are stored in a file buffer instead of memory. * PACK: name of XPK packing and/or encrypting method. This option is only usable with READ command. The correct syntax is: SUBLIBRARY.METHOD SUBLIBRARY is a four-characters algoritm name (e.g. NUKE, MASH, FAST, GZIP, etc) and METHOD is a number (from 0 to 100, default 100) that indicates the method efficency. Examples: xFX READ 0 Ram:MyFileDisk PACK MASH -> alghoritm MASH efficency 100% xFX READ 0 Ram:MyFileDisk PACK FAST.50 -> alghoritm FAST efficency 50% * PASSWD: XPK sublibrary password. During READ or WRITE operations, this parameter allows to specify the en/decrypting password. Not all XPK sublibraries support this password. * START: starting cylinder. It's usable with READ and WRITE commands (default 0). * END: ending cylinder. It's usable with READ and WRITE commands. Default is the last disk cylinder (e.g. for a 3.5" floppy disk driver, default is cylinder 79). * MOUNTLIST: mountlist file name. At the end of file-disk writing operation (READ command), xFX generates a mountlist with source device geometry. Instead of the original device name, the moultlist contains fmsdisk.device. In this way the created file-disk can be simply mounted under AmigaDOS. The file-disk can't be packed. This option can't be used if the source device is specified like a divice driver (e.g. scsi.device:0) and not like a AmigaDOS device (e.g. DH0:), this because the same device driver can control more partitions. * ADDICON: This switch adds an icon with tooltypes to the file-disk generated with READ command. * QUIET: This switch suppresses all messages (except error messages). * VERIFY: This switch turns on the verify option during write to disk operations (WRITE and COPY commands). * NOEJECT: This option inhibits the automatic disk ejection during copy operation. This function is performed by trackdisk.device TD_EJECT command and thus works only with devices that support this command. @{" 3.1.1 Examples " link "Esempi_Shell" 0} @endnode @node "Esempi_Shell" "4.1.1 Shell examples" @{fg shine}> xFX info scsi.device:0@{fg text} displays the hard-disk geometry. @{fg shine}> xFX check mfm:1@{fg text} executes a surface verifing of floppy disk in drive 1 using mfm.device. This disk must be in Ms-Dos-like format (e.g Mac, MSX, ecc). @{fg shine}> xFX read DF0: Ram:MyDisk@{fg text} creates "MyDisk" file-disk in Ram: with the disk image in Amiga format (trackdisk.device) not packed/encrypted. The source disk is inserted into the drive 0. @{fg shine}> xFX read DF0: Ram:MyDisk MOUNTLIST Ram:FF0@{fg text} As upper, plus mountlist generation. @{fg shine}> xFX read PS2: Ram:MyDisk PACK MASH START 20 ADDICON@{fg text} creates a file-disk called "MyDisk" in Ram: from cylinder 20 to 79, using "MASH" compression with 100% efficency and adds an icon. @{fg shine}> xFX write mfm.device:1 Ram:MyDisk START 10 END 20 VERIFY@{fg text} writes (with verify) the disk-image of "MyDisk" file starting from cylinder 20 to 79. If the source file size is uncompatible with the selected cylinder number, an error is displayed. The unpacking is automatically performed with crunched files. @{fg shine}> xFX copy mfm.device:2@{fg text} executes a copy of disk inserted into the drive 2, using the ram buffer. @{fg shine}> xFX copy DF0: TO trackdisk.device:1 VERIFY@{fg text} copies (cylinder by cylinder) form unit 0 to 1 with verify. In this way, the required ram amount is very small. @{fg shine}> xFX copy DEVICE scsi.device:3 DISKBUF DH0:@{fg text} copies the entire disk from scsi.device unit 3 (removible media like ZIP) with temporary buffer in DH0: @endnode @node "Workbench" "4.2 Workbench use" At this time, the xFX graphic user interface is not available, but with some limitations , the use of this program is possible under Workbench. This feature is not available if reqtools.library is not installed in your system. xFX can be used under Workbench in two ways: (1) trough tooltypes and (2) AppIcon drag & drop. @{fg shine}3.2.1 ToolTypes.@{fg text} In this way, a file-disk can be simply restored into the original support. A double click on file-disk project icon (that can be automatically added by xFX) can start the xFX write process. This icon must have xFX as default tool. The tooltypes actually usable are: Non optional tool types: COMMAND -> Name of command to execute. At this time, the only supported command is WRITE, that restores a file-disk to the original storage medium. DEVICE -> Name of device to use. For the correct syntax into @{"Shell use" link "Shell" 42} section. If the device name is omitted or a question mark ("?") is placed instead of it, the reqtools device requester is opened in order to simplify the selection. Optional tool types: START -> Starting cylinder (default is 0). END -> Ending cylinder (default is the last and is dependent on the output device). GEOMETRY -> It's a group of five values separated with one or more spaces: total sectors, size of each sector, sectors per cylinder, number of heads (surfaces). These informations are used from xFX to check if the file-disk is compatible with selected output device. If this tooltype is not set, xFX use another way (but less reliable). VERIFY -> Executes a verify during write operations. NOEJECT -> Disables automatic disk ejection (if it's possible). QUIET -> xFX runs quiet displaing only error messages. @{fg shine}3.2.2 Drag & Drop.@{fg text} When xFX is running under Workbench (double click on icon), an AppIcon appears. If a file-disk is dragged on this icon, this is automatically used to regenerate the starting disk. To quit xFX, you can use the "Kill xFX" item into the tools menu. In another way, you can double click on xFX AppIcon. A file requester asks you confirm to proceed with this operation. All read and write operations are graphically displayed in a window containing the "Abort" button. If this gadget is pressed or you type ESC or "A" (upper or lower case) on your keyboard, all operations are stopped. @endnode @node "ARexx" "4.3 ARexx port use" If in your system is installed rexxsyslib.library and xFX is running under Workbench (double click on icon), an ARexx port called "xFX.N" is created. N is a progressive number that is used to avoid the duplication of name port if two or more xFX copies are running at same time. Usually, if only one xFX copy is running, the port name is "xFX.1". Each command sent trough ARexx port, sets correctly the return code (RC ARexx variable), the RESULT variable for the return value and a special variable called XFX.LASTERROR with the error message that can be generated during xFX run. The supported ARexx commands are: NOVIEWERR -> Disables the displaying of error requesters, but all er- rors are still reported in XFX.LASTERROR variable. QUIT -> Exits from xFX. REQERR "TEXT" -> Displays a text in an error requester. VERSION -> Returns the current xFX version in RESULT. VIEWERR -> Activates the displaying of all errors (default mode). Other commands follow the same syntax of shell ones: > info "DF0:" > read "diskspare.device:0" "MyDisk.dsk" pack SHRI NOEJECT @endnode @node "Consigli" "4.4 Hints" @{fg shine}3.4.1 Packing method choice.@{fg text} The packing method choice can be very important to obtain much compact filedisk and to waste a minimal amount of time to process a disk. A very good and fast algoritm is MASH. With slower Amigas, NUKE is sufficient for most applications but the efficency is not the same of MASH. The best compression ratio (but with slow speed) can be obtained with SHRI and can be used to transfer disk images with a modem. This packing method is very useful with MSX disk, because can reduce a 720 Kb disk in 160-230 Kb file. @{fg shine}3.4.2 xFX and ShapeShifter.@{fg text} The performances that xFX offers to ShapeShifter users, are very useful: HD disk copy, conversion of a disk into a file-disk for direct use with the emulator and the conversion of a entire ShapeShifter device-disk into a file-disk. This last possibility is very interesting, because it allows to create a Mac file-disk (e.g. to insert in a CD-ROM). Trough Consultron's mro.device, it's possible to convert 800 Kb A-Max disks into file-disks for ShapeShifter direct use. Sometimes, using a xFX file-disk, ShapeShifter does not recognize it immediately and asks for format. If you won't allow this operation, ShapeShifter will rebuild automatically the desktop and the file-disk icon will appear. @{fg shine}3.4.3 xFX and fMSX.@{fg text} xFX can be used to archive MSX disks in simply way using mfm.device. The XPK SHRI packing method allow to obtain the best compression ratio. File-disks, created with xFX, can be directly used with fMSX. @endnode @node "Errori" "4.5 Error messages" xFX can returns all error messages in three different ways: Shell error messages (if it does run under shell), reqtools message requesters (if does run under Workbench) and "XFX.LASTERROR" ARexx variable. Here we report, alphabetically ordered, all possible error messages: @{fg shine}* Aborted.@{fg text} It's not a real error message. It allows to inform the user that xFX run is aborted (e.g. CTRL+C). @{fg shine}* Can't add icon@{fg text} It's not possible to add the file-disk icon , when the ADDICON option is selected. A disk access problem can generate this error. @{fg shine}* Can't allocate crunch/decrunch buffer !@{fg text} The crunch/decrunch allocation failed, because your system has not enough free memory. @{fg shine}* Can't allocate device requester@{fg text} Reqtools.library is not able to allocate the file requester. Maybe the memory run out. @{fg shine}* Can't create AppIcon@{fg text} During Workbench run, xFX can't add the AppIcon. With most probability, your chip memory run out. @{fg shine}* Can't create ARexx port@{fg text} The program can't create the ARexx port. Maybe your memory run out. @{fg shine}* Can't create MenuItem@{fg text} During Workbench run, xFX can't add items to tools menu. @{fg shine}* Can't create mountlist@{fg text} It's not possible to create the mountlist (MOUNTLIST option), because xFX can't recognize the file system of selected device driver. Usually this problem appers when you access directly a device driver. To solve this problem, you can use the correspondent AmigaDOS device, @{fg shine}* Can't find disk object@{fg text} It's not possible to find the disk object selected with drag & drop on AppIcon. @{fg shine}* Can't open DEVICE unit N@{fg text} The device DECICE unit N can't be opened, because the device is temporarily busy and allocated by another program, or simply it's not installed in your computer. @{fg shine}* Can't open progress window@{fg text} It's not possible to open the progress window. @{fg shine}* Can't read drive geometry@{fg text} The selected device driver does not respond to TD_GETGEOMETRY command. This problem can be bypassed using the correspondent AmigaDOS device. @{fg shine}* Can't use an assign@{fg text} Instead of a normal AmigaDOS device, you have used an assignment. @{fg shine}* Command COMMAND require option OPTION@{fg text} The specified command (COMMAND) requires the option OPTION. @{fg shine}* Device name too long@{fg text} The size of specified device (DEVICE and TO options) is too long. @{fg shine}* Disk buffer full@{fg text} On your disk, there is not enough free space to create the buffer. @{fg shine}* Disk buffer not usable@{fg text} The disk buffer is not usable. With most probability, the specified disk is write protected. @{fg shine}* Disk buffer path too long@{fg text} The disk buffer path is too complex (long). @{fg shine}* Disk has errors !@{fg text} This message remembers only that the processed disk has read or write errors. @{fg shine}* Disk write protected in DEVICE unit N@{fg text} The disk inserted into DEVICE unit N, can't be used, because it's write protected. @{fg shine}* DOS Error: XXX@{fg text} It's a dos error message. For more informations, plese consult AmigaDOS manual. @{fg shine}* File too large@{fg text} The selected file-disk can't be used with WRITE command, because the size is not compatible with geometry of destination device. @{fg shine}* File too short@{fg text} The selected file-disk can't be used with WRITE command, because the size is not compatible with selected range of cylinders (START and END options). @{fg shine}* Illegal character in PACK option@{fg text} You have used an illegal character to specify the efficency of packing method. @{fg shine}* Illegal combination of START/END cylinders@{fg text} The starting cylinder is upper to ending. @{fg shine}* Illegal command@{fg text} Unknown command (COMMAND option). @{fg shine}* Illegal device name@{fg text} The selected device is uncompatible with xFX device syntax. @{fg shine}* Illegal ending cylinder@{fg text} You have specified the END option with a cylinder number greater than top cylinder or lower than zero. @{fg shine}* Illegal pack method@{fg text} The packing efficency is not in 0-100 range. @{fg shine}* Illegal starting cylinder@{fg text} You have specified the START option with a cylinder number greater than top cylinder or lower than zero. @{fg shine}* Illegal unit number@{fg text} You have used a not valid unit number. @{fg shine}* Incompatible options TO and DISKBUF@{fg text} The two-devices disk copy is not compatible with disk buffer. @{fg shine}* IORequest not allocated@{fg text} It's not possible to allocate IORequest. Maybe the memory is not enough. @{fg shine}* KickStart 2.04+ needed !@{fg text} Your system is not compatible with xFX. @{fg shine}* LIBNAME.library VXX.XX or higher needed !@{fg text} xFX can't open the LIBNAME library with specified version. Maybe, the library is not installed in your system. @{fg shine}* Memory fragmentation is too high !@{fg text} The memory fragmentation is too high to make a single-swap copy. You can reset your Amiga, or use the disk buffer. @{fg shine}* MsgPort not allocated@{fg text} xFX can't allocate MsgPort. Maybe the memory is full. @{fg shine}* No device selected@{fg text} You don't have specified the DEVICE tooltype. @{fg shine}* No disk in DEVICE unit N !@{fg text} No disk is present in device DIVICE unit N. @{fg shine}* Not enough disk space for buffer@{fg text} Your disk space is not sufficient for disk buffer (DISKBUF option). @{fg shine}* Not enough memory for single swap copy@{fg text} The single swap copy can't be performed, because your system memory in not enough. You can use disk buffer, or a second device (TO option). @{fg shine}* Only WRITE command is supported through Tool Types@{fg text} Instead of WRITE, you have used another command via tooltypes. @{fg shine}* Option OPTION ignored@{fg text} You have specified a option (OPTION) that is not used by command. This option is ignored. @{fg shine}* Out of chip memory !@{fg text} The chip memory is not enough. @{fg shine}* Read error at cylinder N@{fg text} During read operation, the cylinder N reports an error. @{fg shine}* Screen too small@{fg text} The progress window can'be opened, because the screen is too small. @{fg shine}* Selected device is not a disk or is not mounted@{fg text} The selected device does not correspond to device disk, or it is not mounted. @{fg shine}* SOURCE and DESTINATION are not compatible !@{fg text} The source and destination disks have uncompatible geometry. @{fg shine}* SOURCE and DESTINATION are the same device and unit@{fg text} The source and destination are the same device (COPY command). @{fg shine} * Specify the input file-disk@{fg text} With WRITE command, you need specify the input file. @{fg shine}* Specify the output file@{fg text} With READ command, you need specify the output file. @{fg shine}* Too many objects !@{fg text} You have dragged more the one object on xFX AppIcon. xFX supports only one object at a time. @{fg shine}* Tool type COMMAND required@{fg text} You need COMMAND tooltype. @{fg shine}* Verify error at cylinder N@{fg text} xFX has found a verify error at Nth. cylinder. @{fg shine}* Write error at cylinder N@{fg text} xFX has found a write error at Nth. cylinder. @{fg shine}* XPK Error: XXX@{fg text} It's a XPK library error. Check the XPK documentation. @endnode @node "Note" "5. Note" @{fg shine}4.1 General notes.@{fg text} - xFX does not need a large memory segment to allocate the copy-disk buffer. Thus, it have not problems to run even if memory fragmentation is very high. - xFX works correctly with this tested devices: trackdisk.device, mfm.device, ramdrive.device, fmsdisk.device, scsi.device, atapi.device (Oliver Kastl), diskspare.device, mro.device (anche con disco A-Max), floppy.device 4.1 (Orhan Dagistanli), icddiskide.device. - When any device receives the TD_GETGEOMETRY command, raher than giving a negative answer, crashes the system (this is not a xFX bug), because does not support this command. A little list of these devices: fmsdisk.device, multios.device (Jim Drew). This problem is solved mounting the correspondent AmigaDOS device and using that with xFX. In this way, xFX does not use the trackdisk.device command TD_GETGEOMETRY, but uses the DosList. - Atapi.device (Oliver Kastl) and icddiskide.device don't support TD_GETGEOMETRY (without crashing the system). To use these devices, you can mount and use the correspondent AmigaDOS devices. - xFX is capable to recognize the AmigaDOS device without file system (e.g. SER:, PAR:, etc), but this is not true for device drivers. If you call xFX with SER:, the program displays an error, but if you call xFX with serial.device:0, your Amiga crashes ! @{fg shine}4.2 Floppy disk formats.@{fg text} Computer = computer name. Format = format name. Drv = size of disk (inches). Dsk = disk type SS = single side single density. SD = single side double density. DS = double side single density. DD = double side double density. HD = high density. Size = size in Kbytes. Sec = total number of sectros. SecSize = size of each sector (bytes). TotCyl = total number of cylinders cilindri. SecCyl = number of sectors by cylinder. Surf = number of sides. Dev = device driver for xFX use: 1 = trackdisk.device 2 = diskspare.device 3 = floppy.device 4 = mfm.device 5 = mro.device ======================================================================= Computer Format Drv Dsk Size Sec SecSize TotCyl SecCyl Surf Dev ======================================================================= Amiga trackdisk 3.5 DD 880 1760 512 80 22 2 1 Amiga diskspare 3.5 DD 984 1968 512 82 24 2 2 Amiga floppy 3.5 DD 1148 2296 512 82 28 2 3 Amiga trackdisk 3.5 HD 1760 3520 512 80 44 2 1 Amiga diskspare 3.5 HD 1968 3963 512 82 48 2 2 Amiga floppy 3.5 HD 2050 4100 512 82 50 2 3 Atari ST 3.5 SD 360 720 512 80 9 1 4 Atari ST 3.5 DD 720 1440 512 80 18 2 4 C= 1541 5.25 SS 171 683 256 35 17-21 1 - C= 1571 5.25 DS 342 1366 256 35 17-21 2 - Macintosh 3.5 DD 800 1600 512 80 20 2 5 Macintosh 3.5 HD 1440 2880 512 80 36 2 4 Ms-Dos 5.25 SD 160 320 512 40 8 1 4 Ms-Dos 5.25 SD 180 160 512 40 9 1 4 Ms-Dos 5.25 DD 320 640 512 40 16 2 4 Ms-Dos 5.25 DD 360 720 512 40 18 2 4 Ms-Dos 3.5 SD 360 720 512 80 9 1 4 Ms-Dos 2.5 DD 720 1440 512 80 18 2 4 Ms-Dos 3.5 DD 720 1440 512 80 18 2 4 Ms-Dos 5.25 HD ? ? 512 ? ? 2 4 Ms-Dos 3.5 HD 1440 2880 512 80 36 2 4 Ms-Dos 3.5 ED 2880 5760 512 80 72 2 4 MSX 3.5 SD 360 720 512 80 9 1 4 MSX 3.5 DD 720 1440 512 80 18 2 4 Spectrum 3.5 SD 400 800 512 80 10 1 4 Spectrum 3.5 DD 800 1600 512 80 20 2 4 ======================================================================= @endnode @node "Bugs" "6. Bugs" xFX is a very young software and, with most probability, contains some little bugs. For suggestions, questions and bug reports, please you refer to the @{"Author address." link "Copyright" 0} @endnode @node "Futuro" "7. Future" - @{"Graphic user interface" system "SYS:Utilities/Multiview GuiX_Preview"} trough ARexx port (MUI). - Support of single sided disks. - GZip like packing method (LZ77) for Unix users (Uae !??!). - PowerPacker support. - File-disk multi-split. - Localizzation. - SCSI-Direct support. - Use of iec.library for drive C= 1541 compatibility with creations of file-disks in raw and .d64 format. - Direct access to 5.25 inches floppy driver to read C= 64 floppy disks. @endnode @node "Strumenti" "8. Development tools" @{fg shine}- Development hardware:@{fg text} A1200 030/882 @50 MHz, 16 Mb Fast Ram, HD 1080 Mb, CD-ROM 4x, Kick 3.0 @{fg shine} - Hardware for beta-testing:@{fg text} A4000 040 @25 MHz, 16 Mb Fast Ram, CV 64, HD 3.2 Gb, CD-ROM, Kick 3.0 A3000 030/882 @25 MHz, 2 Mb Chip/12 Mb Fast, Merlin, HD 2 Gb, Kick 3.1 A500 512Kb Chip/1.8Mb Fast, HD 20 Mb, Kick 2.04 @{fg shine}- Software:@{fg text} Gcc V2.7.2, Libnix, CygnusEd II, GoldED 4, XPK User & Developer Archive, Enforcer V37, MungWall. @endnode @node "Ringraziamenti" "9. Thanks" - Carolyn Scheppner (Sushi). - Christian Bauer (ShapeShifter & Frodo). - Dave Jones & Matt Dillon (fmsdisk.device). - Dietmar Eiler (GoldEd). - Dirk Stöcker, Bryan Ford, Urban Dominik Müller, Christian von Roques & Co. (Librerie XPK). - Fred Fish and your collaborators (ADE). - Free Software Foundation (packages GNU). - Jaun Antº Gómez (AmiMSX, AmiMasterGear, AmiGameBoy). - Klaus Deppisch (DiskSpareDevice). - Marat Fayzullin & Hans Guijt (fMSX). - Michael Sinz (Enforcer). - Michiel Plet (Professional File System). - Nico François & Mangus Holmgren (reqtools.library). - Oliver Kastl (IDEFix & atapi.device). - Roman Patzner (icons). - William James (Speculator). Special thanks to all my beta testers (Steve Peruzzi & Andrea Orsucci) and to all my friends. At last but not least, I want to thank all people (and are very much) that have contributed to make Amiga so wonderful. All people unitentionally not thanked in this document, please don't offend. @endnode @node "Copyright" "10. Copyright" All trademarks and softwares directly or indirectly referred in this document, are copyrighted from legal owners. xFX is a program freeware and can be spreaded trough Internet, BBS, CD-ROM and each other electronic form. The Author of this program accepts no responsabilty for hardware/software damages resulting from the use of this package. xFX is a software developed in 1997 by Alessandro Pedretti All rights reserved. Alessandro Pedretti via Enrico Mattei 16/D 20018 Sedriano (MI) - Italia Tel. +39-2-90110528 Fax. +39-2-90110528 1st E-Mail: apedretti@mbox.est.it 2nd E-Mail: alex@indigo.farma.unimi.it @endnode @node "Storia" "11. History" @{fg shine}0.10 (internal):@{fg text} - First release. @{fg shine}0.11 (internal):@{fg text} - Solved the access inhibition problem when device in use. - Now the ARexx error messages are reported correctly. - The device unit number is not more limited to 10. - Added the IDCMP DISKINSERTED message to notify the disk swap. @{fg shine}1.0 (first public release):@{fg text} - AmigaGuide® documentation. - Installer. - ARexx examples. - Removed a little bug concerning to two drive copy. - Added automatic stack checker. @endnode