#SetPatch 3.1 Woes
6 messages in this thread
Steve:
I just tried the SetPatch in the library here (40.14) and got the same
hang-up at boot-time. Looks like I'll have to live without the SetPatch. I
just can't figure out why. Do you think I should try to use the old 37.10
SetPatch from 2.04, rather than do without any at all?
Hmmm… just thought of something… do you think I could have an old/out
of date/ prototype device driver that is hanging up with SetPatch? No,
can't be… I wiped out the old SYS: partition already, and re-installed
3.1… the only thing I can think of now is a hardware problem.
— Dave
Dave,
I've got no idea. If it were me, I'd backup, format the harddrive(s), install
3.1 from scratch, then restore the applications.
Dave:
Does it crash if you disable your hard drive and boot from the original
3.1 floppies? If it doesn't, you might try using HDTools to low-level
format and repartition your hard drive. I'm reaching, but you may have
corrupt Rigid Disk Blocks that are causing the problem. Anyway, use the
early startup screen to take your hard drive off-line or simply unplug it
from the SCSI controller.
Wayne
Wayne:
>>Does it crash if you disable your hard drive and boot from the original
3.1 floppies?
Yes. Disabling the HD partitions makes no difference.
— Dave
Dave,
This may sound dumb, but do you have the ROMs installed in the right
sockets?
Steve:
I followed instructions on putting in the ROMS (Rom0 in U181, Rom1 in
U180), and it would seem to me that if the ROMS were not properly
installed, the machine would not boot at all. However, I am now running
3.1 successfully, just no SetPatch.
— Dave