Jump to content

AGiambra

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

18 Good

About AGiambra

  • Rank
    Space Invader

Profile Information

  • Custom Status
    DOSMaster
  • Gender
    Male
  1. There's a Wikipedia article that says this: "Plans for DOS XL 4 were scrapped due to low demand and competition" http://en.wikipedia.org/wiki/DOS_XL
  2. I have DOSXL 2.30p (same as you posted). But I am unfamiliar with the Bug/65 fix. Could you explain it?
  3. Hah hah. Thanks Ken. I've been a student of Atari Dos for years. One of the things i've always loved to do is make it do things it was never designed to do. My copy of Inside Atari DOS is so dog-eared it's nearly falling apart. Actually I'd like to change my name to DOSMaster but I can't find where to do it. Do you kow how?
  4. I mentioned that I had written a utility called RAMDIR that moves the disk directories and the VTOC up into the memory under the OS. From then on it will access the directories from there instead of the disk. It will do this for up to 3 drives. If the directory or the VTOC has been modified it will get rewritten back to the disk of course. It's smart enough to know if the disk has been swapped out and if so it will refresh the directory pages in memory. You turn it on by keying in RAMDIR. You turn it off by keying in RAMOFF. When using disk with lots of files, it saves a lot of IO since the disk does not have to be accessed to find files in the directory. The only IO that takes place is to check if the disk has been swapped out. The utility uses sector 720 which, due to a bug in DOS, is never used. It writes three random numbers to sector 720. Whenever a directory search is done, it checks sector 720 to see if the same disk is still in the drive. Hope someone finds this useful. Ange PS: You'll see the screen flicker a little as it works. This is because the program is rapidly back switching from OS memory to RAM memory. RAMDIR.atr
  5. i've never been happy with the UNDELETE program. You had to key in the name of the file you wanted to undelete, Wouldn't it be nicer if the program displayed the names of the files on the disk which had been deleted? And all you had to do was choose which file to undelete? I rewrote the UNDELETE program to do exactly this and I am much happier with it. I've re-posted the Utitilies disk with the new version of UNDELETE on it. Ange Utilities.atr
  6. That's pretty cool stuff Bob. I recently wrote a utility that puts the DOS Directories from each drive into the RAM beneath the OS. Whenever you issue a directory command or copy files or do anything that accesses the disk, my utility reads from the RAM resident directories instead of the drives. On drives where you have lots of files it saves a lot of IO. The utility is smart enough to know when directory entries have been changed and need to be written back to the disk. It's even smart enough to know if you have swapped out the disk because then the RAM versions of the directory need to be refreshed. Fun stuff.
  7. DOS uses location $709 to determine how many bufers to allocate. By default this is set to 3. So DOS will allocate 3 128 byte buffers. Location $70A is used to tell DOS how many drives you have. If you set this to 3 it means there are two drives. If you set this to 7 it means you have three drives. 15 means you have four drives. Of note, DOS also has a bug. Put three double density drives online and then try copying a file from one drive to the other. You'll get an error 161 (no buffers available). DOS doesn't allocate enough buffers when your have three DD disks online. To fix this, set location $709 to 7.
  8. Yes I used the disk version of MAC/65 (although during this project I also used the cartridge based version. I like the cartridge version because it allows you to use the SET 6 command to create an offset. I don't know why this was not included in the disk based version), I am running on an 800 XL.
  9. If anyone can use them, the attached ATR has several utility programs I've written. SORTDISK will sort the directory of any ATARI DOS disk (including DOSXL). Since Atari DOS stores the file number in every files data sectors, it will rewrite each file with the new file number. I am working on a new version that does not require data sectors to be rewritten FIXDISK will repair disks of common problems. Opening a file for output and not closing it can cause hidden directory entries that chew up space on your disk. Run this utility on your disks and if there are any errors it will report on them and repair them. If there are lost sectors on your disk it will give them back to you. UNDELETE will undelete a file as long as the data sectors in the file have not been reused by another file. If so, it will tell you that the file cannot be undeleted. RAMXL is very cool (if you are running on an XL machine). When using DOSXL, external commands such as COPY, DUPSK, etc. have to load into memory every time you use them. Rename RAMXL.COM as AUTORUN.SYS. On a DOSXL disk, change the extension of COPY.COM to COPY.MEM. You can rename up to four files (such as DUPDSK.MEM, INIT.MEM). When you reboot your disk, RAMXL will search for file with the MEM extension and store them beneath the OS. Now, to run any external command, prefix it with RUN 2300. For example, to copy a file your would key in RUN 2300 COPY <File A> <File B> Or to run DUPDSK you would key in RUN 2300 DUPDSK Finally, a hidden utility. Atari DOS will only let you store 64 files on a disk, even if it is a double density disk and has lots of room. This ATR was created with a utility I call DOS CD (capacity doubler). It will allow you to store up to 128 files on a DD disk. If you boot from this disk and then create new disks using INIT to rewrite your DOS files, the new disks will also have DOS CD on them. I hope someone finds this stuff useful. Utilities.atr
  10. Concerning your question "Can I just move it up $0200 bytes instead of $0C00 bytes" I wouldn't recommend this Bob. Atari chose to put it at least $0300 bytes above DOS. This is because Atari DOS needs at least that much memory for its buffers. If you put it any lower you risk crashing DUP.SYS. But you can experiment and see what happens.
  11. Bob, Load DUPSYS2.M65 and search through the listing for "MDEND+" You'll find a line that says "MDEND+$0C00". Change the $0C00 to any value you like and you'll move the resident portion of DUP.SYS up by that value. Attached is an .ATR of DOS with DUP.SYS moved up by $0C00 bytes. If you look at the heading after you boot, you'll see I changed the Version number to 3.0S. I wanted to have something visual so I'd know which version of DUP.SYS I was running. Have fun!!!!! Ange PS Why didn't I think of simply attaching an .ATR berfore???? This makes it so easy. On the .ATR disk I have included all the files you'll nned to modify DUP.SYS. Ain't this fun?????? Atari Dos with Modified DUPSYS.atr
  12. The command in BUG65 should be W 4540 6C05 #D:DUPSYS.COM
  13. I forgot that the CONVERT program INCLUDES a MACRO called IOMAC.M65. Download the attached file and place it on the same disk as CONVERT.M65. When you assemble this program, it will call the MACRO file. IOMAC.TXT
  14. Everything beyond line 2008 is uncommented. That's what I meant when I said the code was uncommented. Yes I can give you a step by step. First, do the following: I assume you have a method of getting the files from Windows onto your Atari disks. I use Ape for Windows which has a nice function called MIRROR that alows me to take files from Windows and put them on Atari disks. Next the files need to be converted becuase the carriage returns are in Windows format. Using MAC/65 key in the program called CONVERT.TXT and assemble it into CONVERT.COM. To convert the files, first rename Dup.Sys Part 1.TXT to INPUT.DOC. Put CONVERT.COM on the same disk and run it. The conversion program will create a file called OUTPUT.DOC. Rename this to DUPSYS.M65 Do this for the four remaining files. Make sure that you name the remaining files DUPSYS2.M65, DUPSYS3.M65 and DUPSYS4.M65. This is important because the first file references the others. Also download the file called INSTALL.TXT. Key it into MAC/65 and assemble it into INSTALL.COM. Now you're ready to modify DUP.SYS on your system. Make sure all four DUPSYS files are on the same disk. Run MAC/65 and key in: ASM #D:DUPSYS.M65,,#D:DUPSYS.COM This will run for quite some time and create the DUPSYS.COM file. Now run BUG65. Key in R 3000 #D:DUPSYS.COM This will load the COM file into memory with an offset of $3000. For now, don't worry about why we're doing this. Now key in W 4540 6B05 #D:DUPSYS.COM When the file finishes being written, key in Q to exit BUG65. Okay we're almost done. Copy DUPSYS.COM and INSTALL.COM onto a standard Atari DOS boot disk. Boot from the Atari DOS disk. Issue an L command to tell DOS you want to load a file. When it asks which file to load, key in DUPSYS.COM Next issue an L command to load another file. When it asks which file to load, key in INSTALL.COM INSTALL.COM will load and install the new version of DUP.SYS. It will happen in the blink of an eye. Now issue an H command to tell DOS you want to write out new DOS files. When it asks which drive to write them to, key in 1 and press RETURN You're done! The modified version of DUP.SYS in installed and whenever you boot from this disk you will be in the new version. To install it to other disks, simply boot from this disk and write DOS files to the new disk. I hope this was not too hard to follow. I'll be glad to answer any follow up questions you might have. Dup.Sys Part 2.TXT Dup.Sys Part 3.TXT Dup.Sys Part 4.TXT Install.TXT Convert.TXT Dup.Sys part 1.TXT
×
×
  • Create New...