Gateway CDROM misery...it won't work !

It's an older gateway (P5-200) windows 95 machine.
hard drive went bad, fixed that and tried to install windows from CD, but it wouldn't work, even with the cdrom being the first boot device in the bios. So I installed w95 from backup floppies.
The CDROM is actually a Mitsumi FX120T plugged into the secondary on the MB, same as it was from gateway, when it was new.
I downloaded and installed drivers-I tried the drivers from gateway, and from somewhere else for the mitsumi. I found no difference.(system.ini, config.sys, autoexec.bat, all edited)
During normal boot, the cdrom is not detected, so the drivers don't load, and the secondary IDE controller doesn't show up in the device manager.
Now when I plug it into the same ribbon with the HD, and change jumpers, it's detected and the secondary IDE controller shows in the device manager, but if I try to use it, I get an error "code 4 "...I can't find anymore info about "code 4 ".
I've tried different ribbon cables, checked all the connectors pins, and tried all jumper settings, and even tried another power plug. Nothing seems to work.
The drive itself I think is OK....the drawer opens and closes alright, and the light flashes.
I also tried a W98 boot floppy and choose cd support, the drive spins up and tried to read the cd, but I get the "code 4 ".-note; this is only when the cdrom is on the same ribbon with the hd. When the cdrom is on it's own ribbon and plugged into the secondary on the MB, I get nothing....it doesn't work in dos or windows.
I also noticed that when the cdrom is on the hd ribbon, the secondary controller is enabled in the bios, and I can select it, but when it's on it's own ribbon, the secondary controller is disabled, and I can't select or change it. I've tried everything I can think of....2-3-4 times ! What am I missing?
Help?

 

Hi Welderjeffo,

Sounds like you have tried a lot of things. I would run the drive in another PC, that should rule out a problem with the drive itself. While it is out, remove it from Device Manager. I would also remove the Seconary IDE controller, you may need to have the motherboard/chipset drivers ready on reboot.

At least, try it in another machine then let us know the outcome. It will make the possibilities a lot more managable.

Matt

 

mattman has a good idea.

trying on a different system, if it works there, it would eliminate things like
a bad cable. I've had a couple drives go out on me and it was things like those
little internal gears would wear down (sometimes work, sometimes dont).
These were Mitsumi drives from Gateway also.

Sorry, cant help with error code 4....

savagcl

 

Well guys, thanks for the replies, but no help.
The drive works fine in another pc with XP using mitsumi drivers i downloaded.
I put it back in the gateway, it won't work, with mitsumi drivers, or the drivers from gateway.
Except for 1 time, I had it working, but it wasn't showing in the device manager, so i rebooted and now I can't get it working again.
I can't figure out what I did to make it work before the reboot.
When I have all the drivers in place and system.ini, config.sys, autoexec.bat are edited accordingly, the drive shows up in explorer, but it doesn't work, and it doesn't show up in device manager.
When i let windows detect new hardware, it finds a "standard IDE/ESDI controller ". If I let windows install it, and reboot, the drive is not detected, and no drivers load, nor does it show in explorer, but it shows up in device manager with "! ", and says it's using the MS-DOS compatibility mode.
Now if I try to manually install new hardware, i need an installation disk, or at least it seems like I need a .inf specifically for that drive.....I have no idea what that .inf might be named. I've searched through all the cab files on both W95a+W95b cd's for anything that looks like it might be the right one.
The only other thing I can think of is the registry has a bad entry, or it's missing an entry.
I had the same problem with my compaq presario....no matter what I did, I couldn't get the cdrom working, but lucky for me, I found my quick restore disks and that fixed that rig.
But I don't have the restore disks for my gateway, and even if I did, it probably wouldn't work because of the HD problem.
I'm about ready to pull out my hair on this one!
Any more ideas? anyone?
thanks.

 

Ok, so the drive works good. Thats progress anyway.

I found this doing a google for it.
Attention! Windows 95/98 uses its own IDE driver. Normally this operating system recognizes Mitsumi drives without any problem. Under "CD-ROM" the device manager will then say: "Mitsumi (drive specification)!B ". If, however, the drive is not recognized, carry out manual hardware recognition. Positively do not load any older proprietary drivers offered to you for manual hardware recognition. These drivers block the search for your IDE drive. For further information on Windows 95/98, please contact Microsoft.

This page has a diagnostic program for win 95/98, you may want to give it a try.
http://www.mitsumi.com/enduser/1_drivers.html

clif

 

Just had one thought. Try booting into Safe Mode and look in Device Manager there. I would say that you will have a long list of old drivers under the CD drive section. Remove them all. On reboot try the different install paths if Windows detects it: Windows selection (if it autodetects), select from list (if it is listed) or "have disk" and browse to the best(?) drivers.

Just had another thought (wow, two in one day!! ). Get a Win 98 boot disk from www.bootdisk.com. They have several CD drivers. If that works, you could use those drivers and edit your config.sys and autoexec.bat files to emulate those of the boot disk. (As a project, I did this one time in 95 to make a customised boot disk, with the CD manufacturers drivers. Because I learning and teaching myself at the time, it took a little trial and error, but I did it and was quite pleased with myself ). I may still have some information about it if you find the bootdisk.com drivers work and can't get it set up for DOS.

Matt

 

Since it worked in the other system, all thats left is hardware and software.
you could swap the cable with another one, do a test, Then if still bad clean
the reg Like mattman said. Other than that is beyond me.

luck,
savagcl

 

OK here's the deal.......I've tried everything you guys suggested, except editing the registry....I'm a bit nervous about changing things in there, since I don't know exactly what I'm looking for, and even if I did, I'm not sure what I'd change.
But after plugging/unplugging the cdrom and changing things in the bios and device manager, this is what I've got: with the cdrom plugged in and in safe mode, cdrom is listed in device manager, but no details are available and
cdrom is not listed in windows explorer. also, I have a standard dual PCI IDE controller, as parent device to pri. and sec. IDE controllers, but no details. I can't remove the secondary controller.
After normal boot, the cdrom does not show any where and the secondary controller is also missing.
Back to safe mode, I remove the cdrom and shut down, unplug the cdrom and reboot, then shut down and reconnect the cdrom. Then on normal boot, windows detects the cdrom, and it shows up in explorer and in device manager, and is using the proper I/O and IRQ settings. I put a cd in the tray and can read it....the cdrom works fine now.
Everything looks good right?....NOPE....don't count yer chickens just yet !
Shut down and reboot and guess what, windows again detects the cdrom, it shows up in explorer, but doesn't work and the device manager doesn't list it anymore. So I go to let windows find new hardware and it finds a standard IDE/ESDI hard disk controller. If I let windows install it and reboot, then the cdrom is not detected and doesn't show up anywhere, but that controller is using the I/O and IRQ settings that are supposed to be for the cdrom.
If I don't install it, windows detects the cdrom on every boot and it shows up in explorer, but it doesn't work and it's not listed in the device manager.
Is it possible that the standard dual PCI IDE controller is causing this problem? If so, what will happen if I remove it? ie:the hard drive not be detected?
What if I use the current settings associated with the HD to set the IDE/ESDI controller, and then install another instance of this IDE/ESDI with the settings for the cdrom? or maybe use some other controller for the HD?
Or maybe just clear the cmos and restart the system with everything attached?
What's the most logical thing to do here...what's most likely to work with the least amount of manual reconfigurationating?<-(my new word..hehe)
Thanks again for any ideas.

 

Welderjeffo, Windows is running "standard" drivers for your IDE controller. The motherboard/chipset drivers are not installed. This is the most likely reason why you are having trouble. There may be specific drivers for your motherboard (I do not have much/any experience with Gateway boards). Check if motherboard/chipset drivers are available from Gateway. Do you have the original Gateway "system" disk? It may be the only way to install drivers for that PC.

The www.bootdisk.com startup disk did not work?

I think you need to find the drivers for that PC or, otherwise, if the CD drive is the only problem, try another (more modern?) CD drive.

Matt
PS the Config.sys and Autoexec.bat edits I mentioned are required for Win95 to load "special" drivers (like CDroms that require drivers). No registry edits (you mentioned edits to the Config.sys and Autoexec.bat files in your original question)

 

The whole problem here seems to be gateway....I can't get a newer cdrom to work with this machine....I've tried 2 different drives and I get the same results as with the original mitsumi.
The main board is Intel TE430VX....I have the manual-(from Intel) and all the specs on it but I haven't been able to find the right software for it.....I figure gateway had their own version, which I don't have. And gateway no longer offers support for this unit-(by serial#), but I did find the install program for the gateway PN mistumi drive on the gateway site, but it didn't work properly...it appears to be the same program I've found elsewhere. All it did was copy a couple files into an MTM folder, and add a few lines in the config.sys and autoexec.bat, referring to the mtm files. With those lines in there, windows detects the drive, but doesn't load ANY drivers, so I reverted to the copies I made prior to running the install program because I seem to make more progress with nothing atall listed in there, AND- from what I've been reading, no changes are required in config or autoexec to get the drive working.
As far as boot disks.....I have copies of ALL variations on my HD in my new rig, and have compiled a custom disk for myself with all the best features. I can make the drive work in dos with the use of MSCDEX.EXE, but once windows starts, that's it......the thing won't work.
I did notice that in the adapter.inf file, there are only 5 listed;
sony proprietary, mkepanasonic and then 3 under mitsumi; older single speed, newer single speed, double speed........so I'm very limited in choices of hardware to install manually. I've compared the file with several versions of windows that I have on CDs, and they are the same. Microsoft has a different version of the file in precopy2.cab of W95OEM SR2, but I don't have that CD, so I obviously can't look at it to compare.
I also noticed that the driver 'mtmdai.sys', which is specified as the correct driver, by gateway and mitsumi, doesn't appear in the safe list in Ios.ini. There are several mitsumi drivers listed there, but they are for older drives.
I suspect it maybe listed in Ios.ini from the same W95OEM SR2 cd.
Today I'm going to try to locate these files on an older compaq cd that I have, although it won't be easy since compaq has a unique file structure and their own names for these files.
With any luck, I will find what I need, and from there, I am going to use regseeker to clean the registry, then clear the cmos and try to get it working.
I was able to figure out how to get the secondary ide controller enabled, through a half dozen changes and reboots, so hopefully that won't be a roadblock again.
In the meanwhile, the MB on my other new homebuilt machine went to sleep forever, so I bought a new one and got it installed but I'm having a bit of trouble with a few things, so I have my hands full.
I'll post up my results later tonight or in the morning.
Thanks again.

 

Jeff, good of you to list all that info.
I thought that not being able to get the secondonary IDE controller operational was big part of the problem. It seems that you now have it working.

Try this:
Shutdown and disconnect the CD drive. Boot into Safe Mode and remove the Mitsumi. Boot into normal Windows (to the desktop). Shutdown and reconnect the drive. This should reset the ASPI layer drivers that Windows uses to run these types of drives (Edit: SCSI drives are also run on the ASPI layer drivers. If you have any SCSI drives you will need to disconnect those as well, and maybe ZIP drives as well or other types of drives). You say it should work without installing special drivers, so if those standard IDE controller drivers are adequate, then you may see a difference and hopefully be able to get the drivers to function correctly.

Luck
Matt

 

UPDATE: I'm very close to getting the cdrom working!
I found the following at Intel:
Description
Some versions of Windows 95 may not recognize the IDE controller on Intel motherboards using the 82371SB PIIX3 or 82371AB PIIX4 component. This can cause the BIOS to disable the secondary IDE channel, resulting in IDE devices (such as CD-ROM drives) not being detected or disappearing after the system is rebooted.

Root Cause
The PIIX3 and PIIX4 components are not included in the list of IDE controllers in the MSHDC.INF file shipped with some versions of Windows 95. During installation, these versions of Windows 95 see the IDE functionality but can't identify the exact controller type. Windows 95 enables the primary IDE channel of the 82371SB or 82371AB, but assumes that the secondary IDE channel belongs to a non-plug and play ISA IDE controller. Windows 95 then adds this information to the plug and play configuration area. When the system is rebooted, the motherboard BIOS interprets this information as indicating an ISA IDE expansion card has been installed, and disables the onboard secondary IDE channel -- rendering any devices on this channel inaccessible. The most common symptom is that the CD-ROM drive will not be recognized by Windows 95 after rebooting the system.

Affected Products
This issue affects all Intel motherboard products with the 82371SB PIIX3 or 82371AB PIIX4 component.

Workaround / Action
To determine how the system has been configured, look in the Windows 95 Device Manager:

Click
1. Start
2. Settings
3. Control Panel

# Double click on the System icon, then click on the Device Manager tab.
# Double click on Hard Disk Controllers.

If you see the following drivers listed, the system has NOT been configured correctly:
Hard Disk Controllers
* Primary IDE Controller (single FIFO)
* Standard Dual PCI IDE Controller
* Standard IDE/ESDI Hard Disk Controller

An Install Wizard has been developed that adds an entry for the PIIX3 or PIIX4 IDE controller (as appropriate for your motherboard) into the MSHDC.INF file.
So I have that much straightened out, but now I've got a problem with the PCI host bridge. Windows detects it on boot and installs a default driver for it and it doesn't work properly. Gimme another week or so and I'll have it fixed.
(I hope)
Thanks for all your thoughts and suggestions.

 

Jeff, some good detective work.

I might speculate here, anyway...
"Phantom" ISA controllers? You may have a (minor) resource problem now. If you are running any ISA cards, I would take the cards out and remove the drivers. Windows may now need to reallocate all the resources. When you have the PCI host controller working, reinstall the ISA cards.

Go to Safe Mode and look through the lists of drivers for long lists of multiple entries or entries related to ISA when you have removed the hardware. Remove anything you know should not be there by using the Windows IDE controller modifications.

You could try changing the resources the PCI host controller uses (read under "resouces" in the Start>Help menu). If there is no change, put them back to standard.

Hope it may be it few days, not weeks.
Matt

 

Matt,
No extra entries in Dm in safe mode and windows doesn't point out any conflicts. And I checked each item with my own eyeballs, just to be sure. I also checked to make sure the proper resources are being used by each item, according to the MB & chipset manuals. The only thing that doesn't jive is the PCI host bridge......it shouldn't be there, but as soon as I remove it and reboot, windows detects it and reinstalls. I tried some resource shuffling to no avail, and I got the blue screen of death a few times, so that's out.
I tried physical removal of the sound card (isa), which doesn't make any difference, but I can't really take out the video(pci) as there's no video on the mainboard.....all I can do is cancel installation when windows starts.
I figure the bios is being fooled by the hardware because windows doesn't properly recognize the chips, or vice versa, which is what I thought about the original problem, and finally confirmed when I stumbled onto the page that Intel had stuffed into the deepest, darkest corner of their site.
Thank god MS has a better working relationship with manufacturers nowdays.
Anyway, I'm back to looking at INF's.....the Intel fix was supposed to modify several, but I found only one>Mshdc.inf< was actually modified.
The chip configuration isn't listed in the adapter.inf, machine.inf, ihost.inf, maybe a few others as well, but I haven't figured out which ones I need to modify. (or which ones I'm missing) I compared some to those for W95b and see the proper configuration listed in a few, but I'm not sure W95b INF's will work with W95a, so it pretty much comes down to manually editing each INF until I get a combination that works.
My searches produce interesting results, but most are links to pages that aren't there anymore. Nobody supports this rig anymore, and I guess Intel never really did anyway, since they only custom manufactured this board for Gateway....and Micron>(I found the manuals in their dungeon).
Intel doesn't support any older than the 430TX, which was the next step above the 430VX....the only real differences between the two is a minor variation in the chipset and the VX is stripped down.
Anyway, I think the only other options I have are: Try the W95b INF's, or remove windows and pre-install software for the chipset, or try to scrap W95 altogether and try to install W98>(which I don't think will work since I can't find a newer bios).
This is presuming I won't be lucky enough to find someone who has some of the original Gateway software.....no luck so far.
If you think of anything else....let me know.....I really appreciate the help.

 

Might help, might not :
If it is detecting the PCI host bridge, it probably should be there. I reinstalled a video card today and on reboot it asked for drivers for the PCI host bridge. Let's hope your's does not need a specialized Gateway driver. (BTW, what errors show for PCI host bridge?)

I haven't tried editing INFs (interesting concept though ). If you can see the correct configuration in 95b, right-click on the .inf and select install. That should put the driver information into the "list" of selectable drivers. Remove the drivers for the hardware (host bridge). When you reboot, select the "install from list of drivers" radio button. Find and highlight the driver and OK that. When it asks for the drivers disk, put in the Win95b disk instead of the 95a. I've had this work for me for Win98/Win98SE. There should not be any distinction between Win95a and 95b, as far as the hardware manufacturers are concerned I would say they are virtually the same version, updated drivers were added to the later editions.

You should not have trouble installing Win98 (I don't see why you would need a BIOS update, unless you know something special about that machine that I wouldn't). In the system requirements Win98 should run on a 486 PC. Although, you may still need the Gateway software. I would only try to upgrade if there were no other alternatives.

Hope you hit it.
Matt

 

Matt,
First off, I don't see any errors/conflicts showing anywhere. But if the pci host bridge is installed correctly, I think it should be listed as;
"Intel 82371SB pci to cpu host bridge "
or something similar, but it is not. It's either not there-(if I cancel install) or it's listed as "pci standard host cpu bridge "-(if I let it install)
Either way, everything else seems to be working properly, except for cdrom, which is visable but doesn't work. A click on it says D is not accessible, like there's no cd in the tray, even though there is. Prior to the INF edits, I had it reading CDs....at least until reboot, when the drive would disappear.
And then there's a minor problem with the display, (matrox mga pci card)> but I'll get back to the video issue in a minute.
I'm sure that only part of the software for the MB chipset is installed, but I'm not sure if I even have all of it....possible incomplete program from Intel?
Whenever windows complains about the host bridge, there is no button for "let windows find the best driver.... ", standard is the only choice.
That tells me at least one INF is lacking an entry, has an error, or I'm still missing one. "ihost.inf" maybe one to concentrate on, I have a copy from intel but for some reason doesn't seem to be doing the trick. (I pasted a copy down below) It seems like the INF's are key to the whole problem.
Anyway, I can't install from manufacturer disk,(since I don't have one) and the only other options are browse or cancel.
If I browse for the driver, I can get to my Intel folder, but I can't scroll through the list to see what's there, it only highlights the first one in the folder.. ..almost as if it freezes. It makes no difference if I'm browsing the HD or a floppy. But even if it didn't freeze, I would have to try each one out of over 100, until I got one that works, and delete each one as I go. It would be extremely helpful if I knew the exact name, I could put it on a disk and be done with it.
I haven't had any luck finding applicable information on this topic, but I finally found and downloaded a bios upgrade last night, which supposedly has added support for busmastering and some other issues that maybe relevant to the problem.....it was originally published by gateway, but I downloaded it from some hole in the wall.....gateway doesn't have it anymore.
That might cure part of the problem, but I'm a little nervous about it, as I have no way of knowing the quality of the file unless I try it.
There is a bios recovery jumper on the MB, so I'm compiling a program right now that should restore the current bios if something goes wrong with the upgrade. As soon as I have that done, I'll proceed with the upgrade.

Now for the video issue, drivers seem to be installed and working properly, there are no conflicts, but there is a minor problem.
Note; I installed software from intel for the MB before I installed software for the vid card. Both the card and installation disk are direct from gateway, and specifically for this unit. The display was extremely poor until I ran the disk.
After install, I made the following observations;
If I let windows install the pci standard host bridge,
the display on the monitor shifts right, with 1/2" wide black strip at left.
If I cancel windows install of the pci standard host bridge,
the display on the monitor shifts left, with 1/2" wide black strip at right.
Whatever that means, if anything, is beyond me, but it sure is strange.

I'll just keep on searching and experimenting, installing, rebooting, uninstalling, removing, rebooting and go back where I started and do it again.
Sounds like a song don't it?.......if I had time to play my guitar, I might have a top ten hit here!

Oh, one comment about editing INF's.......it works! but use caution because those harmless looking files WILL change the registry! one mistake in an INF creates another mistake in the registry....multiplying the problem.

Here's the copy my newly aquired "Ihost.inf "
note;
my board is an 82430VX consisting of;
82371SB pci/isa ide xcelerator- PIIX3 bridge
82437VX tvx accelerated controller
two 82438VX tdx data path components
SMC FDC37C932FR (smc93x) ultra I/O controller
-------------------------------------------------------------------------------------------------
****************************************************************************
; ****************************************************************************
; ** Filename: IHOST.INF
; ** Abstract: Windows* 95 INF Update File for Intel(r) 82371SB, 82439TX
; ** and BX/DX/EX/GX/LX/ZX Chipsets
; ** Last Update: June 14, 1999 (Version 1.65)
; ****************************************************************************
; ****************************************************************************


[version]
LayoutFile=layout.inf
signature= "$CHICAGO$ "
Class=System
ClassGUID={4d36e97d-e325-11ce-bfc1-08002be10318}
Provider=%INTEL%
SetupClass=BASE

[ClassInstall]
AddReg=System_Class_Reg
DelReg=System_Class_DelReg

[System_Class_Reg]
HKR,,,,%SystemClassName%
HKR,,Installer,,sysclass.dll

[System_Class_DelReg]
HKR,,NoInstallClass

[Manufacturer]
%INTEL_MFG%=INTEL_SYS

[INTEL_SYS]
%PCI\VEN_8086&DEV_7000.DeviceDesc%=ISA_DRV,PCI\VEN_8086&DEV_7000
%PCI\VEN_8086&DEV_7100.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7100
%PCI\VEN_8086&DEV_7180.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7180
%PCI\VEN_8086&DEV_7181.DeviceDesc%=AGP_BRIDGE_DRV,PCI\VEN_8086&DEV_7181
%PCI\VEN_8086&DEV_7190.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7190
%PCI\VEN_8086&DEV_7191.DeviceDesc%=AGP_BRIDGE_DRV,PCI\VEN_8086&DEV_7191
%PCI\VEN_8086&DEV_7192.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7192
%PCI\VEN_8086&DEV_71A0.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_71A0
%PCI\VEN_8086&DEV_71A1.DeviceDesc%=AGP_BRIDGE_DRV,PCI\VEN_8086&DEV_71A1
%PCI\VEN_8086&DEV_71A2.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_71A2


[ISA_DRV]
AddReg=ISA_DRV_AddReg,System_Dev_Properties_AddReg

[ISA_DRV.NoResDup]
*PNP0A00

[ISA_DRV_AddReg]
HKR,,DevLoader,,isapnp.vxd
; Devices specific settings (value name is DevID cat with VenID)
; Bit 0: Devices video wanting no IRQ
; Bit 1: Devices PCMCIA wanting IRQ
; Bit 2: Devices Dual PCI IDE without programming code with bit 3 set
; Bit 3: Devices needing no enum at all
; Bit 4: Devices needing no resources but having garbage in base address registers
; Bit 5: Devices needing dword access
; Bit 6: Devices being single function parading as multiple functions
; Bit 7: Device always enabled
; Bit 8: Device is IDE even though not class code of 0101
; Bit 9: Device is video even though not class code of 0001 or 03xx
; Bit 10: Automatically fail to start the device. It is not supported in pmode
; Bit 11: Device can only appear on bus 0 (improperly decode type 1 transactions)
; Bit 12: Device can only appear on dev <16
; Bit 13: Bridge device can only have children at Dev0
; Bit 14: Do not modify the command bits of the device
; Bit 15: Device is VGA even though not class code of 0001 or 0300 (only has meaning if bit 9 is set).
; Bit 16: Device is MF CardBus controller that shares Command register
; Bit 17: Device is a PCI/PCI bridge with straight thru routing (pin A to pin A, etc).
; Bit 18: Device is a subtractive decode PCI-PCI bridge with writable IO window
HKLM,System\CurrentControlSet\Services\VxD\PCI,70108086,1,04,00,00,00


; IRQ Miniport Data
;

HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\70008086,Name,, "Intel(r)82371SB "
HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\70008086,Path,, "PCIMP.PCI "
HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\70008086,Instance,1,01,00,00,00

;
; IDE Miniport Data
;
HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\70108086,Name,, "Intel(r)82371SB "
HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\70108086,Path,, "PCIMP.PCI "
HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\70108086,Instance,1,00,00,00,00

HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\71118086,Name,, "Intel(r)82371AB/EB/MB "
HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\71118086,Path,, "PCIMP.PCI "
HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\71118086,Instance,1,00,00,00,00


[System_Dev_Properties_AddReg]
HKR,,EnumPropPages,, "sysclass.dll,EnumPropPages "

[NO_DRV]

[AGP_BRIDGE_DRV]

[ControlFlags]
ExcludeFromSelect=PCI\VEN_8086&DEV_7000
ExcludeFromSelect=PCI\VEN_8086&DEV_7100
ExcludeFromSelect=PCI\VEN_8086&DEV_7180
ExcludeFromSelect=PCI\VEN_8086&DEV_7181
ExcludeFromSelect=PCI\VEN_8086&DEV_7190
ExcludeFromSelect=PCI\VEN_8086&DEV_7191
ExcludeFromSelect=PCI\VEN_8086&DEV_7192
ExcludeFromSelect=PCI\VEN_8086&DEV_71A0
ExcludeFromSelect=PCI\VEN_8086&DEV_71A1
ExcludeFromSelect=PCI\VEN_8086&DEV_71A2


[Strings]
SystemClassName = "System devices "
INTEL = "Intel "
NULL = " "
WINBASE = "Base Windows Components "
SRCPATH = "Distribution directory "

INTEL_MFG= "Intel "

PCI\VEN_8086&DEV_7000.DeviceDesc= "Intel(r) 82371SB PCI to ISA bridge "
PCI\VEN_8086&DEV_7100.DeviceDesc= "Intel(r) 82439TX Processor to PCI bridge "
PCI\VEN_8086&DEV_7180.DeviceDesc= "Intel(r) 82443LX/EX Processor to PCI bridge "
PCI\VEN_8086&DEV_7181.DeviceDesc= "Intel(r) 82443LX/EX Processor to AGP controller "
PCI\VEN_8086&DEV_7190.DeviceDesc= "Intel(r) 82443BX/ZX/DX Processor to PCI bridge "
PCI\VEN_8086&DEV_7191.DeviceDesc= "Intel(r) 82443BX/ZX/DX Processor to AGP controller "
PCI\VEN_8086&DEV_7192.DeviceDesc= "Intel(r) 82443BX/ZX/DX Processor to PCI bridge "
PCI\VEN_8086&DEV_71A0.DeviceDesc= "Intel(r) 82443GX Processor to PCI bridge "
PCI\VEN_8086&DEV_71A1.DeviceDesc= "Intel(r) 82443GX Processor to AGP controller "
PCI\VEN_8086&DEV_71A2.DeviceDesc= "Intel(r) 82443GX Processor to PCI bridge "

; Copyright (c) Intel Corporation, 1998-1999
; Copyright (c) Microsoft Corporation, 1993-1995

; ************************************************************
; Intel is making no claims of usability, efficacy or
; warranty.
; ************************************************************
; Information in this document is provided in connection with
; Intel products. No license, express or implied, by estoppel
; or otherwise, to any intellectual property rights is granted
; by this document. Intel assumes no liability whatsoever,
; and Intel disclaims any express or implied warranty,
; relating to sale and/or use of Intel products including
; liability or warranties relating to fitness for a particular
; purpose, merchantability, or infringement of any patent,
; copyright or other intellectual property right. Intel
; products are not intended for use in medical, life saving,
; or life sustaining applications.

; ************************************************************
; Intel Corporation disclaims all warranties and liabilities
; for the use of this document and the information contained
; herein, and assumes no responsibility for any errors which
; may appear in this document, nor does Intel make a
; commitment to update the information contained herein. Intel
; reserves the right to make changes to this document at any
; time, without notice.
; ************************************************************
; ************************************************************

; * Third-party brands and names are the property of their
; respective owners.
-------------------------------------------------------------------------------------------------

Keep the ideas coming, I really appreciate it.
Thanks

 

Jeff, running VERY low on ideas now

I am not sure of the effects of the edits. I have only ever installed or removed drivers.

I am not sure about reading INFs, but from your post, your chipset might appear to be a VX. VX is not mentioned in the install instructions.

A trick (maybe ) if you are installing the drivers and Windows asks for which drive to search for driver files, uncheck all the drives (checkboxes). If the original drivers are in the Windows\System folder, it will try to find them there.

The Gateway machine that I have worked on was

Let us know if you have any successes.
Matt

 

Matt,
I know....this rig is *******.
You're right about VX...
The chipset is identified as "7000 ";
%PCI\VEN_8086&DEV_7000.DeviceDesc%=ISA_DRV,PCI\VEN_8086&DEV_7000

There seems to be another part of the puzzle missing, I believe it's identified as "7010 ". I haven't figured out where that entry is needed, or why.

There maybe yet another entry missing, something that gateway added, but what, is beyond me.

Now to complicate things, I'm working 12 hour second shifts now, and my mind is spent when I sit down and try to concentrate on this. Maybe I'll make some progress this w/e.

Thanks.

 

As a once upon a time Gateway tech I can assure you that if the PIIX3 or PIIX4 busmastering drivers are not installed properly you will have nothing but grief.

First off I need to know which version of W95 - W95sr2B the OEM only release that supports FAT32 has built in PnP support for PIIX / PIIX3.

Likely your system is a PIIX4 and you will need this driver file 7502700.exe Its a self extracting zip with like 3 files. That page will also have a link How to install. Read that also - not all applies to your since you are not doing a clean install (but you might consider it - and I can give you a much faster/safer install method)

Post back if you need more help.

GAB

Edit: After re-reading above I'm sure your system is a 440LX which is PIIX4.

 

Profgab101,
Thank god you know something about Gateway.
However, I don't think I've got the LX.... PIIX4, but please correct me if I'm wrong.
I already investigated the driver file #7502700 that you mention. It doesn't list my MB G2K# MBDPCI023ABWW as applicable.
Using #'s right off the chips, it's ID'd as a Intel TE430VX board, code name "tiger eye ":
Intel 82430VX-PCI chipset/ 430VX Triton III
Intel 82371SB-PCI/ISA IDE xcelerator-PIIX3 bridge
Intel 82437VX-TVX accelerated controller
Intel 82438VX-TDX data path components
SMC FDC37C932FR-ultra I/O controller
I'm sure it was customized for Gateway, since it's lacking several other chips and features that were available from Intel. There's no USB, or onboard video for that matter.
BTW, the video is a Matrox MGA Mystique, PCI card, which I'm guessing must have been standard, it's labelled the same as the machine serial # 0006166339.
The sound card is Ensoniq soundscape vivo90, G2K#SNDCRD010AAWW.
The cdrom is Mitsumi FX120T, G2K#SDRIDE033AAWW
I've got an AMIbios upgrade 1.00.08CY1T installed, from the original 1.00.06CY1T.
I've got windows 95a(sp1) installed now, it's the only version that I have on floppies.
To be honest, I don't know if I originally had 95, 95a or 95b.
I've got 95,95a,95b,98se,XP on cd's but I don't have any gateway version of windows. I'm not opposed to doing another clean install, that's gravy IF I can get the cdrom to read the cd. Otherwise, I'll have to make a set of floppies from the cd, but I've never tried that before, so I don't know how difficult it is, as far as to label all the disks in the chain.
Is there anything else I can tell you to help you help me?
Thanks.