bizzybody

Is there any way to make Windows actually use the MRU lists in the Registry when it goes looking for its own installation files and other things like driver files? All the MRU lists are used for is to fill in the drop list Windows asks the user to chose from (or Browse) when it gets amnesia and can't remember where things are, often several times during some driver installs or things like changing network settings. Windows SHOULD SEARCH THE MRU PATHS for files. Windows SHOULD NEVER HAVE TO ASK WHERE ITS OWN INSTALLATION FILES ARE! But no, it can't. It keeps asking for the "CD-ROM" even when it was installed from the Win98 folder on the hard drive. Really annoying is when it's asking "Duh... where's muh install files?" and RIGHT THERE in the drop list it has c:\win98 ! Every version of Windows from 95 through XP does this same STUPID thing. Does Vista still do this?

It's the *uninstaller* that renames the .INF file! (Bad uninstaller! Bad! *viciously cluebats whomever programmed the uninstaller to do that*) So I did this, ran uninstaller, rebooted, found new hardware, no driver, renamed the .BAK file to .INF, update driver on unknown device, found driver, rebooted... No sound. Says "The NTKERN.VXD, MMDEVLDR.VXD device loader(s) for this device could not load the device driver. (Code 2.) To fix this, click Update Driver to update the device driver." Really? I thought the Update Driver button made the computer fix me a ham sandwich. *clicky* It reinstalls the driver, even though it says the best driver is already installed... Reboot and still got the (!) and "NO CONFLICTS". (Bull#%@#, there's a conflict between me and one stupid OS that can't even remember where its installation files are.) Remove the device, reboot, finds and installs driver, reboot, get cursor with hourglass that won't go away, *reset* annnnnnd... Right back where I started, see the "The NTKERN.VXD..." above. Where do I apply the blowtorch to make this %&%@# thing activate this sound hardware?

I found that WDMA_YMH.INF in c:\windows\inf had been renamed to WDMA_YMH.BAK so I changed it back. I'll run the Yamaha uninstaller again, then rebooting should force windows to install its WDM driver. (I would do it right now but waiting on the horrendously long process to install Office 97 Pro, even though I'm only installing Word, Excel, MS Photo Editor and a few other things.) Microsoft claims that INF is in cab 49. http://support.microsoft.com/kb/238775/en-us Wrong! It's actually in cab 50.

I've done a fresh install of 98SE and 98SE2ME on my Tecra 8000 Pentium 2 300Mhz laptop with 128meg RAM and a 'new' 40gig hard drive. The built in audio is Yamaha OPL3-SAx and when I first installed Windows there was sound, but I then installed the drivers from Toshiba. After doing 98SE2ME (current release) it does bad things whenever I have my Compucable USB2 CardBus (PCC-USB2-2) or Belkin F5D7010 Ver.4000 WiFi card installed. The audio sometimes crackles and it'll lock out the keyboard and mouse buttons and eventually freeze the computer or do the thing where moving the mouse or clicking buttons or pressing keys makes it buzz. Doesn't happen without either of those CardBus cards installed. Didn't happen with plain old 98SE and the VXD audio driver either. I tried using the sound driver uninstaller then tried to get Windows' own driver back but the only Yamaha driver in the list is for some USB audio thing. How can I get that 'generic' driver back? Or might there be a way to use the WDM driver included with WinMe? Yamaha's site claims theres a WDM driver included with 98.

On my laptop running 98SE and Office 97, it's recently begun doing a strange thing. When I doubleclick a JPEG image, it launches MS Photo Editor, which immediately prints the image to the default printer, then exits. How do I stop it? (Photo Editor is doing the same #%%@ thing on one of my XP desktops too!)

Is there a site that has older intel chipset drivers, listing the latest chipset it actually contains drivers for? Intel gives all versions the same filename and many times I've gone back to the oldest download shown and still it won't install anything because the chipset is already "supported" by that version of Windows. Baloney! Some no longer available Intel download did install drivers but not the latest or currently oldest available that claims in its description to "support" that chipset and Win98SE. For example, such a site would have an installer that will actually install the last 98SE drivers Intel made for the 815 chipset. Or the 440BX or the... Same for 95, 95B, 98FE, Me, 2000 and XP. I'm tired of Intel lying on their site about what chipsets and Windows versions their installers support. When it DOES NOT really contain drivers for a specific chipset/windows combination, why does the description say it's 'supported' by that installer?

In Win9x/me, IO.SYS combines the functions formerly split between IO.SYS and MSDOS.SYS in MS-DOS 6.22 and older. MSDOS.SYS is merely a read only text file the IO.SYS process reads to obtain a few parameters- such as where Windows is located. Once control is handed off to the Windows kernel, IO.SYS is out of the picture. IO.SYS could actually be named anything because the BIOS doesn't launch the bootstrap file by name, it launches it by the physical location of its first sector on the hard drive. After that first sector is read, the boot process switches from BIOS to software control. Before Win95, MSDOS.SYS also had to have its first sector in a specific location or IO.SYS couldn't find it. With Win95 through Me, IO.SYS does what it should have all along- it uses the file allocation table to find MSDOS.SYS. After IO.SYS has launched and read the parameters in MSDOS.SYS and passed them to WIN.COM- it's all 32bitsville and the DOS stuff is pushed out of the way. It would be possible to use a completely new loader in place of IO.SYS to launch Win9x/Me but Microsoft did things that way to maintain the ability to run in a plain DOS mode and for running DOS programs in a virtual machine when Windows was running. If a DOS program makes a call to MSDOS.SYS, IO.SYS intercepts it and redirects it to the appropriate function within itself. DOS programs that cause problems with "DOS 7" or later or don't run under Windows 9x tend to be those that try to do things in undocumented ways. If a program tries to "strong arm" its way to an MSDOS.SYS function it'll crash because that file isn't what it was in DOS 6.22 and older. That does have a nifty benefit, it makes it extremely simple to move a complete Windows 9x install to a new hard drive without requiring any 3rd party software. With your new hard drive FDISKed and FORMAT d: /S 'ed with the first partition tagged Active, jumpered appropriate to where it's connected... Step 1. Boot up then change the virtual memory file to use the root of C:\ and reboot. Step 2. Launch Windows Explorer and go to the new drive. Step 3. On the new drive, rightclick MSDOS.SYS, click Properties and uncheck the System and Read Only boxes. Step 4. Click in the right pane on C: and hit Ctrl+A to select everything. Ctrl+click to UNSELECT IO.SYS WIN386.SWP and COMMAND.COM You *do* want MSDOS.SYS selected. (Without copying the old file, Windows won't know where to find itself on the new drive.) Step 5. Hold the Right mouse button and drag all the selected files to the root of the new drive. Answer YES to overwrite any files. Step 6. Shut down, re-arrange your hard drives so the new drive is connected how the old drive was and boot into Windows 9x exactly how it was, except on your new, larger and faster drive. The only detail you may have to attend to is setting the swap file, Windows 9x sometimes gets confused about it when it "wakes up" in the unfamiliar surroundings of a roomier hard drive.

Nope. This was from before anyone got MP10 onto 98SSE. Here's a batch file I picked up off the forum, I also found the exe2cab program somewhere. Just never have got a round-tuit to do anything with this. @echo off rem i have use exe2cab.exe to convert WindowsXP-KB835935-SP2-ENU.exe to rem WindowsXP-KB835935-SP2-ENU.cab rem i have renamed WindowsXP-KB835935-SP2-ENU.cab to winxpsp2.cab for ease. rem if u like to extract all files from WindowsXP-KB835935-SP2-ENU.exe rem u can use WindowsXP-KB835935-SP2-ENU.exe /x it will extract all files rem to current directory extract winxpsp2.cab ADVPACK.DL_ extract winxpsp2.cab BROWSELC.DL_ extract winxpsp2.cab MSHTMLED.DL_ extract winxpsp2.cab MSHTMLER.DL_ extract winxpsp2.cab MSXML.DL_ extract winxpsp2.cab MSXML2.DL_ extract winxpsp2.cab PNGFILT.DL_ extract winxpsp2.cab SHDOCLC.DL_ extract winxpsp2.cab SQLSRV32.DL_ extract winxpsp2.cab USP10.DL_ extract winxpsp2.cab ASCTRLS.OC_ extract winxpsp2.cab MSHTML.TL_ extract winxpsp2.cab EXTRAC32.EX_ extract winxpsp2.cab L3CODECA.AC_ extract winxpsp2.cab WMV8DS32.AX_ extract winxpsp2.cab WMVDS32.AX_ extract winxpsp2.cab ASFERROR.DL_ extract winxpsp2.cab BLACKBOX.DL_ extract winxpsp2.cab DRMCLIEN.DL_ extract winxpsp2.cab DRMSTOR.DL_ extract winxpsp2.cab DRMV2CLT.DL_ extract winxpsp2.cab LAPRXY.DL_ extract winxpsp2.cab MP43DMOD.DL_ extract winxpsp2.cab MP4SDMOD.DL_ extract winxpsp2.cab MPG4DMOD.DL_ extract winxpsp2.cab MPVIS.DL_ extract winxpsp2.cab MSNETOBJ.DL_ extract winxpsp2.cab MSPMSP.DL_ extract winxpsp2.cab MSSCP.DL_ extract winxpsp2.cab MSWMDM.DL_ extract winxpsp2.cab NPDRMV2.DL_ extract winxpsp2.cab NPDSPLAY.DL_ extract winxpsp2.cab NPWMSDRM.DL_ extract winxpsp2.cab QASF.DL_ extract winxpsp2.cab WMADMOD.DL_ extract winxpsp2.cab WMADMOE.DL_ extract winxpsp2.cab WMASF.DL_ extract winxpsp2.cab WMDMLOG.DL_ extract winxpsp2.cab WMDMPS.DL_ extract winxpsp2.cab WMERROR.DL_ extract winxpsp2.cab WMIDX.DL_ extract winxpsp2.cab WMNETMGR.DL_ extract winxpsp2.cab WMP.DL_ extract winxpsp2.cab WMPASF.DL_ extract winxpsp2.cab WMPBAND.DL_ extract winxpsp2.cab WMPCD.DL_ extract winxpsp2.cab WMPCORE.DL_ extract winxpsp2.cab WMPDXM.DL_ extract winxpsp2.cab WMPLOC.DL_ extract winxpsp2.cab WMPNS.DL_ extract winxpsp2.cab WMPSHELL.DL_ extract winxpsp2.cab WMPUI.DL_ extract winxpsp2.cab WMSDMOD.DL_ extract winxpsp2.cab WMSDMOE.DL_ extract winxpsp2.cab WMSDMOE2.DL_ extract winxpsp2.cab WMSPDMOD.DL_ extract winxpsp2.cab WMSPDMOE.DL_ extract winxpsp2.cab WMSTREAM.DL_ extract winxpsp2.cab WMVCORE.DL_ extract winxpsp2.cab WMVDMOD.DL_ extract winxpsp2.cab WMVDMOE2.DL_ extract winxpsp2.cab LOGAGENT.EX_ extract winxpsp2.cab MPLAYER2.EX_ extract winxpsp2.cab WMPLAYER.EX_ extract winxpsp2.cab WMP.OC_ rem because it bydefault extract file in i386 folder cd i386 EXPAND ADVPACK.DL_ ADVPACK.DLL EXPAND BROWSELC.DL_ BROWSELC.DLL EXPAND MSHTMLED.DL_ MSHTMLED.DLL EXPAND MSHTMLER.DL_ MSHTMLER.DLL EXPAND MSXML.DL_ MSXML.DLL EXPAND MSXML2.DL_ MSXML2.DLL EXPAND PNGFILT.DL_ PNGFILT.DLL EXPAND SHDOCLC.DL_ SHDOCLC.DLL EXPAND SQLSRV32.DL_ SQLSRV32.DLL EXPAND USP10.DL_ USP10.DLL EXPAND ASCTRLS.OC_ ASCTRLS.OCX EXPAND MSHTML.TL_ MSHTML.TLB EXPAND EXTRAC32.EX_ EXTRAC32.EXE EXPAND L3CODECA.AC_ L3CODECA.ACM EXPAND WMV8DS32.AX_ WMV8DS32.AX EXPAND WMVDS32.AX_ WMVDS32.AX EXPAND ASFERROR.DL_ ASFERROR.DLL EXPAND BLACKBOX.DL_ BLACKBOX.DLL EXPAND DRMCLIEN.DL_ DRMCLIEN.DLL EXPAND DRMSTOR.DL_ DRMSTOR.DLL EXPAND DRMV2CLT.DL_ DRMV2CLT.DLL EXPAND LAPRXY.DL_ LAPRXY.DLL EXPAND MP43DMOD.DL_ MP43DMOD.DLL EXPAND MP4SDMOD.DL_ MP4SDMOD.DLL EXPAND MPG4DMOD.DL_ MPG4DMOD.DLL EXPAND MPVIS.DL_ MPVIS.DLL EXPAND MSNETOBJ.DL_ MSNETOBJ.DLL EXPAND MSPMSP.DL_ MSPMSP.DLL EXPAND MSSCP.DL_ MSSCP.DLL EXPAND MSWMDM.DL_ MSWMDM.DLL EXPAND NPDRMV2.DL_ NPDRMV2.DLL EXPAND NPDSPLAY.DL_ NPDSPLAY.DLL EXPAND NPWMSDRM.DL_ NPWMSDRM.DLL EXPAND QASF.DL_ QASF.DLL EXPAND WMADMOD.DL_ WMADMOD.DLL EXPAND WMADMOE.DL_ WMADMOE.DLL EXPAND WMASF.DL_ WMASF.DLL EXPAND WMDMLOG.DL_ WMDMLOG.DLL EXPAND WMDMPS.DL_ WMDMPS.DLL EXPAND WMERROR.DL_ WMERROR.DLL EXPAND WMIDX.DL_ WMIDX.DLL EXPAND WMNETMGR.DL_ WMNETMGR.DLL EXPAND WMP.DL_ WMP.DLL EXPAND WMPASF.DL_ WMPASF.DLL EXPAND WMPBAND.DL_ WMPBAND.DLL EXPAND WMPCD.DL_ WMPCD.DLL EXPAND WMPCORE.DL_ WMPCORE.DLL EXPAND WMPDXM.DL_ WMPDXM.DLL EXPAND WMPLOC.DL_ WMPLOC.DLL EXPAND WMPNS.DL_ WMPNS.DLL EXPAND WMPSHELL.DL_ WMPSHELL.DLL EXPAND WMPUI.DL_ WMPUI.DLL EXPAND WMSDMOD.DL_ WMSDMOD.DLL EXPAND WMSDMOE.DL_ WMSDMOE.DLL EXPAND WMSDMOE2.DL_ WMSDMOE2.DLL EXPAND WMSPDMOD.DL_ WMSPDMOD.DLL EXPAND WMSPDMOE.DL_ WMSPDMOE.DLL EXPAND WMSTREAM.DL_ WMSTREAM.DLL EXPAND WMVCORE.DL_ WMVCORE.DLL EXPAND WMVDMOD.DL_ WMVDMOD.DLL EXPAND WMVDMOE2.DL_ WMVDMOE2.DLL EXPAND LOGAGENT.EX_ LOGAGENT.EXE EXPAND MPLAYER2.EX_ MPLAYER2.EXE EXPAND WMPLAYER.EX_ WMPLAYER.EXE EXPAND WMP.OC_ WMP.OCX cls copy ADVPACK.DLL C:\WINDOWS\SYSTEM copy BROWSELC.DLL C:\WINDOWS\SYSTEM copy MSHTMLED.DLL C:\WINDOWS\SYSTEM copy MSHTMLER.DLL C:\WINDOWS\SYSTEM copy MSXML.DLL C:\WINDOWS\SYSTEM copy MSXML2.DLL C:\WINDOWS\SYSTEM copy PNGFILT.DLL C:\WINDOWS\SYSTEM copy SHDOCLC.DLL C:\WINDOWS\SYSTEM copy SQLSRV32.DLL C:\WINDOWS\SYSTEM copy USP10.DLL C:\WINDOWS\SYSTEM copy ASCTRLS.OCX C:\WINDOWS\SYSTEM copy MSHTML.TLB C:\WINDOWS\SYSTEM copy EXTRAC32.EXE C:\WINDOWS copy L3CODECA.ACM C:\WINDOWS\SYSTEM copy WMV8DS32.AX C:\WINDOWS\SYSTEM copy WMVDS32.AX C:\WINDOWS\SYSTEM copy ASFERROR.DLL C:\WINDOWS\SYSTEM copy BLACKBOX.DLL C:\WINDOWS\SYSTEM copy DRMCLIEN.DLL C:\WINDOWS\SYSTEM copy DRMSTOR.DLL C:\WINDOWS\SYSTEM copy DRMV2CLT.DLL C:\WINDOWS\SYSTEM copy LAPRXY.DLL C:\WINDOWS\SYSTEM copy MP43DMOD.DLL C:\WINDOWS\SYSTEM copy MP4SDMOD.DLL C:\WINDOWS\SYSTEM copy MPG4DMOD.DLL C:\WINDOWS\SYSTEM copy MPVIS.DLL C:\Program Files\Windows Media Player copy MSNETOBJ.DLL C:\WINDOWS\SYSTEM copy MSPMSP.DLL C:\WINDOWS\SYSTEM copy MSSCP.DLL C:\WINDOWS\SYSTEM copy MSWMDM.DLL C:\WINDOWS\SYSTEM copy NPDRMV2.DLL C:\Program Files\Windows Media Player copy NPDSPLAY.DLL C:\Program Files\Windows Media Player copy NPWMSDRM.DLL C:\Program Files\Windows Media Player copy QASF.DLL C:\WINDOWS\SYSTEM copy WMADMOD.DLL C:\WINDOWS\SYSTEM copy WMADMOE.DLL C:\WINDOWS\SYSTEM copy WMASF.DLL C:\WINDOWS\SYSTEM copy WMDMLOG.DLL C:\WINDOWS\SYSTEM copy WMDMPS.DLL C:\WINDOWS\SYSTEM copy WMERROR.DLL C:\WINDOWS\SYSTEM copy WMIDX.DLL C:\WINDOWS\SYSTEM copy WMNETMGR.DLL C:\WINDOWS\SYSTEM copy WMP.DLL C:\WINDOWS\SYSTEM copy WMPASF.DLL C:\WINDOWS\SYSTEM copy WMPBAND.DLL C:\Program Files\Windows Media Player copy WMPCD.DLL C:\WINDOWS\SYSTEM copy WMPCORE.DLL C:\WINDOWS\SYSTEM copy WMPDXM.DLL C:\WINDOWS\SYSTEM copy WMPLOC.DLL C:\WINDOWS\SYSTEM copy WMPNS.DLL C:\WINDOWS\SYSTEM copy WMPSHELL.DLL C:\WINDOWS\SYSTEM copy WMPUI.DLL C:\WINDOWS\SYSTEM copy WMSDMOD.DLL C:\WINDOWS\SYSTEM copy WMSDMOE.DLL C:\WINDOWS\SYSTEM copy WMSDMOE2.DLL C:\WINDOWS\SYSTEM copy WMSPDMOD.DLL C:\WINDOWS\SYSTEM copy WMSPDMOE.DLL C:\WINDOWS\SYSTEM copy WMSTREAM.DLL C:\WINDOWS\SYSTEM copy WMVCORE.DLL C:\WINDOWS\SYSTEM copy WMVDMOD.DLL C:\WINDOWS\SYSTEM copy WMVDMOE2.DLL C:\WINDOWS\SYSTEM copy LOGAGENT.EXE C:\WINDOWS\SYSTEM copy MPLAYER2.EXE C:\Program Files\Windows Media Player copy WMPLAYER.EXE C:\Program Files\Windows Media Player copy WMP.OCX C:\WINDOWS\SYSTEM @ECHO OFF REGSVR32 /S %windir%\SYSTEM\MSHTMLED.DLL REGSVR32 /S %windir%\SYSTEM\MSXML.DLL REGSVR32 /S %windir%\SYSTEM\MSXML2.DLL REGSVR32 /S %windir%\SYSTEM\PNGFILT.DLL REGSVR32 /S %windir%\SYSTEM\ASCTRLS.OCX REGSVR32 /S %windir%\SYSTEM\L3CODECA.ACM REGSVR32 /S %windir%\SYSTEM\WMV8DS32.AX REGSVR32 /S %windir%\SYSTEM\WMVDS32.AX REGSVR32 /S %windir%\SYSTEM\LAPRXY.DLL REGSVR32 /S %windir%\SYSTEM\MP43DMOD.DLL REGSVR32 /S %windir%\SYSTEM\MP4SDMOD.DLL REGSVR32 /S %windir%\SYSTEM\MPG4DMOD.DLL REGSVR32 /S %windir%\SYSTEM\MSNETOBJ.DLL REGSVR32 /S %windir%\SYSTEM\MSPMSP.DLL REGSVR32 /S %windir%\SYSTEM\MSSCP.DLL REGSVR32 /S %windir%\SYSTEM\MSWMDM.DLL REGSVR32 /S %windir%\SYSTEM\QASF.DLL REGSVR32 /S %windir%\SYSTEM\WMADMOE.DLL REGSVR32 /S %windir%\SYSTEM\WMDMLOG.DLL REGSVR32 /S %windir%\SYSTEM\WMDMPS.DLL REGSVR32 /S %windir%\SYSTEM\WMNETMGR.DLL REGSVR32 /S %windir%\SYSTEM\WMP.DLL REGSVR32 /S %windir%\SYSTEM\WMPASF.DLL REGSVR32 /S %windir%\SYSTEM\WMPCD.DLL REGSVR32 /S %windir%\SYSTEM\WMPCORE.DLL REGSVR32 /S %windir%\SYSTEM\WMPDXM.DLL REGSVR32 /S %windir%\SYSTEM\WMPSHELL.DLL REGSVR32 /S %windir%\SYSTEM\WMPUI.DLL REGSVR32 /S %windir%\SYSTEM\WMSDMOE.DLL REGSVR32 /S %windir%\SYSTEM\WMSDMOE2.DLL REGSVR32 /S %windir%\SYSTEM\WMSPDMOE.DLL REGSVR32 /S %windir%\SYSTEM\WMSTREAM.DLL REGSVR32 /S %windir%\SYSTEM\WMVCORE.DLL REGSVR32 /S %windir%\SYSTEM\WMVDMOE2.DLL REGSVR32 /S %windir%\SYSTEM\WMP.OCX REGSVR32 /S %windir%\SYSTEM\WMSDMOD.DLL REGSVR32 /S %windir%\SYSTEM\WMSPDMOD.DLL REGSVR32 /S %windir%\SYSTEM\WMVDMOD.DLL REGSVR32 /S WMPBAND.DLL /ShowWMP /SetShowState %windir%\INF\UNREGMP2 /UpdateWMP CLS EXIT

Which should I run first? Autopatcher or 98SE2ME? What about the XP SP2 stuff? I'm currently experimenting with all this fun stuff on my old, slow laptop. Already ran Autopatcher and had it install everything it's got. Just the bare bones Me stuff it installs has already made a big speed difference! My plan is to eventually (sooner if something goes *foom*) wipe the hard drive and start fresh on the laptop.

How do I fix Windows Update thinking my 98SE laptop is a Macintosh? I tried both of the standalone fixes. Which part of the auto-patcher is that fix in, in 1.95? Something else to think about is Spyware/Malware blockers that have runtime programs to guard against Registry and system file changes. If there's a way to at least detect them running and abort the install, with an ending note/warning to stop the resident program from launching at boot, that'd be nifty. For Spybot Search and Destroy, the program is teatimer.exe Autopatcher will still work, if you're willing to sit there to poke the A key every time TeaTimer pops up. Now that I know this'll work, I'm going to get WinMe, already have XP's Service Pack 2, so I should be all set to nuke-and-pave for the ultimate 98SE system. Just the 'bare bones' WinMe bits make a noticeable speed improvement. Toshiba Tecra 8000, Pentium 2, 300Mhz, 128meg RAM, 6.4gig hard drive. Fortunately no BIOS or other issues on this model with drives up to at least 120gig.

KB913433 is obsolete for the current version of Macromedia Flash (from Adobe now) for IE6. It's also obsolete for whatever prior version of Flash I had on my 98SE laptop. Other than that, everything else installed OK.

The speed of it ain't the problem. This has gotten slower over time. I've had boxen of similar speed running 2000 Pro on my LAN and never had any network browsing speed issues with them. On the laptop, it's all "stock" 98SE except for the WinMe USB Mass Storage drivers from this forum.

Something I've found. If I click size to group the smaller files first, then go to thumbnail, it'll display more of them. If I group the larger files first, it displays fewer thumbnails. It's also spread to every folder on every drive with images! It appears as if Windows has "decided" that there will be a certain total size of thumbnails per folder and that's all I'm going to get. I've also found that it creates the thumbnails on two files at a time by using Process Explorer. I can select a folder with images, go to thumbnail view then when it stops, Process Explorer shows two files in the folder with open handles, sometimes more than one handle per file. Even weirder is that the last row showing thumbnails always has just icons on the LEFT, with a couple of thumbnails on the RIGHT, as if it's generating them in order from left to right. I haven't installed, or uninstalled, any software that does anything with editing images. I did uninstall DreamWeaver MX, but that doesn't _edit_ images, it just plonks them into HTML.

I've searched the web and found the fix for NONE of the thumbnails displaying for one or more image file types, but that's not my problem. All file types that 2000 can display thumbnails for in Explorer do, but in _some_ folders the thumbnails will display for the first 20 or 30 or 53 or however many images, then none will display for the rest of them in the folder, no matter what sort option I choose before switching to thumbnail view. Nifty how I can sort by modified then switch to thumbnails and have the newest files at top or bottom, then go back to details, sort by name then back to thumbnails and there they are by name. I have some folders with hundreds of images where thumbnails will display for them all, and some with only 100 or so that only the first (variable number) will display. It's NOT a corrupted file problem, every image will open fine in Photoshop 7.0.1 or MS Photo Editor or Paint. (The few types Paint supports.) Does Windows 2000 have somewhere a maximum total of allowed thumbnails that needs to be increased? Possibly related to this is I have it set to cache thumbnails, but it never has. Every time I launch Explorer and open a folder set to Thumbnails, it has to regenerate them all. It'll hang onto them until I exit Explorer. (Indexing for searching the drives has also always behaved like that, only hanging onto the index until I quit the current Exploer session, but that's most likely unrelated to the thumbnail problem.)

I have a PC running 2000 Pro SP4 with all current updates, connected through a D-Link DSS-5+ 10/100 switch to a Toshiba Tecra 8000 laptop with a 3-Com combo 56k 10/100 CardBus card. The laptop is running 98SE, all current updates. I can browse the PC's shared drives from the laptop just like they're connected locally, but browsing the laptop's one drive from the desktop is S L O O O O O O W W W. It's just these two computers on the network currently. The laptop is set to NOT sleep, hibernate or otherwise do any powersaving while plugged into AC. I have verified that the network connection is running 100 megabit, full duplex on both ends. I'm not trying to view image thumbnails on the laptop over the network or any other crazy bandwidth hogging stuff like that. It just takes MINUTES to open folders or show their contents on the laptop. It didn't use to be liek this, but over time it's been getting slower and slower from the PC end, no change from the laptop end. Laptop is a PII 300Mhz with 128meg, PC is a 1.4Ghz Athlon XP with 512meg. Any clues why the one way slowness? Edit: I've tried all the ports on the switch, and different network cables. Same result.

Just a little note on using the iesetup switches to grab IE for one or all supported Windows versions. The iesetup.ini file will not have the lines needed to do a local install. Setup will ignore the local files and go looking "out there", anywhere _except_ any local storage. Here's the fix. [Options] Language=0409 Shell_Integration=0 ConfirmFileList=0 LocalInstall=1 Win95=6.0.2800.1106 Millen=6.0.2800.1106 NTx86=6.0.2800.1106 W2K=6.0.2800.1106 NTalpha=0 [Version] Signature=Active Setup [Downloaded Files] Without these lines ConfirmFileList=0 LocalInstall=1 it'll try a network/internet install. The iesetup.ini on the FTP site posted earlier in this thread is nowhere near complete. Here's the full one produced by an all version IE6 SP1 download (plus the local install edits). [Options] Language=0409 Shell_Integration=0 ConfirmFileList=0 LocalInstall=1 Win95=6.0.2800.1106 Millen=6.0.2800.1106 NTx86=6.0.2800.1106 W2K=6.0.2800.1106 NTalpha=0 [Version] Signature=Active Setup [Downloaded Files] ie6setup.exe=1 iesetup.dir=1 filelist.dat=1 iesetup.ini=1 This folder is safe to delete.txt=1 GSETUP95.CAB=1 GSETUPNT.CAB=1 CRLUPD.CAB=1 IEW2K_1.CAB=1 IEW2K_2.CAB=1 IEW2K_3.CAB=1 IEW2K_4.CAB=1 IEMIL_1.CAB=1 IEMIL_2.CAB=1 IEMIL_3.CAB=1 IEMIL_4.CAB=1 SETUPNT.CAB=1 IEDOM.CAB=1 IENT_S1.CAB=1 IENT_S2.CAB=1 IENT_S3.CAB=1 IENT_S4.CAB=1 IENT_S5.CAB=1 IENT_S6.CAB=1 SETUPW95.CAB=1 IE_S1.CAB=1 IE_S2.CAB=1 IE_S3.CAB=1 IE_S4.CAB=1 IE_S5.CAB=1 IE_S6.CAB=1 IEEXINST.CAB=1 TS95.CAB=1 TSNT.CAB=1 MOBILENT.CAB=1 MOBILE95.CAB=1 BRANDING.CAB=1 ADVAUTH.CAB=1 HHUPD.CAB=1 HELPCONT.CAB=1 ICWCON.CAB=1 ICW.CAB=1 FONTCORE.CAB=1 IEDATA.CAB=1 IE_EXTRA.CAB=1 WAB.CAB=1 MAILNEWS.CAB=1 OEEXCEP.CAB=1 MPLAY2U.CAB=1 MPLAY2A.CAB=1 MPLAYER2.CAB=1 MPCDCS.CAB=1 VGX.CAB=1 AOLSUPP.CAB=1 SWFLASH.CAB=1 SCRIPTEN.CAB=1 SCR56EN.CAB=1 FONTSUP.CAB=1 IELPKAD.CAB=1 README.CAB=1 OAINST.CAB=1 It's still not a FULL download because it will not grab the additions for other languages or Flash. Doing this for IE5 will only download the Flash stuff on a fresh and clean original Windows 95 without the a update. Any other version of Windows, it'll detect that a newer version is already installed and it won't download Flash. Anyone know how to force it to download ALL of the IE components, no matter what language version it's being run on or what IE features are already installed?

What I'd love to see is a single custom installer with the latest or last drivers for all Intel chipsets, for all windows 9x, Me, 2K and XP. Why? Because the newer installers from intel do not have any drivers for older chipsets. They may be omitted even for Windows 2000 in newer releases. All you get is a message saying the chipset is supported by this OS. (Sure it is, by Microsoft's halfarsed drivers.) It's especially annoying with WinMe. I spent a few hours downloading older and older infinst_enu.zip packages from intel, trying to find the last one with Me drivers for the 810 chipset. I went all the way back to the very first one listed as supporting Me and it wouldn't install anything. I finally dug around on my 2000 Pro box and found a really old version that had info saying it was for 95, 98, and 98SE, but Me took it just fine without a bit of complaint! ISTR it was what I downloaded right around when the 810 chipset was first released. What might work better is seperate installers for each Windows version, containing all the latest/last available intel chipset drivers for that version. Then when encountering WinMe on an Intel chipset, just run the MeIntel installer and if there's drivers for that chipset, they'll be installed.

Try this to see how annoying it is. Launch Windows Explorer. Click the + next to a folder with sub-folders to expand it. Click on any subfolder to select it. Click the - by the top folder to close it. The folder will collapse THEN POP BACK OPEN, the folder highlight pops briefly back to the folder that was selected before clicking the -, then jumps to the top folder, displaying its contents in the right pane. Is there a way to stop the $#$%%# thing from popping the folder back open? If _I_ wanted it open, I wouldn't have clicked the - to close it. That's been one of the main things I've hated about 98/98SE from the first time I used it. (I don't recall if 95 did this.) In other words, I want it to work like it does in 2000, the folder collapses and shifts the selection to the top folder where the - was clicked. If it's possible, I'd also like to disable the automatic opening of subfolders when dragging files. _I_ will open the folder tree to the exact place I will be moving or copying, thankyouverymuch. 'Course then MS had to do something "better" with XP's default "Simple Folder View" that assumes the user is such an id*** that he can only handle having one folder open at a time.

Sounds like a job for the denizens of this forum. "The Latest (or last) intel Drivers for All Windows, All Chipsets, Driver Pack" Such would be HIGHLY USEFUL so I could just run one installer no matter what Windows version on any intel chipset and it'd toss in the latest/last drivers for that chipset and that version of windows.

You'll have to figure out which .inf file Windows is using to choose the "best" driver, then either remark out or delete the line(s) for that driver or just delete the whole file. Then Windows will have to accept the correct driver you supply. Just another one of the "Windows knows best." things the 9x/Me series is infamous for.

Good info, thanks. I use driverguide all the time, and have uploaded several drivers there. I'll check the others you posted. What I'd like to know is why Intel has "unsupported" their older chipsets in later relases of their infinst downloads, when they had drivers for those chipsets for 9x, Me and 2K in previous releases. I'd like to see a single infinst download with the last drivers released for all 9x, Me and 2K for all intel's discontinued chipsets. That'd make a PC tech's life sooooo much simpler when he can just run one installer for any intel chipset running a non-XP version of Windows.

The USB files on my PC. There's a winnt\usb2 folder with even older versions of some of these. usbcamd.sys 5.0.2135.1 (for Cameras) usbd.sys 5.0.2195.6658 usbehci.sys 5.0.2195.5652 usbhub.sys 5.0.2195.6689 usbhub20.sys 5.0.2195.6655 usbintel.sys 5.0.2134.1 usbmon.dll 5.0.2195.6684 usbport.sys 5.0.2195.5652 usbprint.sys 5.0.2195.6655 usbscan.sys 5.0.2195.6655 usbstor.sys 5.0.2195.6655 usbui.dll 5.0.2134.1 I'm on dialup so it's gonna take me a while to download your service pack.

Are there any intel 810 chipset drivers for Windows Me, or is that chipset just "supported" by Microsoft's lousy generic drivers? I've just spent a lot of time downloading several old versions of the intel chipset drivers off their "previously released" area, and even the very first one that lists Me in the supported Windows versions claims that it has nothing to install because the os already supports the chipset. 'Course that section doesn't have EVERY version of infinst_enu.exe or infinst_enu.zip because I have a few newer ones not in their list. Sooo, what is needed to be found and safely stashed somewhere is the FINAL version of the intel driver package that actually has drivers in it for the 810/815 chipset for Windows Me. That'd be a good thing for every intel chipset, locate and archive the last versions with drivers for each chipset, for each version of Windows from 95 on. P.S. I dug up what from the release notes is version 2.10.0002, but there's no mention of any version past 98SE, and the last chipset listed is the 810. So I installed it. Windows Me didn't complain a bit. Sooo, that gives an early version, what's the latest version that'll work on Me, "supported" or not?

In my mucking about with USB 2.0 cards, I've managed to get a version of the Microsoft USB drivers and USB Mass Storage drivers onto 2000 Pro SP4 that are not the latest, and they won't update through Windowsupdate site or through Device Manager. Is there a standalone package available anywhere?

In the Maximus Decim USB drivers for 98se thread, someone posted this link. http://www.doubleh.com.tw/dh-page/download.htm The drivers downloadable there are the OrangeWare USB 2.0 drivers, version 2.3.0.0. What's so happy fun ball about them is they're quite a bit newer than what Belkin has on their site for their F5U219 USB 2.0 PCI card. I have a cheap USB 2.0 to IDE cable from geeks.com, which uses the Genesys GL811E chip, which is apparently a bit on the "iffy" side, but actually works* (instead of not working at all) on the Belkin card after installing those newer OrangeWare drivers. *But only in FAT32, can't get it to go at all as an NTFS drive in 2K Pro SP4. So! Has anyone seen any higher version number on OrangeWare USB 2.0 drivers? It doesn't matter what the filenames are, the internal version data always says made by OWC. Also note that the OWC drivers support all brands of USB 2.0 chips, so the 2.3.0.0 ones from the site should work with VIA, Intel, etc in addition to the two shown.