JR>

See my later post above. Once you are in the terminal, put in the CP/M boot disk and press the "Drive Type" and "Error" buttons simultaneously. This seems to initiate the loading of CP/M from the disk, but so far it just locks up after showing the CP/M messages on the screen. I have also found that it appears to make a difference which BOIS version you have in the Indus. The two button press doesn't seem to work with version 1.4. With 1.2 I get the behavior noted above, but in a drive with 1.4, pressing the buttons puts an "E" in the display and does not try to load from the disk. It might just be that drive though. I have another 1.2 drive that I'm going to try next. I also found that, in that 1.4 drive at least, putting the Ramcharger board in, made the drive less reliable. Tesing without the board the drive would boot disks fine, with the board in, it would get several read errors on those same disks. It would usually be able to get by the errors, but it was noticably worse with the board in. I suspect that may be due to the extra power needs.

Thanks, I didn't know you could set the density that way. That would explain why I get an error in 1A since the CP/M disk is Double density.

Yeah, I had found that Diagnostic disk, but it doesn't have anything for the ramcharger. Just FYI that diagnostic disk does not seem to like APE. When I would RUN "D:DIAGS" with APE drives active, it would lock up with a heart character on the screen. Disable APE and the diagnostic program runs fine. Thanks for the suggestion about the buttons. That has gotten me a little further. After booting the terminal disk and loading the terminal program, Insert the CP/M boot disk and press and hold the "Drive Type" button and press the Track button on the fron of the drive. This seems to cycle the drive between 3 "modes" 1A, 1b, and 1C as displayed on the LED's. After selecting a mode, press and hold "drive Type" again and press 'Error". This seems to reset the drive and it tries to initiate itself from the disk in the mechanism. The result of this is dependent on the mode selected. In mode 1A I get a G5 error on the panel and nothing on the screen In mode 1b the drive loads some data from the disk and this appears on the screen: FUTURE CPM 2.2 REV 1.0 Hit return to continue COPYRIGHT © 1979, DIGITAL RESEARCH Unfortunately, hitting return does nothing and the drive appears to be locked up. Similarily, from mode 1C the same first 2 lines appear, but not the third: FUTURE CPM 2.2 REV 1.0 Hit return to continue And again the drive seems to be locked up.

Hi Larry, I'm not sure, but I don't think so. How would I go about testing that? It doesn't seem any faster than a regular Indus and seems to need to read the disk every time, even when just accessing a few sectors on the same track repatedly. The drive is pretty beat up and does have some issues. It reads and writes pretty good but can't successfully format a disk. I tried booting with a Super Syncromesh DOS XL Disk that works on my other Indus' and it locks up the drive. I think I'll try swapping the board into another drive that I know to be in good shape and see if I get any better results. I don't have any documentation on the Ramcharger at all. All I got was the drive with the board in it. I found ATR images of the CP/M and Terminal disks online, but can't find any other documentation on this item at all! I'll take some picures of the board in and out of a drive when I swap it to another drive.

Does anybody know how to boot one of these into CP/M? I picked up an Indus drive recently that has a Ramcharger board in it. I found the CP/M disks for it here: http://retrobits.net/atari/indus.shtml I made floppy copies of all the images and I can boot the 40-80 Column terminal disk from the INDUS, but I can't figure out what to do from there. I put the CP/M boot disk in at that point and I assume that there is some way to issue a boot command to the Indus from the terminal program but I cant figure out what it is. I've tried every keystroke and key combination I can think of but can't get the drive to respond to anything once I'm in the terminal program.

WOW! I think that is my old 1090XL! I recognize the scratch on the front! I sold it several years ago before I got back into the 8-bits. I wish now that I hadn't done that, but I'm glad to see it's still around! Update: I just located some old pictures I took before I sold it. That sure looks like the same scratch. PS - I didn't make the scratch, it came that way when I bought it from Best.

This might help. OmniView.pdf

I thought OSNXL was the OS that contained Omnimon. My memory is very sketchy. Wasn't OSN XL the Fast chip (or something like that)? - Steve Hey Steve...how's it going? You can read all about it here: http://www.cyberroach.com/analog/an25/onmiviewXL.htm

I thought OSNXL was the OS that contained Omnimon.

Sorry it took so long!

I've got one of those 5.25 + 3.5 mods in one of my XF551's, but there's more to it than just a ROM, there is also an epoxy sealed module with several wires that attach to various points on the MB.

I've got one of those 64X4 130XE's sitting around here somewhere. It may take a while, but I'll try to dig it out and take a picture of the MB.

Yep, all that's really in there is a Power Supply, Buffers for the PBI lines and 5 Edge Connectors.

Now that I'm actually looking for it, I'm not sure there ever was a Woolley 5.25 version. I think his may have just been the 3.5 mod and I had confused the CSS XF Update with a Wooley patched version. I'm pretty sure the XF551360.bin I posted is just the stock XF OS.

Yeah, I think you're right. Maybe this is the one. It's the only other 360K one I have, but it might be stock too, I don't know for sure. xf551360.bin

I believe this is the Woolley 5.25 version: XF551.zip You can find the Hyper-XF Roms here: http://www.atariage.com/forums/index.php?s...c=84017&hl=

well, lets see...There is a PAL version ... from Atari I assume. There is the Bob Woolley version that fixes a few issues in the original. There is also a Bob Woolley 3.5" 720K version. From CSS there was the "XF Update" that improves upon the stock OS as well as the "XF single Drive Upgrade" that also upgraded to a 3.5, and the "XF Dual Drive Upgrade" that allows the XF551 to support both a 5.25 and a 3.5 mechanism at the same time as 2 separate drives. This upgrade includes both an OS upgrade as well as some additional electronics to support the second drive. Those along with the stock NTSC and the 2 versions of the Hyper-XF are the ones that I am aware of.

Hi Larry, They are called decoupling capacitors. Digital electronics tend to generate a lot of noise in the power supply traces and these help filter that out and maintain pure DC voltage. They should be placed between the + and - power pins of the chip, as close as possoble to the chip itself. Not sure what value Atari used, .1 MFD should do the job.

C012409 would be the Atari part number. Most likely a ROM chip from some cartridge that was from a bad batch or overstocked.

Finally got around to checking mine: 72R DA 11169 203 72R DA 12974 203 83S DA 74756 203 What do you suppose the odds were that I'd have three with the last 3 numbers stamped on the label all the same (203)? One in a million by my calculations (of course I'm sure not all numbers were ever used).....guess I better buy a lottery ticket today!

You might try these products with the CF/IDE adapter plugged directly into the IDE bus of your PC instead of using a USB card reader. Then the device should appear as an IDE drive instead of a USB Mass Storage Device.

Here ya go. USPOS_1011.ZIP

I don't believe I have a copy of that particular version of MyDos in my collection. Any chance you could post an ATR of that? Also I have some scanned images of the CSS Ultraspeed OS manual if you need them. If you do decide to replace it with a 32 in 1, I'd be interested in buying the Ultraspeed module from you.

It might be the CSS Ultra Speed Plus OS upgrade.

Um...The drive busy light is ON the mechanism