[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Uncooperative RamFast
Steve:
Could somehow the RamFAST's ProDOS 8 re-mapping be pointing the boot volume
to a volume on the now disconnected drive, since that configuration data is
also stored in a reserved block on your other drive?
Anyway, I've found that the The '0' and '1-7' keys seem tough to time, at
times.
But, all is not lost.
I use the 'RAMFAST.SYSTEM' program in the 'CVTECH.RAM' folder that you can
put on any disk.
Then, just boot from the disk that contains _that_ to run the program and
access the setup screen. (As you already know, I'm certain) On a IIGS, just
change the boot slot in the Control Panel. On a IIe, put the RamFAST in a
slot lower than the floppy or other drive.
I can send you that Program/Folder if you'd like. It's the same one that the
RamFAST writes to your drive when you instruct it to do from the config
screen.
Let me know if you need it. All my RamFASTs are Rev Ds, if that matters to
you.
Also, I've found over the years that if you're dumped into the error screen,
a power-off may be required to clear it.
BTW, may I assume that those SCSI<--->CF card adapters don't permit hot
swapping, or do they?
Hugh Hood
in article 38idndDqQePG6R_TnZ2dnUVZ_jKdnZ2d@giganews.com, Steven Hirsch at
snhirsch@gmail.com wrote on 9/27/11 8:11 PM:
> I'm running out of ideas and wonder if someone in the community can help.
> While testing my SCSI<-->CF card adapter, I added a drive at ID2 and
> partitioned it for test. That works fine. The problem is this: How on earth
> do I _remove_ that drive from the RamFast configuration? The utility program
> provides no obvious way to remove the physical drive. If I try to boot with
> it disconnected, I get the ** Unable to load ProDOS ** screen and a hung
> computer.
>
> The manual claims I can hold down '0' at start to force it into the setup
> screen (or 1..7 to boot other volumes), but this simply does not work. It
> jumps to the error screen and refuses to respond to any keystrokes.
>
> What am I missing?
>
> Steve