VOGONS


First post, by dogchainx

User metadata
Rank Member
Rank
Member

I'm wondering if anyone has had issues with an internal Iomega Jaz 1GB drive freezing their system when accessing it in Windows 98SE?

I have an internal PCI Adaptec 2930 scsi 50 pin with a SCSIselect BIOS and two different internal Jaz SCSI drives with 5 different Jaz disks.

Also, on boot up I can enter the Adaptec SCSISelect bios and see the Jaz drive, but when I go to verify or format the drive the whole system hangs for a bit then a timeout error occurs. No activity on the iomega Jaz drive happens. I read a posting a long time ago where someone had a similar issue that would freeze his entire Windows 98 system if he tried to access his Jaz drive, where the amber access light stayed steady. There was no solution to his problem.

I hooked up three different SCSI hard disks (2gb, 4gb and 4gb) and was able to verify and format their media, and access those drives in Windows 98SE. But the Jaz drive hangs. I've tried different parts of the cable (1st, 2nd, and the 3rd, which is the terminal end), different SCSI ID's, different SCSI BIOS settings, etc. No solution to the Jaz drive NOT being able to be accessed.

Before I go buy another Adaptec controller (2940uw) for $15 shipped off ebay, is there a simple solution I'm not seeing? Any help would be grateful. Thanks!

:::UPDATE:::

My brother pulled out of his closet an external Jaz drive. It works perfectly fine with the card. I'm guessing the internal ones are just dead, and bad luck of getting two drives in a row dead in vintage systems. Oh well. Moving on!

:::2nd Update:::

Yes, the other two Jaz drives are DEAD. They might light up, but they won't read disks. I found another Jaz internal among my collection (3rd one) and hooked it up. Works just fine! Meh...i hate dead vintage computer equipment. Oh well...again, moving on!

Last edited by dogchainx on 2016-02-16, 03:39. Edited 1 time in total.

386DX-40MHz-8MB-540MB+428MB+Speedstar64@2MB+SoundBlaster Pro+MT-32/MKII
486DX2-66Mhz-16MB-4.3GB+SpeedStar64 VLB DRAM 2MB+AWE32/SB16+SCB-55
MY BLOG RETRO PC BLOG: https://bitbyted.wordpress.com/

Reply 1 of 6, by Kahenraz

User metadata
Rank l33t
Rank
l33t

Just so you know, these things are ticking time bombs. My dad asked me to pull some data off of his old Jaz disks and when I put them into the dive, the part of the disk where the platters are connected to the plastic frame broke apart while they spun up. Out of something like 10 or 12 disks I think only two didn't fly apart in the drive.

To clarify, the disks were shipped around multiple times between moves and placement in storage lockers. They experienced both very high and very low temperatures during this time. When the drive spun up the plastic actually broke apart between the connection of the disk housing. This resulted in the platter stack "floating" around inside the disk after removal from the drive.

I would not recommend these disks for anything other than a novelty.

Reply 2 of 6, by dogchainx

User metadata
Rank Member
Rank
Member

Thanks for the heads up. I don't trust ZIP or Jaz, but transferring a few things between systems makes it a bit easier.

I'm creating an all-in-one media station that can read any media. I doubt I'll use the Jaz drive much, but I have had it requested a few times in the past. I'll just use the external Jaz for now.

386DX-40MHz-8MB-540MB+428MB+Speedstar64@2MB+SoundBlaster Pro+MT-32/MKII
486DX2-66Mhz-16MB-4.3GB+SpeedStar64 VLB DRAM 2MB+AWE32/SB16+SCB-55
MY BLOG RETRO PC BLOG: https://bitbyted.wordpress.com/

Reply 3 of 6, by Cloudschatze

User metadata
Rank Oldbie
Rank
Oldbie
Kahenraz wrote:

I would not recommend these disks for anything other than a novelty.

Your Jaz experience sounds more like an exception than a norm. Iomega did issue a recall for faulty cartridges at one point though, which is something that anyone using Jaz media should probably watch out for:

https://web.archive.org/web/19980118002914/ht … az/jazdisk.html

Regarding the original issue, can you describe how your internal SCSI chain is terminated, dogchainx?

Reply 4 of 6, by dogchainx

User metadata
Rank Member
Rank
Member

Its terminated by the last SCSI drive (and only) which is the Iomega Jaz. I even tried a few different cables, both with the Jaz drive in the middle of the cable with a SCSI terminator at the end. The working drive I tested is configured with jumpers exactly the same (SCSI ID 0, sometimes 1 or 2) and the SCSI ID of the controller is 7. The working one has no issues whatsoever no matter the cable or where its place in the drive train.

With the "problematic ones" I tried to flip around the ID's to see if that made any difference, with the controller at 0 and Jaz at 2, 4 and 6 but no difference. The disk spins up, then no activity after that and the drive times out in SCSISelect bios and in Windows98SE when i try TIP or access the drive in explorer.

386DX-40MHz-8MB-540MB+428MB+Speedstar64@2MB+SoundBlaster Pro+MT-32/MKII
486DX2-66Mhz-16MB-4.3GB+SpeedStar64 VLB DRAM 2MB+AWE32/SB16+SCB-55
MY BLOG RETRO PC BLOG: https://bitbyted.wordpress.com/

Reply 5 of 6, by Cloudschatze

User metadata
Rank Oldbie
Rank
Oldbie

Bah, sorry, I'd missed the edit where you mentioned that a third internal Jaz drive worked fine.

Reply 6 of 6, by dogchainx

User metadata
Rank Member
Rank
Member
Cloudschatze wrote:

Bah, sorry, I'd missed the edit where you mentioned that a third internal Jaz drive worked fine.

Thanks for the help though! 😎

386DX-40MHz-8MB-540MB+428MB+Speedstar64@2MB+SoundBlaster Pro+MT-32/MKII
486DX2-66Mhz-16MB-4.3GB+SpeedStar64 VLB DRAM 2MB+AWE32/SB16+SCB-55
MY BLOG RETRO PC BLOG: https://bitbyted.wordpress.com/