ir645@sdcc6.UUCP (Laurence Weiss) (05/10/86)
Help!
I am having a problem with RAMSTART on a MAC+; I am hoping one of
you ResEdit Gurus out there can help me with.
I made the modifications to Version 1.21 that have been floating about
on various networks: at sector $0C offset $B4, 4EBA 0682 -> 4E71 4E71
and at $0D offset $17A, 6700 0012 -> 6000 0012.
My problem is that on some of my disks, this works fine (for example
the 400K ramdisk I have set up for terminal emulation). Ramstart makes
the virtual disk, copies everything, ejects the floppy I started from, and
reboots to the finder in ram. On others, for example the 512K I set up
from my MacWrite disk, RamStart bombs with "Sigh, Programmers error:
unable to find our drive #, (Quit) (Continue)". If I hit continue, it bombs.
If I hit Quit, I return to the desktop with my startup disk and the RamDisk
Icons showing. I can then eject the startup disk, open the folder on
RamDisk called Unamed #1, and Opt-Cmd-DblClick on the finder, and
everything works fine from there on out.
I tried one other thing, which was to change RamStart's driver number from
10 to 11 with ResEdit; That made no difference.
So my question is: what causes some of my disks to halt before
RamStart manages to reboot to the memory copy of the finder?
Send me mail, and I will post a summary of the best answer(s).
Thanks much in advance,
Dan Graifer
sdcsvax!sdcc6!ir645
Ignore the Larry Weiss on the Header of this. This is my advisors account,
but as he has never logged on in his life, I doubt he has any knowledge of
the weird things I do on it! Besides, he's on sabbatical this quarter.