Welcome, Guest. Please login or register.

Author Topic: Troubles With Large HDs...  (Read 2142 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Karlos

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16879
  • Country: gb
  • Thanked: 5 times
    • Show all replies
Re: Troubles With Large HDs...
« on: January 07, 2011, 12:17:26 PM »
The only time I had a problem with a HD > 4GB was down to an OS3.9 rom update being replaced with one from 3.5 (as indicated by the filesystem resource version) which was readily fixed. Not sure what happened there but I had been tinkering and may have overwritten it, thus a clear case of PEBCAK.

However, I think that it might be handy for people that are returning to the scene after years away, or people that are new to it all. My first suggestion would be to make a downloadable archive that can be extracted to a floppy and if there is enough demand for it then go that way.

Incidentally, if you aren't using SCSI on your Blizzard (assuming it has it) then you are a very silly person. Like me ;) 10MB/s DMA-based disk transfer is nice to have...
int p; // A
 

Offline Karlos

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16879
  • Country: gb
  • Thanked: 5 times
    • Show all replies
Re: Troubles With Large HDs...
« Reply #1 on: January 07, 2011, 12:52:13 PM »
Quote from: Franko;604599
Course my BLizzard has SCSI but IDE is cheaper and fast enough to do the job. Also SCSI drives as far as I can tell are no longer manufactured, ever tried buying a brand new one lately... :(


SCSI is still available. However, the route I intended to take (but never got around to it) was to use an SCSI <-> IDE adapter (or today, a SCSI <-> SATA). They are pretty expensive, but one of those plus a large IDE drive will cost less than the equivalent large SCSI drive ;)

The Blizzard SCSI interface will still be the rate limiting link in the chain, so you should be able to get it running at full tilt - just without the CPU load :)
int p; // A