CompuServe Messages

SetPatch Crash/A3000 3.1

    29-Sep-94 21:07:37
Fm: Eulogio (DJ) Garcia 74471,23
To: Dave Arre 70337,1642
Dave, your 3000 sounds like most 3000s. There is an empty space where it looks like two more ROM sockets might go, but are not installed. I think those might have been for network booting, I'm not sure, but they are perfectly normal as they are (empty). The 3.1 ROMs go in the old ROM's sockets. They are obviously in the right place, or you wouldn't boot, with or without setpatch :-). SetPatches are meant for specific OS releases. NEVER run a setpatch from a different OS release, or your system will shrivel up and turn into a stinky puddle. OK, I exagerate but you get the drift <g>. It is best to find out why the patch is making the system crash, because to me that indicates something somewhere ain't kosher. You might want to comment out the QUIET from the setpatch command to see what it's doing, and put an ASK command right after it to stop until you can read the messages. You will also find out if the SetPatch is crashing or if it's something else further down the startup sequence. DJ On AP from Queens, the thrill and excitement of the Big Apple Where a little paranoia is always a healthy attitude …