CompuServe Thread

#A3000 Upgrades

4 messages in this thread
#163208From: Eulogio (DJ) GarciaSep 9, 1994 9:34 PM
WARNING!!! *** You Must Use The "Initiate Synchronous SCSI" Option *** I changed mine to NO with the BATTMEM utility and my HD went bananas. I had to disable the HD, which would stay lit continuously and wouldn't let the floppy boot, then boot from floppy and use BATTMEM on a floppy to change it back, then reconnected the HD. I sweated rocks for a while <G>. This is after switching to 3.1, so I don't know if the same would be true under 2.1. DJ On AP from Queens, the rotten core of the Big Apple
#163247From: matthew straneySep 10, 1994 12:47 AM
And how big were these rocks?, about the size of a brick, oh yeah that wouldn't be sweat would it. <G> I know that feeling, I had a drive freak out from a shareware reorganizer, NEVER AGAIN. Matt Straney, 3 hours late, without your luggage from Grand Ledge — on AutoPilot ——–>
#163369From: Dave ArreSep 10, 1994 6:12 PM
DJ: You changed your SCSI drive to ASYNC *AFTER* upgrading to 3.1? I have 2.04, and according to SCRAM3, the SYNC transfer is set to NO! I've never touched it. Should I change it now, to avoid a disaster, or, perhaps, keep a copy of SCRAM3 on a floppy and change it that way if there is a problem like you did? Do you know what the setting was BEFORE upgrading? Thanks for the warning! — Dave
#163400From: Eulogio (DJ) GarciaSep 10, 1994 10:39 PM
Dave, according to Battmem, I had Initiate Synchronous Transfers set to YES. The drive went into a tiz when I switched to NO – I couldn't even boot from a floppy without disconnecting the HD. DJ On AP from Queens, the rotten core of the Big Apple