@DATABASE dms.guide @INDEX Index *1************************************************************************** @NODE MAIN @TITLE "Device-Masher System Documentation" DATE: 14.4.1994 Device-Masher System v2 By ParCon Software Table of contents: @{" About DMS " link DMSgeneral} @{" DMS NEWS! " link DMSnews} @{" DMS commands " link DMScommand} @{" DMS options " link DMSoption} @{" FMS options " link FMSoption} @{" Copyright " link Copyright}@{" Credits " link Credits} *************************************************************************** * * * Device-Masher System * * * * DEVELOPED on the Amiga, FOR THE AMIGA AND used on the AMIGA ONLY!. * * * * It's all about making the right choice, so when YOU have to choose. * * * * CHOOSE D M S . * * * *************************************************************************** +-----------------------------------------------------------+ | "There can be, only one!" said the student. | | The Master just looked back at him with a sad expression. | +-----------------------------------------------------------+ @ENDNODE *2************************************************************************** *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE DMSgeneral @TITLE "About dms" The story. DMS was originally written by SDS software and first release was made in 1991. Shortly after the release of DMS, WARP was quickly replaced by DMS, because of its advantage in compression and speed. Since DMS version v1.11, users have not seen any updates from SDS software. Registered users which got their v1.11 never got anything else. From different sources, We were told, that SDS software never replied to bug reports nor updates. We find that SDS software was ignoring all mail because the programmer didn't want to continue his work, or simply started working on another platform. We at ParCon software saw our chance to make DMS more powerful and make the nessesary changes which were needed to keep up with the operating systems made for Amiga, and try to pleeze those people who tried to notify SDS about problems with dms. In 1993, DMS v1.51 was released through a source which was quite famous and working in group which was known for releasing powerful products. This early release version was made to test users ability to change from using the old dms v1.11 and upgrade to the new v1.51 . Soon after followed the v1.53 still released through this source. DMS got well received by the users all over the world, and We decided to follow up on the development of dms, and created the company "ParCon software" . We rewrote most routines in DMS, except for the compression algorithms which is very complex and efficient, and made dms perform better on disks which were unrecognized since the release of Kickstart 2.x. Several changes in DMS have made it possible for the user to compress different kinds of devices, such as highdensity and pc disks. Registered users of the old dms v1.11, will once again have to register to get their updated version. As DMS v1.11 and DMS v2.x got only one thing in common, that is the compability of compressing and decompressing of DMS images. We have not ripped dms from the authors, they gave up in 1991. The Device-Masher System is made very similar to the old dms v1.11 because users have a hard time changing from one program to another, if the old one still works fine. And those who wished to use the new version had no problems installing their dms v2.x in their regular scripts, etc. The register fee you must pay is because we feel, that all the work and effort we have put in development of this updated/rewritten dms have taken us a lot of time. Commercial products are often much more expensive. So we urge you to register your dms, so we can continue the work, with our registered users in mind, so We feel that all our work hasn't been for nothing . Other Products. ParCon Software is also developing a few other products . If you have ideas for programs you would like see written, contact us at the address shown in chapter 10. . @ENDNODE *2************************************************************************** *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE Credits @TITLE "Credits" MACIEJ MARZEC, Doing the endless testing of DMS, Supply of new ideas for improvements of DMS. PETER NIELSEN, Making the new ANSI layout for DMSTEST v1.32 KENNETH PERTO, Testing the PC functions in DMS... NICHOLAS CLARKE, (Co-writer of ParCon programs) Making the WINDOW INTERFACE for DMSWB ... ERIK LØVENDAHL SØRENSEN, (SAFE HEX INTERNATIONAL) For supply of needed material to make the virus checker, in DMS v2.x ERNEST OTTE, Informing us about the UNRELEASED MEMORY when exiting DMSWB. @ENDNODE *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE Copyright @TITLE "Copyright" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ COPYRIGHTS AND PUBLIC DOMAIN NOTICE: ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ ~ ~Device Master System(DMS) is a Copyrighted material. ~ ~ ~ ~DMS is copyrighted by ParCon Software and is available as shareware. ~ ~DMS is freely distributable provided the following rules: ~ ~ ~ ~ 1. No charge excepting reasonable media costs may be charged. ~ ~ ~ ~ 2. The program and documentation may not be modified in any way. ~ ~ ~ ~ 3. The program package have all the files, as described in ~ ~ the CONTENTS.DOC . ~ ~ ~ ~ParCon Software will be in no way liable for damages, incidental or ~ ~consequential, arising from the use or misuse of The Device-Masher, ~ ~or for any claim by any other party. Use this program at your own ~ ~ risk. No warranty is given either expressed or implied. Terms of ~ ~ registration are subject to change without notice. ~ ~ ~ ~ ~ ~ ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ ~ @{" Evaluation limitations " link Copyright2} ~ ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~This version of DMS is released as shareware, and is limited for some ~ ~options. A full version is available to registered users. ~ ~The registered version features: ~ ~ ~ ~ ~ ~ A new version of DMS which can pack disks %40 faster. ~ ~ And got special options related to the DMS.DEVICE, which makes ~ ~ them run at high-speed, like a normal diskdrive. ~ ~ ~ ~ A full version of DMS WINDOW which is %40 faster in packing, ~ ~ compared to previous DMSWIN versions. ~ ~ ~ ~ Other utilities made by ParCon Software. ~ ~ ~ ~ ParCon Software will send you the lastest updated version, for free. ~ ~ and you will receive another update, if made, for free. ~ ~ If you want us to continue sending you updated versions, or ~ ~ new programs made by us, you must add $5 to the registration fee, ~ ~ for each package extra you want to receive. ~ ~ ~ READ THE @{"REGISTER" link DMSregister} DOCUMENTATION FOR MORE INFORMATION ON REGISTER ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @ENDNODE *2************************************************************************** @{"REGISTER" link DMSregister} *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE Copyright2 @TITLE "Evaluation Limitations" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ Evaluation limitations in DMS ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In the Evaluation version, you have limited access to the some of the options in DMS. @{" Device-Masher System (DMS) " link DMS1} @{" File-Masher System (FMS) " link FMS1} @{" How do I get a FULL version " link DMSregister} @ENDNODE *2************************************************************************* *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE DMS1 @TITLE "DMS Limitations" 1: DMS will run at aprox. 40% slower speed, when compressing disks. 2: DMS cannot make the High-Speed '.DMS' files, using the "DEVFIX" option. @ENDNODE *2************************************************************************ *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE FMS1 @TITLE "FMS Limitations" 1: files larger than 66 kilobytes cannot be packed with the evaluation version. 2: you will only be able to pack one directory at a time, if this directory contains subdirectories, FMS will skip this subdirectory. @ENDNODE *2*********************************************************************** *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE DMSnews @TITLE "DMS NEWS!" DMS NEWS REGION @{" UPDATE Info on DMS/DMSWB (NEWEST VERSION ONLY) " link DMSUPDATE} @{" File-Masher System (FMS) " link FMS} @{" File-Masher System WBench (DMS WB) " link DMSWB} @{" DMS.DEVICE " link DMSDEVICE} @{" UnDMS " link UNDMS} @{" SFXDMS " link SFXDMS} @{" Device-Masher Backup " link DMB} @ENDNODE *2*********************************************************************** @NODE DMSDEVICE @TITLE "DMSDEVICE" The device driver which can be found in the DEVS: directory on this disk is for the mounting of a virtual drive. But not as you normally would expect. Unlike FFx: FMx: , DMS-DEVICE is for mounting DMS files, and accessing files included in the archive without having to extract it. So the main difference between FMx/FFx and our DMx: device, is that FMS.device and FFx.device takes up 901120 bytes pr. disk, And DMS.device only uses the same space which your DMS file does. @ENDNODE @NODE SFXDMS @TITLE "SFXDMS" SFXDMS is a part of DMS, which gives you the option of creating executable DMS files, which can be extracted without the need of the DMS program. The executable file will only occupy memory for the main program. Data will be loaded in one track at a time, and depacked. The new option in DMS for this, is SFX. Read more about this later in this documentation. ADVANTAGE: *SIMPLE PATCH FILES WHICH WILL UNPACK WITHOUT NEED OF DMS. @ENDNODE @NODE UNDMS @TITLE "UNDMS" UNdms can only unpack DMS files. The main reason for making this tool is for those who need to include DMS archives on their disk. But because of the minimizing of the filesize, boottracks will not be tested for viruses nor shown. UNdms works with all the supplied options as in the FULL DMS. but unlike DMS, UNdms will not use verification of data written to disk as default. you must use the "VERIFY" option for verification. ADVANTAGES: *MORE SPACE ON THE DISKS WHERE DMS, IS A PART OF THE TOOLS WHICH IS NEEDED TO EXTRACT PATCHES ETC. *SIMPLY MORE SPACE ON YOUR MODEM-DISK, IF YOU ARE A DISK USER @ENDNODE @NODE DMSUPDATE @TITLE "Device-Masher System v2" BUGS: *BUGS IN DMSWB* 1. DMSWB DID NOT DEALLOCATE OCCUPIED MEMORY WHEN THE PROGRAM WAS ENDED. 2. SAVING OF PREFS WAS DISABLED, THIS OPTION IS NOW ENABLED. 3. PROCESSES 2-4 DID NOT WRITE PROBERLY, BECAUSE THEIR TASK-PRIORITY WAS SET TO -1, THEIR PRIORITY IS NOW 0. *BUGS IN DMS* 1. WHEN THE CTRL-C OPTION WAS ADDED, DMS DID NOT WORK WITH ">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE FMS @TITLE "File-Masher System" File-Masher System Version 2.01 DOCUMENTATION FMS is a part of DMS, which allows the user to pack files and include those files to the .DMS file. DMS and FMS, a 2-in-one file packing utility. FMS is file compressor for data or executable files. its nothing new that LhA, already did quite a job on that. DMS shows that it can compete with LhA in file packing, and combining both Diskimages and files in one single file makes it even more powerful. FMS will detect DMS images(tracks) and tell you its here, if found. and DMS will do the same when unpacking tracks. When packing whole directories, FMS is very simple to use for that. Specify directory for packing, and the directory + subdirectories will be packed without doing anything, but specifying the directory. @ENDNODE *2*********************************************************************** *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE DMB @TITLE "Device-Masher Backup" Device-Masher Backup is basically a Harddrive backup system, which is able to pack the files with the mode used by DMS. DMB will also be able to function without packing mode, but generally its made for the purpose of saving disks when making a backup. @ENDNODE *2*********************************************************************** *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE DMScommand @TITLE "DMS commands" Commands for DMS @{" READ " link DMS_READ} @{" WRITE " link DMS_WRITE} @{" APPEND " link DMS_APPEND} @{" REPACK " link DMS_REPACK} @{" VIEW " link DMS_VIEW} @{" TEST " link DMS_TEST} @{" TEXT " link DMS_TEXT} @{" VIEWDIZ " link DMS_VIEWDIZ} @{" SFX " link DMS_SFX} @ENDNODE @NODE DMS_SFX @TITLE "DMS option: SFX" You can make your .DMS file executable, by using this command. The DMS file executable file, have all the options which can be used with the normal DMS, the only difference is that you do not need the DMS program to unpack the file with when you have made the .DMS file executable. The .DMS filesize will only be 17K larger, when the executable hunk is added to the .DMS file, which is not much. so if you need the .DMS file and the DMS program together on one disk, you can simply make the .DMS file executable and put it on the disk. The SFX file may look like it needs a lot of memory to be executed, but it will only allocate around 150K. The DMS DATA, will be loaded into memory when needed. So don't let yourself get scared when you have an executable file of 850K. *example: DMS SFX .DMS @ENDNODE @NODE DMS_READ @TITLE "DMS option: READ" This command will read and compress a disk. The basic usage for this command is: DMS Read file[.DMS] [FROM Dev:] [PC] [HD] [TEXT filetext] [DIZTEXT filetext] [CMODE mode] [LOW lowtrack] [HIGH hightrack] [ENCRYPT password] [NOVAL] [NOZERO] [RETRY value] [DEVFIX] Where file[.DMS] - is the output file which will contain the archived disk. The output file can be either a previously written FMS file, or you can append tracks to an existing DMS archive. READ EXAMPLES ------------- DMS READ myfile - compress a disk inserted in DF0: and save the data as MYFILE.dms. DMS READ myfile FROM df1: TEXT mytext LOW 0 HIGH 79 - compress a disk inserted in DF1: and save the compressed data as MYFILE.dms, include a text called MYTEXT and read tracks 0 to 79. DMS READ myfile FROM PC1: PC HD LOW 0 HIGH 79 CMODE NONE - compress a PC disk inserted in PC1: and save the data as MYFILE.dms, read tracks 0 to 79, and do not compress the data. @ENDNODE @NODE DMS_WRITE @TITLE "DMS option: WRITE" This command will write an archive to a device. The basic usage for this command is: DMS Write file[.DMS],,, [PC] [HD] [TO Dev:] [LOW lowtrack] [HIGH hightrack] [DECRYPT password] [NOVAL] [NOVERIFY] [NOTEXT] [NOPAUSE] [RETRY value] Where - file[.DMS] can be an DMS archive. Multiply files can be written at one time. WRITE EXAMPLES -------------- DMS WRITE myfile - decompress myfile.dms to a disk in DF0: DMS WRITE myfile TO df1: NOVERIFY NOTEXT - decompress myfile.dms to a disk in DF1: , do not verify the datas written, ignore text files added to this archive and leave out printing of the boottrack. DMS WRITE myfile TO pc1: PC DECRYPT ParCon_Software - decompress myfile.dms to a disk in PC1: , write data in PC disk format, and decrypt the archive with the password Parcon_Software. @ENDNODE @NODE DMS_REPACK @TITLE "DMS option: REPACK" This command will repack a previously compressed archive. The basic usage for this command is: DMS Repack file[.DMS] [TO file] [LOW lowtrack] [HIGH hightrack] [CMODE mode] [NOTEXT] REPACK EXAMPLES --------------- DMS REPACK stuff LOW 20 HIGH 40 CMODE none - Will extract tracks 20 through 40 from the archive stuff.DMS , recompress them using no compression and store the results in the file TEMP.DMS . DMS REPACK old TO new - Will recompress the archive old.DMS using the default compression mode and store the results in the file new.DMS @ENDNODE @NODE DMS_TEST @TITLE "DMS option: TEST" Test integrity of archive. DMS makes a basic CRC check of the archive. DMS will not report errors which is case of bad compression. The basic usage for this command is: DMS Test file[.DMS] @ENDNODE @NODE DMS_TEXT @TITLE "DMS option: TEXT" Show the text header which is added to a archive. DMS will show the first text information added to the archive. The basic usage for this command is: DMS Text file[.DMS] @ENDNODE @NODE DMS_APPEND @TITLE "DMS option: APPEND" (OPERATION OPTION) :> MUST BE WRITTEN DIRECTLY AFTER THE "DMS" command name. Sometimes you need to pack multiply track, ex. 2 and 5. and the tracks is not followed by eachother, normally you would pack two or more files to do it.... and join them into a .LhA archive. That is not nessessary anymore DMS can APPEND a single track to your DMS file.. and makes it easier for you to join single tracks into one DMS file. The APPEND option supports all other available suboptions, like TEXT,NOZERO e.t.c.. *example: DMS APPEND .DMS LOW HIGH @ENDNODE @NODE DMS_VIEW @TITLE "DMS option: VIEW" View information in archive. You can view information about the archive and the computer it was compressed on. The basic usage for this command is: DMS View file[.DMS] [FULL] EXAMPLE OUTPUT OF A DMS FILE ---------------------------- File: myfile.DMS Size: 823928 Created: Thu Apr 07 10:33:03 1994 Lowtrack in Archive: 00 Hightrack in Archive: 79 Packed Bytes: 802486 UnPacked Bytes: 901120 Kickstart Version used : 39.106 AGA Machine Used: AMIGA Machine CPU: 68020 CPU Coprocessor: 68881 Time to Create Archive: 1 mins. 1 secs. Version Number of Creator: 2.03 Version Needed to Extract: 1.11 Disktype of Archive: AMIGA OS 1.0 OFS Compression Mode Used: HEAVY2 General Info: NOZERO Info Header CRC: 3A65 When the option FULL is added, dms will after the information header show you the compression rates on tracks in the archive. Track Plength Ulength Cmode USUM HCRC DCRC Cflag ----- ------- ------- ------ ---- ---- ---- ----- 0 11264 11264 NOCOMP 026A 58CF 42A7 0 @ENDNODE @NODE DMS_VIEWDIZ @TITLE "DMS option: VIEWDIZ" This command will read a archive and search for a file_id.diz textfile which maybe have been added and show the file_id.diz found. The basic usage for this command is: DMS viewdiz file[.DMS] [SAVE filename] - If the SAVE option have been added, you can choose a filename for the file_id.diz found in the archive, and it will be saved for future use. @ENDNODE *2*********************************************************************** *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE DMSoption @TITLE "DMS options" Options for DMS @{" FROM " link DMS_FROM} @{" TEXT " link DMS_TEXT} @{" CMODE " link DMS_CMODE} @{" LOW " link DMS_LOW} @{" HIGH " link DMS_HIGH} @{" NOVAL " link DMS_NOVAL} @{" NOZERO " link DMS_NOZERO} @{" NOPAUSE " link DMS_NOPAUSE} @{" ENCRYPT " link DMS_ENCRYPT} @{" DECRYPT " link DMS_DECRYPT} @{" VERIFY " link DMS_VERIFY} @{" NOVERIFY " link DMS_NOVERIFY} @{" NOTEXT " link DMS_NOTEXT} @{" NOPAUSE " link DMS_NOTEXT} @{" HD " link DMS_HD} @{" PC " link DMS_PC} @{" DIZTEXT " link DMS_DIZTEXT} @ENDNODE @NODE DMS_FROM @TITLE "DMS option: FROM" Will read the disk from a different device. The default device is DF0: (internal drive). Reading of HIGH-DENSITY DISKS needs the HD option added after the command. Reading of PC DOS DISKS need the PC option added after the command. You may choose any device when the following specifications match. ADOS DISK: 80 tracks, 2 sides, 11 sectors/track, 512 bytes per sector. [Usually DF0:, DF1:, DF2:, DF3:, RAD:, FM0:, FF0:, etc.] ADOS HIGH-DENSITY DISK: 80 tracks, 2 sides, 22 sectors/track, 512 bytes per sector. [Usually DF0:, DF1:, DF2:, DF3: ] Cross-Dos mounted devices. PC DOS DISK: 80 tracks, 2 sides, 9 sectors/track, 512 bytes per sector. [Usually PC0:, PC1:, PC2:, PC3: ] PC DOS HIGH-DENSITY DISK: 80 tracks, 2 sides, 18 sectors/track, 512 bytes per sector. [Usually PC0:, PC1:, PC2:, PC3: ] @ENDNODE @NODE DMS_TEXT @TITLE "DMS option: TEXT" TEXT filetext - Causes DMS to read in the file 'filetext' and add it to the archive. When the archive is extracted the text will be displayed before writing the disk. This is useful for identifying disks or giving other information about the archive. This option will only show the first identified TEXT file, found in the .dms archive. @ENDNODE @NODE DMS_CMODE @TITLE "DMS option: CMODE" CMODE mode - Chooses the compression mode used. Mode is either NONE, HEAVY1, HEAVY2, or BEST The default mode is BEST Available modes are: NONE - No Compression is performed (Straight Read). HEAVY1 - Heavy compression, good speed/compression ratio. HEAVY2 - Best available compression. Only available with >1meg ram. BEST - Chooses Best compression method for available memory. @ENDNODE @NODE DMS_LOW @TITLE "DMS option: LOW" LOW lowtrack - Specifies the starting track to read from. The default is track 0. Lowtrack must be a value from 0 to 79. @ENDNODE @NODE DMS_HIGH @TITLE "DMS option: HIGH" HIGH hightrack - Specifies the ending track to stop at. The default is track 79. Hightrack must be a value from 0 to 79. @ENDNODE @NODE DMS_NOVAL @TITLE "DMS option: NOVAL" NOVAL - Stops DMS from inhibiting the disk validator when reading the disk. @ENDNODE @NODE DMS_NOZERO @TITLE "DMS option: NOZERO" NOZERO - Normally DMS will read the AmigaDOS bitmap from the disk and archive only sectors which are being used. If the disk is a non-filing system disk or has a bad bitmap, DMS will automatically archive the whole disk. In EXTREME cases DMS will make a wrong assumption about the type of disk it is archiving. NOZERO will cause DMS to archive the whole disk totally ignoring the disk bitmap. Generally you will rarely if ever have to use this option. @ENDNODE @NODE DMS_ENCRYPT @TITLE "DMS option: ENCRYPT" ENCRPYT password - Causes DMS to encrypt the input from the disk using the password supplied. 'password' is any alphanumeric word you desire. Examples: Joe, Fred, ABC1234, ONLY-FOR-ME, etc. @ENDNODE @NODE DMS_DECRYPT @TITLE "DMS option: DECRYPT" DECRPYT password - Causes DMS to decrypt the archive with the password 'password'. This is only used if the archive was previously encrypted. 'password' must be the EXACT same one used when encrypting the file otherwise the archive will not be processed correctly. @ENDNODE @NODE DMS_NOPAUSE @TITLE "DMS option: NOPAUSE" - Stops DMS from pausing after displaying any text from the archive. @ENDNODE @NODE DMS_VERIFY @TITLE "DMS VERIFY" We have all tried to unpack Disks and later found out , that the disk had read errors. It's now possible to verify the written datas. DMS will ALWAYS, unless specified, unpack with VERIFY on, why do it without?... DMS will tell you IF an error occured, and report to you the BAD TRACK. DMS will try to write the track 3 times, and after 3 error reports, DMS will continue writing and report to you the bad track. @ENDNODE @NODE DMS_NOVERIFY @TITLE "DMS option: NOVERIFY" You can disable the VERIFY , by adding the NOVERIFY option at the end of the command line. But I do not recommend it! as DMS would then function in almost the same way as previous versions... *example: DMS WRITE .DMS NOVERIFY @ENDNODE @NODE DMS_NOTEXT @TITLE "DMS option: NOTEXT" The NOTEXT option have been changed to ignore Track 0 (bootblock) advert texts to be shown, too...prefered?!... *example: DMS WRITE .DMS NOTEXT @ENDNODE @NODE DMS_HD @TITLE "DMS option: HD" READING HD DISKS ^^^^^^^^^^^^^^^^ @{" NOTE TO USERS OF DMS v 1.5x: READHD" link DMS_SUB_HD} Since Kickstart 3.0, shipped with the A1200/A4000. The AmigaDos can read/write HighDensity(DUAL FORMAT) disks. But untill now, no Diskimploder/packer supports the option of packing those disk types. DMS can take those 1.7Meg disks now. Just remember that this version of DMS do not check IF you are unpacking to a normal doubledensity disk, and writing a Highdensity DMS file, to a normal disk will result in an error. And writing the HighDensity DMS files also needs a new WRITE option, explained later in this documentation. The HD option supports all other available suboptions, like TEXT,NOZERO e.t.c.. NOTE: you cannot REPACK a HighDensity .DMS file. *example: DMS READ .DMS HD WRITING HD DISKS ^^^^^^^^^^^^^^^^ @{" NOTE TO USERS OF DMS v 1.5x: WRITEHD" link DMS_SUB_HD} If you want to unpack a DMS file which is packed using the HighDensity option, you must use this one to unpack the disk correctly again... The HD option supports all other available suboptions, like NOTEXT,NOVAL,NOVERIFY e.t.c.. *example: DMS WRITE .DMS HD >>NOTE: >> >>If you're using the option HD, the disk cannot be unpacked >>using previous versions of DMS, to be more exact. >>you cannot depack a .DMS file packed with V1.51, using V1.11 >> IT IS POSSIBLE TO READ A NORMAL DOS disk( 1.x/2.x ) WITH THIS OPTION BUT IF YOU REALLY WANT TO, THEN SPECIFY LOW 0 HIGH 39 AND IT WILL READ AS IT WAS AN 1.7Meg disk. IF YOU TRY THIS, YOU WILL SEE A SMALL ADVANCHE IN PACKING (10-20K), BUT! THESE FILES CANNOT BE UNPACKED WITH DMS v1.11 !!!!!!!!!!!!!! EXPLANATION WHY THIS WORKS: A normal DOS disk consists of 880K data, each track holds data of 11264 bytes length, where a HighDensity disk can take DOUBLE the size of datas stored on a normal DD disk, and therefor hold 11264 *2 bytes on each track. So it IS POSSIBLE to read with the READHD option, but unless you need to make the file those 10-20K smaller, dont use it for that.. Generally most people still have the DMS v1.11. By some time, maybe most of the DMS users will have the updated version and then.. Thats up to you. @ENDNODE @NODE DMS_SUB_HD @TITLE "NOTE: how to use with dms v1.5x" As from DMS v2.x, the use of the HD option have been changed to be an option added after your command, instead of being a command. It makes reading of disks easier, and less commands to use. But for those with old version left, and intends to continue using that version, the command explanation is still here. READHD. ^^^^^^^ *example: DMS READHD .DMS WRITEHD. ^^^^^^^^ *example: DMS WRITEHD .DMS The instructions is explained closer, in the previous chapter. @ENDNODE @NODE DMS_PC @TITLE "DMS option: PC" Another option in DMS, is packing pc/ms-dos disks, on Amiga. You can pack those disks using the PCx: device (used by CrossDos), all you need to do is, tell DMS to read the disk as a PC disk. By adding the PC option at the end of the command line, DMS will work with the disk in the drive as it is pc/ms-dos disk. People using DMS v1.xx will not be able to unpack these .dms files, but will be notified of using a newer version, when they try to unpack a PC packed .dms file. *example for reading a PC/MS-DOS disk: DMS READ .DMS PC *example for writing a .DMS file back as a PC/MS-DOS disk: DMS WRITE .DMS PC @ENDNODE @NODE DMS_DIZTEXT @TITLE "DMS option: DIZTEXT" Many bulletin boards support the use of FILE_ID.DIZ texts nowadays. The only thing missing was that DMS supported it. The option works in the same way as TEXT. (for more info read below about TEXT) *example: DMS READ .DMS DIZTEXT FILE_ID.DIZ @ENDNODE *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE FMSoption @TITLE "FMS options" Options for FMS @{" MAKESFX " link FMS_MAKESFX} @{" A (Add files to archive) " link FMS_ADDFILES} @{" E (Extract files from archive) " link FMS_EXTFILES} @{" V (View files in archive) " link FMS_VIVFILES} @{" L (List files in archive) " link FMS_LSTFILES} @{" TEST (Test files in archive) " link FMS_TSTFILES} @ENDNODE @NODE FMS_MAKESFX @TITLE "FMS option: MAKESFX" If you want people to be able to unpack your .FMS files, without needing the DMS program, you can use this command.. to make an .SFX file, write: DMS MAKESFX @ENDNODE @NODE FMS_ADDFILES @TITLE "FMS option: A" Add and compress files to archive. With this option you can put files into a archive or you can join those files to a previous .DMS file. NOTE: to add files to a existing .DMS file, add the .DMS extension ex. 1: DMS A .... @ENDNODE @NODE FMS_EXTFILES @TITLE "FMS option: E" Extract files from archive. With this option you extract files from a archive. you can select a destination directory for the files. When extracting, dms will search for .DMS and .FMS files. ex. 1: DMS E @ENDNODE @NODE FMS_VIVFILES @TITLE "FMS option: V" View files in archive. When viewing the compressed archive, dms will show, the most important info on the files, and full directory structure. ex. 1: DMS V @ENDNODE @NODE FMS_LSTFILES @TITLE "FMS option: L" List files in archive. When viewing the compressed archive, dms will show, the most important info on the files, dms will show only the filename. ex. 1: DMS L @ENDNODE @NODE FMS_TSTFILES @TITLE "FMS option: TEST" For testing the .FMS file, use the "TEST" option, and specify the extension too. And dms will validate the .FMS file. ex. 1: DMS TEST @ENDNODE *2*********************************************************************** *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE DMSregister @TITLE "DMS register" You can register your version of the Device-Masher System by filling out the registration text included with the package. It costs Dkr 200, to register DMS. Send only CASH or International Money Order(From your postoffice) And by being a registered user, you will receive the latest updates of Device-Masher System(DMS), and other utilities made by Parcon. Register form and suggestions/bug reports can be sent to: ParCon software. v. Michael Pendec Islandsh0jparken 5, st.th. DK-2990 NIVAA DENMARK We have received several letters, concerning registration. Often asked, were "Can I pay in Danish Kr", We want you to send the fee in Danish Kr, and if its impossible for you to do, then go to your local postoffice, and send us a International money order, shipped by the postoffice. If you decide to include cash in your letter, include ONLY DANISH Kr 200, Or US DOLLARS $30. We will NOT ship DMS out on "C.O.D [Cash On Delivery]" nor payment after receiving DMS. There is only ONE WAY to get DMS, include money with your register form, or use the International Money order, made at your local postoffice. ************************************************************* You can reach us at this bbs, leave mail for : Michael Pendec I do not, at this time, have a FIDO NET MAIL ADDRESS, so I cannot reply to your mail, but all requests, bugreports will be looked into. @{" Perto's Asshole BBS " link Perto} ************************************************************* @ENDNODE @NODE Perto @TITLE "Perto's Asshole" PERTO'S ASSHOLE FIDONET: BBS +45-86720273 16k8 DUAL 2.xGb 2:230/815 BBS +45-86720274 14k4 HST 2.xGb 2:230/816 BBS +45-86293910 14k4 V32b 2.xGb 2:230/817 BBS +45-87370010 64k0 ISDN 2.xGb 2:230/1815 @ENDNODE *1>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> @NODE Index @TITLE "dms.guide Index" @{" About DMS " link DMSgeneral} @{" NEWS IN DMS " link DMSnews} @{" UPDATE Information on DMS (NEW VERSION) " link DMSUPDATE} @{" File-Masher System (FMS) " link FMS} @{" File-Masher System WBench (DMS WB) " link DMSWB} @{" DMS.DEVICE " link DMSDEVICE} @{" UnDMS " link UNDMS} @{" SFXDMS " link SFXDMS} @{" Device-Masher Backup " link DMB} @{" Credits " link Credits} @{" Copyright " link Copyright} @{" Evaluation Limitations " link Copyright2} @{" File-Masher Limitations " link FMS1} @{" Device-Masher Limitations " link DMS1} @{" How do I get a FULL version " link DMSregister} @{" DMS commands " link DMScommand} @{" READ " link DMS_READ} @{" WRITE " link DMS_WRITE} @{" APPEND " link DMS_APPEND} @{" REPACK " link DMS_REPACK} @{" TEST " link DMS_TEST} @{" VIEW " link DMS_VIEW} @{" TEXT " link DMS_TEXT} @{" VIEWDIZ " link DMS_VIEWDIZ} @{" SFX " link DMS_SFX} @{" DMS options " link DMSoption} @{" VERIFY " link DMS_VERIFY} @{" NOVERIFY " link DMS_NOVERIFY} @{" NOTEXT " link DMS_NOTEXT} @{" HD " link DMS_HD} @{" PC " link DMS_PC} @{" DIZTEXT " link DMS_DIZTEXT} @{" FMS options " link FMSoption} @{" MAKESFX " link FMS_MAKESFX} @{" A (Add files to archive) " link FMS_ADDFILES} @{" E (Extract files from archive) " link FMS_EXTFILES} @{" V (View files in archive) " link FMS_VIVFILES} @{" L (List files in archive) " link FMS_LSTFILES} @{" TEST (Test files in archive) " link FMS_TSTFILES} @{" REGISTRATION of DMS " link DMSregister} @{" Perto's Asshole BBS " link Perto} @{" Device-Masher System Documentation " link MAIN} @ENDNODE *2***********************************************************************