Dell Latitude D600 Windows 98 Drivers
When I went to the Dell support web site, I found only Intel Mobile Chipset drivers Windows 98 drivers for the Latitude D600. The video chip is. To view all drivers for your Latitude D600. Dell Latitude D600 Series Version. The file D600A16.EXE is using the Universal (Windows/ DOS) format and is designed to be directly executed from Windows environment. Click Download now. The File Download window appears.
All the drivers posted here were located through extensive google searching and vogons.org user JiaoTongNan, MSFN.org users PROBLYMCH3LD, stupendousyappi, Dell user Griz UK, Dell does not support Windows 98SE or Windows Me on this laptop model.DISCLAIMER:Both Windows 98SE and ME have been tested with and work with these drivers. If you encounter missing CD drivers when installing 98SE, you'll have to devise a way to get the motherboard driver into the hard drive so 98SE can install it and get the CD drive working, be it editing the hard drive externally or installing an inappropriate CD driver.Most of the drivers make no mention of Windows 95 or Windows 98FE, I have no idea if those will work.Dell has offered the Dell Latitude D600 with a few variations, some models of the Dell Latitude D600 may come with a Intel Pro 2200 Wireless Card instead of a TrueMobile 1300 or 1400, which is incompatible with Windows 9x. Many drivers and instructions here apply to other Dell Latitude Dxxx family models, like the D610, but Windows 9x will only work properly with the D610 models that contain an ATI X300 graphics card as there is no Windows 9x video driver for Intel GMA 900.
Scroll to the very bottom to check compatibility if you're considering installing 9x on a Latitude Dxxx model.DOWNLOAD:Drivers includedMotherboard (Intel 855PM infinstautol.exe infinstenu.exe)Video (radw9xomega2637)Sound (Sigmatel C-Major.exe)Ethernet (Broadcom BCM5787)Wireless (Broadcom 43xx + boingo wireless + mcafee + buffalo)Cardbus Driver (FTSPCCardO2Micro®SmartCardBus®Reader20782)USB Driver - Windows 98SE only! (nusb33e)VDMSound 9x (May not work, included because the sound drivers don't natively support DOS)Windows 98SE Unofficial Service Pack (U98SESP3)Not includedModemWireless Utility (Required for WPA2): download.juniper.net/software/aaa802/public/oac/452/OdysseyClient9x.exe(Generate a trial key!)(Maybe important to know if you plan on buying it)INSTRUCTIONS:Included with the.zip file.
I left the names of the drivers unedited so they are more recognizable.Out of all the drivers, the broadcom wireless was the hardest to find. The DVD Drive is my only remaining problem besides my cardbus (Wireless Laptop Notebook Adapter) the model is Linksys Wireless-G WPC54G. After installing the utility software (Had to transfer it by flash drive since my DVD drive wouldn't work in WinME) I'm getting issues during bootup about the cardbus and cardbus bridge driver. I'm receiving a 'The file 'carddrv.exe' was not found' error, I played around a bit and used the carddrv.exe file found in WinME's C:/Windows/System, but that only made me realize its the default, generic driver which doesn't work.
I tried ripping the files from my installation disc for the cardbus, but telling Windows to search in there doesn't help either.I'm not sure if I'm supposed to keep the Cardbus plugged into the slot during bootup, the manual seems to tell me to (D:) and its the only way the cardbus obtains power and LEDs turn on. There's still an issue, my cardbus is preventing Windows from properly booting if kept in before boot or inserted during boot. The laptop will hang if I insert midway boot and if I insert it before booting, the Windows ME screen will load, but afterwards the screen will become completely black, with a movable cursor.(I apologize if my grammar/spelling is really terrible, its late where I am atm)I tried Windows 98 again, that DVD drive oddly refuses to work with Windows 98 or ME.It works completely fine up until the operating system loads.Would an external DVD player be a good idea?Edited April 4, 2016 by ♥Aiko♥Chan♥. OK.I actually haven't used the DOS 7.1 CD install disk, I just always use the floppy disk.
Do you have the floppy drive module for this laptop? In that case it would be easier.Otherwise you can do this: (somebody who knows how this disk works please demonstrate a more efficient way.) This is what I always do when installing DOS since I'm in complete control over exactly what gets installed and where. It's not very efficient though.1. Boot with the CD, but as soon as the BIOS disappears hit F8 multiple times as fast as you can This will bring up the DOS manual boot settings screen.
Hit Shift+F5 to exit to the command prompt. You should see an A: or a D: prompt, depending on how that CD works.2. Now you need to partition and format your hard drive. Run FDISK (this might not be in the current path; you can check around the disk. There might be two drives, A: and D:, or there might be just one. Either way, FDISK will be in the DOS or SYSTEM folder.) Now that you're in FDISK, check the hard drive partition settings.
Delete all of the existing partitions. Now create a new 'primary' partition with the maximum size and make it active.
Now reboot the system and repeat step 1.3. Now format the c: drive by running the command 'format c:'. This takes a long time.4. Now run the command 'sys a: c:'. (if this doesn't work run 'sys d: c:' instead.) Same thing as FDISK, it might be in the DOS or SYSTEM folder if it doesn't run automatically.5. Now your hard drive is formatted with the bare-bones system files.
Next you install the drivers you need:6. Make a folder called DOS on the C: drive.7. Find the DOS or SYSTEM folder on the CD. Copy the following files to the C:DOS folder:-HIMEM.SYS (XMS memory driver)-EMM386.EXE (EMS memory driver)-VIDE-CDD.SYS (CD driver, part 1)-SHSUCDX.SYS (CD driver, part 2)-EDIT.COM (text editor)8. Now, using EDIT, create two files in the root of the C drive: CONFIG.SYS and AUTOEXEC.BAT.
These will instruct DOS to load those drivers you copied earlier. The contents of CONFIG.SYS need to be as follows:DEVICE=C:HIMEM.SYSDEVICEHIGH=C:EMM386.EXEDEVICEHIGH=C:VIDE-CDD.SYS /D:IDE-CDDOS=HIGH,UMBThe contents of AUTOEXEC.BAT are as follows:@ECHO OFFPATH=C:;C:DOSSHSUCDX /D:?IDE-CDThat's it!
Reboot your computer without the CD in the drive and the hard drive should boot up to the DOS prompt, and you should be able to read any CDs you put in by going to the D: drive.If you want I can explain to you exactly what all of those commands above mean and what the drivers do:-DNow you can follow the rest of my instructions above to install Windows 98.(somebody please tell me if any of this information is wrong) Edited April 5, 2016 by ♥Aiko♥Chan♥. I too worked with the dell latitude d600 on 98SE, i got all drivers to work, except for the pci cardbus bridge 'PCIVEN1217&DEV7112' or 7113 and cardbus controller 'O2Micro-SmartCardBusReader-2E10', i tried like the oldest drivers for both, 2-26-02 or somewhere around there for the cardbus bridge and the other one was,1.03.00.00, but i may have not properly installed the drivers, at least for the cardbus controller portion, i believe that for the 'O2Micro-SmartCardBusReader-2E10' portion, you have to first install scbase.exe, then smclib.exe, then other steps to get it working. For the cardbus bridge, probably have to run o2update.exe to get it work, but i don't know for sure on the process, maybe the drivers arent compatible.
I don't get it. If you already HAD the OS installed, then all you needed to do was to begin at Step #6 (skip steps 1-5) in order to load CD/DVD Driver software. You can do that anytime on a running OS.
You don't need to do anything with a Floppy. Boot Disks Images can be obtained with those drivers (etc) and extracted via WinImage (in the running OS) and proceed from there.HTHSadly that isn't the case with Windows 98SE. Due to lack of chipset drivers (Although there are modded ones capable of installing) and USB support on 98SE, its not even possible to do anything after installing on my laptop.
The DVD drive won't be recognized unless I upgrade from DOS 7.10 that has a CD-Rom driver. I could do that with Windows ME, but I didn't realize all it took was a proper chipset and reassigning of resources to stop conflicts. I'm currently reinstalling Windows ME.
Lately I've been asking on another forums for help and so far problem after problem keeps coming with Windows 98SE (Although I probably didn't use the proper chipset driver). I too worked with the dell latitude d600 on 98SE, i got all drivers to work, except for the pci cardbus bridge 'PCIVEN1217&DEV7112' or 7113 and cardbus controller 'O2Micro-SmartCardBusReader-2E10', i tried like the oldest drivers for both, 2-26-02 or somewhere around there for the cardbus bridge and the other one was,1.03.00.00, but i may have not properly installed the drivers, at least for the cardbus controller portion, i believe that for the 'O2Micro-SmartCardBusReader-2E10' portion, you have to first install scbase.exe, then smclib.exe, then other steps to get it working. For the cardbus bridge, probably have to run o2update.exe to get it work, but i don't know for sure on the process, maybe the drivers arent compatible. Im confused, are you trying to get wireless connection on the broadcom 94306mp or dell truemobile 1400? I've used the bcm94309mp like you mentioned, there is also the 94306mp, and other cards like the intel 21003a or 3b ( not sure on which one ), also the actiontec 802mip mini pci card works. Usually, the utilities that come with the driver packages should let you find a network to connect to, but it is possible to use a seperate one such as wsc gaurd 4.0, allows up to wpa encrypted networks if the wifi card supports it, the utility doesn't work for all network cards.
I am using the 'bcm94309mp' card A.K.A Dell True Mobile 1400 wireless internet. Any help is appreciated! I couldn't get any packages to work with mine that said Windows 98 compatible so, I ended up using this. Tion/2909/ (Broadcom BCM57xx). It was the only thing that let my laptop recognize my card, but my driver has an issue in device manager and I don't have any utilities to manage internet connections! Please link me to any working drivers for utility or the driver used to make wireless internet work!I have no other option for wireless internet besides a cardbus, which did not turn out well.
Even after getting the CD drive working and making sure there were no conflicts in the hard drive or something like that, my Linksys WPC54G card bus will keep asking me for a location for drivers.Edited April 8, 2016 by ♥Aiko♥Chan♥. The DVD drive won't be recognized unless I upgrade from DOS 7.10 that has a CD-Rom driver.Again, I don't get it. All you need are the listed files and the modifications to AUTOEXEC.BAT and CONFIG.SYS. I've done this many times. It's the same principle as DOS and Windows 95 (which used DOS drivers).
You do.not. have to install the way that website stated. That's just dumb!And according to this, there's Intel Chipset drivers that should work (no hacking?).DVD Drive or CD Drive (you've stated both)? Which Chipset Drivers are you using?Edited April 8, 2016 by submix8cAnother Q.
I quickly determined it by looking hereAh, it looks like I made another mistake (darn it, I'm on a streak of mistakes). Didn't check closely enough if the D410's video driver was 98 friendly.Actually there are drivers for the 900 series (910, 915, and 925) if I'm not mistakingCorrect me if I'm wrongAs previously stated - There is NO Intel chipset support for the 900 series in Windows 98. You can download Intel drivers that say they do, but the.inf doesn't have the correct instructions, and the.cab files are invalid. As previously stated - There is NO Intel chipset support for the 900 series in Windows 98. You can download Intel drivers that say they do, but the.inf doesn't have the correct instructions, and the.cab files are invalid.Just what 'instructions' does the 915 INF not have that, say, the 865 ones do? Intel's chipset drivers are essentially a set of glorified text files that only give proper names to their respective onboard devices. An OS can run just fine without these in any case.
I don't remember anything being different about the 915 INF when I made my unofficial INF drivers for 9xx and later chipsets.You are correct however that the download linked by ♥Aiko♥Chan♥ does not support Windows 9x at all. This is a mistake made by Intel, either inadvertently or purposely. The last 9x compatible version is 6.3.0.1007. It does contain a 915 INF but 925 is not covered.
Dell Latitude D600 Audio Driver
Not sure about 910. Just what 'instructions' does the 915 INF not have that, say, the 865 ones do?
Intel's chipset drivers are essentially a set of glorified text files that only give proper names to their respective onboard devices. An OS can run just fine without these in any case. I don't remember anything being different about the 915 INF when I made my unofficial INF drivers for 9xx and later chipsets.You are correct however that the download linked by ♥Aiko♥Chan♥ does not support at all. This is a mistake made by Intel, either inadvertently or purposely. The last 9x compatible version is 6.3.0.1007. It does contain a 915 INF but 925 is not covered.
Not sure about 910.The security catalogs in the Win98 folder for the 915 are not recognized as such (invalid), and the chipsets are not updated when installed. I've tried these.inf on some Dells like the D610, and I couldn't get the USB to work the way it was suppose to, among other things, even with the Unofficial Universal USB 2.0 Stack installed.
I would welcome a chance to try the ones you've modified. It would be very cool to get the D610 working with Windows 98! The security catalogs in the Win98 folder for the 915 are not recognized as such (invalid), and the chipsets are not updated when installed. I've tried these.inf on some Dells like the D610, and I couldn't get the USB to work the way it was suppose to, among other things, even with the Unofficial Universal USB 2.0 Stack installed.
I would welcome a chance to try the ones you've modified. It would be very cool to get the D610 working with Windows 98!I've never tried to actually run the installer on a 915 chipset system so I'm not familiar with the behavior there.
I know it works on the 875 chipset despite it not being specifically named 9x compatible (although the 875 is not much different from the 865, which is named-supported).You could try running the SETUP or extracting it to a folder and then manually use the 98SE Device Manager to update the driver for the 'System Management BUS Controller'; pointing the driver dialog to ICH6CORE.INF and see what happens. 915.INF and 915M.INF will contain some of the devices as well.The security catalogs are pretty useless in all honesty. Probably all they would do in this case is verify the checksum of the INF file against the original one created by Intel. These are also unnecessary to make an OS run on a given set of hardware.
Having a 'working' chipset driver does not guarantee that the OS will run any smoother. In my experience Windows 98SE starts to have problems with ICH6 (9xx) and later chipsets when trying to run using ACPI. Usually it is necessary to run SETUP using the '/p i' switches to disable ACPI and thus prevent various instabilities. It is possible the USB problems you saw were caused by ACPI as I have seen this on newer systems.I have an HP ZD8000 laptop which uses the 915 chipset as well. I have had issues getting 9x to run properly on it but the main problem is the ATI Mobility Radeon X600 graphics chip rather than the motherboard chipset.In any case my unofficial Windows 98SE chipset drivers for 9xx and later Intel systems are.
I've never tried to actually run the installer on a 915 chipset system so I'm not familiar with the behavior there. I know it works on the 875 chipset despite it not being specifically named 9x compatible (although the 875 is not much different from the 865, which is named-supported).You could try running the SETUP or extracting it to a folder and then manually use the 98SE Device Manager to update the driver for the 'System Management BUS Controller'; pointing the driver dialog to ICH6CORE.INF and see what happens. 915.INF and 915M.INF will contain some of the devices as well.The security catalogs are pretty useless in all honesty. Probably all they would do in this case is verify the checksum of the INF file against the original one created by Intel. These are also unnecessary to make an OS run on a given set of hardware.
Having a 'working' chipset driver does not guarantee that the OS will run any smoother. In my experience Windows 98SE starts to have problems with ICH6 (9xx) and later chipsets when trying to run using ACPI. Usually it is necessary to run SETUP using the '/p i' switches to disable ACPI and thus prevent various instabilities. It is possible the USB problems you saw were caused by ACPI as I have seen this on newer systems.I have an HP ZD8000 laptop which uses the 915 chipset as well.
I have had issues getting 9x to run properly on it but the main problem is the ATI Mobility Radeon X600 graphics chip rather than the motherboard chipset.In any case my unofficial Windows 98SE chipset drivers for 9xx and later Intel systems are.has the Windows 98 drivers for ATI Mobility Radeon X600. There is no.inf file in the exe file LoneCrusader indicated. So we are back to my original statement. Would love to hear from someone who has made Windows 98 work fully on Intel 915GM. I have read posts on different forums going back more than 10 years, hasn't been done.Are you sure you know what you're doing? Of course there are INF files in the package!
Windows 98 Drivers Downloads
You can't just play around looking at the file with 7-Zip or whatever, you have to run it to extract them. Examine the 'Command Line Flag Options' in the README if you need a command to extract it without installing it. Well I'm sorry if you thought I was implying anything other than what was stated. I did not state that you don't know what you are talking about, nor did I say anything about being mislead. Don't know where you got that from, but neither was I the first who got snarky.
Maybe you thought I was talking about your modded files. Perhaps you are used to replying only to comments taken out of context. Not trying to start a flame war here. Yes, I have run these files, and I have folders with the extracted files.
Dell Latitude D600 Drivers
I was strictly referring to the 900 series files, not the 800 series. The 900 series were the ONLY files I referred to.
I am looking for files with enough support to provide a fully working Windows 98 system under Intel 900 series chipsets. I still stand by my previous statement - Would love to hear from someone who has made Windows 98 work fully on Intel 915GM. I have read posts on different forums going back more than 10 years, hasn't been done.
I've read those who have used Scitech drivers, virtual machines, etc. Generally with follow-up posts about how much WASN'T working after the fact. People been working on these issues since the time when Windows 98 was STILL being supported by Microsoft. I guess that since even with your modded drivers that you're not seeing 100% success, it ain't gonna happen. Maybe I'll just set up these Dell D610s I have as Linux machines or Hackintoshes. Thanks for your input. Most of the issues with 98 on a 915 or later chipset can't be fixed or helped by just having INF files.
As I said the INF files only give proper names to the 'generic' devices already installed by the OS during SETUP. Sometimes they will eliminate unknown devices such as 'PCI System Management Bus' but all the INF does is give it a name - it doesn't load any files or set any configuration data for the device. Note that no.SYS,.VXD,.PDR,.MPD, or other actual 'driver' files are contained in any of the Intel chipset packages. The only device in these INF's that actually causes a file to be loaded is the 'LPC Controller' which is a legacy bridge providing compatibility with older BUS'es such as ISA. The LPC Controller entries cause ISAPNP.VXD to be loaded, but this file is already present and loaded to begin with.The real 'compatibility' issue with 9xx and later chipsets under Windows 9x lies in how the motherboard BIOS is set up; what options it has and how it manages the system.
For example I have an Intel-branded Intel-BIOS 965 chipset board that has some issues when trying to run 9x. However a Gigabyte-branded AWARD-BIOS 965 chipset board works fine. Now as we both know laptop BIOS'es are always 'proprietary' as intended by their manufacturers and usually severely limit the options available to the end-user, this presents a problem when one wants to use the laptop in any fashion different from the one intended by the manufacturer. These proprietary BIOS'es tend to cause various conflicts, especially when running Windows 98 with ACPI enabled. Also, a big hurdle to compatibility with laptops using the 915 and later chipsets is the various other integrated devices.
The ATI Mobility Radeon graphics chips are obviously problematic in some configurations (I've seen reports of the Dell version of this chip working with 9x but the HP version in my ZD8000 does not. It won't even work with VBE9X.) and I don't know if any available NVidia-based Mobile cards work any better, and in any case they are usually not user-replaceable. I believe I have actually found 9x drivers (not tested them all yet) for every single device in my ZD8000 except the video.
SciTech Display Doctor does work on it, but I can't set the screen's native resolution of 1440x900 without it trying to go into some kind of 'panning' mode, and when SDD is installed it breaks Plug & Play which means USB Flash Drives don't work when connected. Anyone who knows how to fix this problem with SDD please chime in.I have attached the 915 Chipset/ICH6 files extracted from the package I linked previously. This is the extent of Intel's support of the 915 Chipset under 98SE/ME. My unofficial INF's can be used to identify any other 9xx devices on the 915 laptops should they not be covered by the official files.