//flex table opened by JP

Click to See Complete Forum and Search --> : Tough one - Win 95B & hard drives


MaxVal
03-26-1999, 10:18 AM
I have a realitivly complex system-
Epox super 7 MB
P233 @ 262mhz
Matrox G200 TV
128MB PC-66
2 IBM Deskstar 8.4 -Prime. master- Sec. master
Inito 9100u SCSI cont.
Quantum Viking II
Toshiba SCSI CDROM
Yamaha 4260 CDR
Sound Blaster Vibra 16
PCI ethernet adaptor
AOpen FM5600-ITU modem___
System worked fine till I trashed it and had to reformat, reinstall win95, and aplications.
The problem- Win95 SR2 now thinks my IDE drives are SCSI devices. The disk property fields list sync data, disconect, and int 13h (grayed).
The system works O.K. ,with these known exceptions- When playing back long wave files there are periodic "disturbences" in the sound. These seem to happen when the IDE led lights.
At first I thought it might be a DMA problem, But the problem can be heard on CD's that I burn.
Second- AVI fies I previously captured on my drives now drop frames at regular intervals.
I have tried deleating the VIA UDMA driver then restoring the Standard win95 controler, deleating the IBM drives, searching the registry for references to the IBM's as being SCSI , and deleating them. Upon reboot, everything reverts to as it was.
Anyone have any ideas?
Thanks in advance!

Bleeding Edge
03-26-1999, 11:46 AM
I guess you know about AVI drives. I don't know if these Deskstars are or aren't. I'm under the impression that AVI drives are of the SCSI flavor. So I'll assume they aren't.

The problem with IDE drives, when used for playback or recording long sound or video files, is the way they are made to recalibrate themselves at a set interval (every so many milliseconds) for thermal distortions caused by the heat generated by the spinning disks and motor. This is the design of the drive. It has to realign the heads. This results in the symptoms you described.

But on AVI supported SCSI drives (maybe all new scsi drives now) this "alignment" doesn't take place (is withheld) until the stream of data is completely transfered. Resulting in smooth sound and video.

Therefore, I suspect that you were previously using the Viking drive to read and record those long files from.

For some reason I think you are aware of this.

On a other note.

Have you rechecked the SCSI card bios setting for the maxium tranfer rate of your devices.

Did you remember to update the SCSI controller's drivers.

Are you using the the same drive as before as the boot drive.

Instead of deleting the VIA drivers have you tried choosing Update Driver to install Win95 OSR2 UDMA drivers (does it have any? you would have to locate it on the hard drive first)

[This message has been edited by Bleeding Edge (edited 03-26-99).]

Bleeding Edge
03-26-1999, 05:05 PM
What's showing under Performance tab of ControlPanel/System/ Are your drives aren't showing up as being in Dos Compatability Mode are they?

What about Device Manager. Are there any yellow exclamation warning symbols?

Did you recheck the motherboard bios settings to confirm the correct configuration for the Deskstars?

Out of curiosity, see if the Mh32bit.386 driver is being loaded in the System.ini.

[This message has been edited by Bleeding Edge (edited 03-26-99).]

MaxVal
03-27-1999, 12:13 AM
Thanks for the tips! I am aware of the recalibration, but with the previous installation the IDE's worked OK. I'm using the same boot drive, I installed everything in what I belive to be the same mannor. I just get the feeling that the trouble has to do with Win95 detecting the drives as SCSI- no DMA box.
I had previously downloaded the highpoint VIA UDMA from the Epox site, and it gave me the highest numbers under Nuts&Bolts98 (7.2Mb/s).
I do relize that some of these drivers are optimized for tests, but it felt fast also.
It almost seems as if the problem could be a smaller buffer now!
Thanks again, and if you or anyone else have any other Ideas, I would be glad to hear them!
MaxVal

JROBERTS
03-27-1999, 12:52 AM
Windows95 has trouble detecting some ide harddrives correctly. Microsoft released a file named REMIDEUP.EXE to fix the problem. Here is a link where you can download it. users.cyberzone.net/zencomp/TX-Utils/remideup.exe (http://users.cyberzone.net/zencomp/TX-Utils/remideup.exe)

Hopefully this will fix the problem.