awkduck

Providing the device hardware/vendor ID can help locate the driver. I have noticed Win98 listed as a supported operating system (back of packaging). Did your packaging provide a URL? I'm guessing windows found no driver for it. A newer drawing tablet, I bought a couple of years ago, found support. It installed about eight things; but it did work.

I know the following is hardly a contribution to the current subject. It would be better if I provided a detailed description, of what the things being discussed actually do, beyond the vague definitions I offer inside a link. The Internet does know about "/i". I should say, the Internet knew about "/i"; but the Internet is forgetful. If you bug it to remember, you can coax the info into surfacing. Here is a link to Windows 9x setup switches.

@MrMateczko I tested CamStudio, again (could not remember the exact video issue). With Xvid, the render is completely black. Microsoft Video 1 codec would stop recording, after a second, with error "Could not create AVI". If I lowed the quality it would render poorly with choppy capture. Default quality setting was fine, but with really bad quality render. Divx "Quality Based 100%" rendered good with modest enough CPU load. So, it was an Xvid problem there. VirtualDub, not so much. I couldn't even get raw video capture.

I should have been more clear. The issue is only in the captured video. The actual graphics are fine. Just the two mentioned screen capture applications render their output with such artifacts. Nothing seems to abate those issues (including your suggestions). Since other applications work fine, rendering capture, it must be a conflict between the driver, my chipset, and certain capture methods. I suspect that there is an issue with my shared video memory and Vbemp. If it is that, it is probably due to a poor BIOS implementation. This specific machine was not intended to support Win98. But I haven't really looked in to it.

That one has not worked for me. There is a more recent release of that application, under a different name . It also does not work for me. Likewise, I have issues with VirtualDub's screen capture. The mouse leaves black square trailers (where ever it goes), or the screen is black and only the mouse is seen (leaving mouse icon trailers). It could be due to using Vbemp. Maybe not everyone, using Vbemp, has this issue. But I am one of the unfortunate cases, where loading a DoxBox causes the screen to go berserk (must be launched fullscreen). Camtasia, Free Screen Recorder, and LICEcap are the only ones that have worked, thus far.

Tracktion Software - Traction v5, works with KernelEx. ASIO4ALL didn't work well with it, on my machine. But my USB ASIO driver was fine. DirectSound works well. Adjust the samples as low as you system can handle it, before clipping audio. Newer versions may work, but I haven't tested them.

That is for screenshots. I've never used Snag-it. It seems to have some nice options. LICEcap's LCF format is not near RAW. So file size is not a problem. It does seem like it records live to disk (maybe?). Cockos mentions that you should probably have at least a Gig of ram, when using LCF. It can't quite do fullscreen. At 1024x768, it can do 1014x717 maximum. That isn't horrible. Reaper can render it to some other format, using it's cut down FFmpeg. I choose a WEBM container with VP8 and Vorbis (vorbis, only if audio is included). There where other options, but not a ton. The Video played fine. I used LICEcap v1.32. There may be a slight decrease is CPU usage, when using LICEcap over "Free Screen Recorder" (paired with the Xvid codec). The LCF codec is maybe a little less CPU intensive. But you could also use a less compressed format, with "Free Screen Recorder". In my opinion, they are both simple and usable. If the last version of FFmpeg "to work on Win9x" supported LCF video, you could skip Reaper. That would make it another free option.

@defuser I was thinking about full desktop capture (full color). But LICEcap is an interesting application. It has a lossless format (LCF), which can be opened in Reaper. That can then be edited (basic editing and a handful of FX/Transition filters) and converted to something else. With KernelEx, I have had Reaper v6 working (minor quirks and workarounds with VSTi UIs). So, potentially this could be a more professional approach. I haven't tried it. But LCF supports full color. The issue would be memory, as lossless probably takes up a bit of space; and LICEcap doesn't apear to have a "live" record to disk option. If lossless is close to raw, then "live" to disk might not be a likely option. At least not on my system :) I'll look into that.

At least to version 7.XX of Mutools Mulab works, on Windows 98 Gold (and newer). I cannot test this without KernelEx. The Win98FE WDM/DX/DXi bug forces me to use KernelEx as a work around. I am using the same settings as in Reaper v6, as posted before. The MME audio engine does not work. You must use ASIO. Beyond that, it works great. I wouldn't go beneath 1Ghz/1Gb CPU/RAM. Maybe 512Mb would be okay. Really, 1.4Ghz should be a minimum spec. But I can see making it work, on my Pentium M 1.2Ghz. If you test a newer version, please update the thread. Edit: There is one snag. Most of the program's file browsing does not work (expects NT5 or newer). There is a work around. One built in file browser actually works. On the right hand of the screen there is a file browser. At the top there is a "What" option. Select "All Files". This will let you browse to your VST/VSTi .DLL or audio .WAV sample. You drag Instruments or Samples to the Far left, and effects to their rack location. This will also work with presets and samples, for the built in Synths. On the plus side, once you have add a VST/VSTi .Dll, it can be found in the "VST Synths" or "VST Effects" section of the "What" browser option.

There are some good tools for Desktop/Screen capturing (video). Some don't always work. For example, I've had issues using VirtualDub and Vbemp, on some systems. Others are not free, even if abandonware. This one is as good, if not better, then an old version of Camtasia. I would install/use the Xvid encoder, or some codec pack. If using an older machine, maybe mpeg1/2 would be better. For audio Vorbis, MP3, AC3, or PCM. For best results, you'll need to fine tune the Video options. Specifically, the "Caputre Frames Every" and "Playback Rate". But if you machine is too slow, or under load, you may have to settle for less then exacting cursor movement (recorded). It's called "Free Screen Recorder", but I swear I've tried a couple others by the same name. This one actually works. Here is the link.

Cockos Reaper 6.XX works on Win98. The last installer to work, on Win98, is the 4 series. But the five and six series can be installed, from a different machine (XP+ or Linux/Wine), using the installer's portable mode. You just move the portable install to Win98. If you monitor the files installed (Regshot [C:\Windows]) and Compare your pre and post install registry exports (windiff -frx new.reg b4.reg af.reg) you can use the standard install process. You just need to move everything else with it (new.reg and files installed outside of "Program Files"). Edit: My virtual/ram "C:\Windows\Temp" folder was disabled. I was running out of temporary harddrive space, during install. I am using KernelEx. But haven't tried without it. On my machine it is required (read bottom). Using version 6, I didn't run into any huge problems. However, when adding a VST/VSTi, I could not resize the plugin's UI window. But docking the window gave me usable access the the UI. I have not even nearly tested everything. I doubt VST3 and other things will work. But I didn't try. Everything seemed to render fine. If you have a slower machine, I'd stick with version 3. If you don't have ASIO support Dsound (DirectX) works okay. Also, there is always MME (Wave). Might be your only option, if your audio device is only DSound emulated (check DXdiag). I have had some audio programs crash, if there is a VxD audio device driver. This when the application is meant for a newer version of Windows. Some will use Dsound or MME, ignoring the Vxd/WDM difference. The lowest latency I have gotten, using a VxD driver, was when using it with Steinberg's DXASIO or Cakewalk's PipeWire (for use with Cakewalk only). When using Win98FE, I have to run the application in XP compatibility mode and select the advanced option "Don't use these settings in child processes (KernelEx). This is something I must do, even if the application was meant to run on Win98. Seems to be a Win98FE bug, with using WDM drivers and attempting to load\search DX/DXi plugins.

I wish I was talking about HD Audio. There is sound. But yeah, it worked without WDMEX.

Applications crashing, at load time (searching for DX plugins) using WDM AC97 audio drivers, has been solved. As an example, in FL Studio 5 and Sonar2.2XL, a work around is to have the application's .exe run in XP compatibility mode (KernelEx). But the option "Don't use these settings in child processes" must be checked. If you do not select that option (XP compatibility only) your audio device will available in the application, but the device will not have functioning input or output. I should mention again, that this issue existed without the presence of KernelEx, on the system. It was not the cause of issue, but part of the solution.

I don't see too much being posted about Wdmex. Could be that the procedure to success is clear, in the instructions. Also, it is pretty clear that it might just not work, even if you've done everything right. Mostly, for some reason or another, Wdmex has nudged drivers "that are for my system (Win98FE)" to actually work. Some drivers, at the edge of dropping Win98 support, were not very good. Recently, I tested a 2009 Win2K-Vista Sigmatel C-major driver. Fortunately, the driver still used the "Chicago" signature. The .inf file modifications were minor. Entries like "something.nt.inst" just needed converting to "something.inst". There where no registry entries or folder locations, that needed WinNT to Win9x conversions. The .inf file was too big for Windows 98 to use. I don't know what the size limit is. But I was able to fix that, by deleting localization info I didn't need. Also, the file was in unicode text format. It needed to be saved as a plain text file. I haven't extensively tested the driver. I did notice, that when selecting options for mixer controls, that the record (line-in/mic) options where located in playback; this rather than the record category. I don't know if that will cause issues with some programs, when trying to assign input. Also, the head phones now have their own mixer bar, rather then just automatically being controlled by the main volume. However, the main volume still determines the final output, once you un-mute the head phones and adjust that volume. I'm guessing that this setup is common to newer versions of Windows. The main volume control only adjusts the speakers. The previous drivers, generic Realtek Vxd and Wdm, were limited by directsound emulation. The new drivers are not listed as such, and test fine under Dxdiag. I've had other issues, with the Realtek drivers, and haven't test against them. The AC97 Sigmatel is a pretty cheap audio device. So even though this is a success, in means of quality audio production (recording/sampling), I haven't accomplished much. But I could see non-emulated directsound being useful. Rloew, where ever you are (in the beyond), thanks again!

There is also Avidemux Version 2.5.6 (no H.264/5). For the command line there is FFmpeg or LibAV (at least H.264 and probably H.265). Needs KernelEx.

From "My Computer", right click on the drive and select properties. The label should be shown, and is editable.

You should check the .inf file used to install your driver. You can open it with Notepad. Near the top of the file there will be an entry, with the word "Signature". If it is shown as: Signature = "$Windows NT$" this driver most likely will not work. This is what you are looking for: Signature = "$Chicago$" Also, you can go to "Control Panel" > "System" > "Device Manager" (tab) > then right click on your installed driver and select "Properties". When the device properties window opens, click on the "Driver" tab. If the "Driver File Details" button is grey out (you can't click on it), then your driver is most likely not compatible with your version of Windows. It will also have a message like: No driver files are required or have been loaded for this device. To update the driver files for this device, click Update Driver. This message is only okay for passive\non-hardware devices. An example is the "PCMCIA Card Service" device. If you are installing a driver, for hardware, then you should most likely be able to click on the "Driver File Details" button and see list of driver files. I don't think Acer ever released/developed Win9x "SDcard Adapter" drivers, for the "Aspire 1690". You don't need a patch or anything like that. If you do your research, you might be able to get those "Windows NT" driver working, on Win9x. But that is beyond the kind of help most can provide you, though a forum. You'll need to modify the .inf file, to conform with the "Chigaco" .inf specifications. Likely you'll need at least Rloew's WDMEX tool and more over WDMStub. You'll want to look at checking any DLL files with Dependency Walker and get a hold of WDMCHECK. Quite frankly, the work involved is often beyond what most people are willing to do. There is also no guarantee that you will have any success. As with NT designed Video device drivers, NT SDcard adapter drivers just might not have potential to work with Win9x. Edit: ------- "You could try your luck with a PCMCIA SDcard Adapter, providing it has drivers for Win9x. But it might come with some built in size limitation (the driver's limitation, not a Windows limitation). You'd want to research the product before buying it. I've had partial luck with a cheap generic PCMCIA card. It uses IOS.xvd and ESDI_506.pdr, from Windows 98. But they are not sufficient, and potentially counter productive, towards the card's functionality. I haven't looked into it." I looked into the PCMCIA/SDcard adapter, that I have (some cheap generic model). I assumed some functionality issues; but once the SDcard was formatted everything worked fine (32Gb). I'm guessing a PCMCIA/CFcard adapter would also work fine. But this is dependent on a couple of things. One is your "CARD BUS" being functional. Some card bus .inf files, for Win9x, just reference Windows files. So if you find that your card bus is not installed, you could potentially build one using your card bus pci vender/device id. The other is finding a PCMCIA card that isn't incompatible with Win9x. I can't make any promises, but the hardware is relatively simple; so most are likely fine. ------- The best chance, is a SDCard to USB adapter. But it is my guess, that this isn't something your interested in. Wish I had better news to share. It would be nice to use those SDcards. If I ever get NT SDcard adapter drivers to work for Win9x, I'll make a post about it. That kinda thing only happens when I get free time. Edit: I've never tested one, but it is possible that a CFcard to PCMCIA adapter may work. I know that it wouldn't solve you problem. But for extra storage space, it might be an option. Some are designed to insert, with the CFcard, flush with the laptop's shell.

Many Intel GPUs don't produce as much heat. The "Rugged" brand of Toughbooks have a heat spreader, about the size of and underneath of the keyboard. The cases hard surface is just to make it more durable. If you do buy one, make sure it comes with the Harddrive caddy. Unlike some common laptops, you cannot install a Harddrive without the caddy. The laptop's harddrive interface uses a special connector; the caddy comes with the adapter for it. I have not used the 855 GPU myself. But I have seen many "Win9x" drivers for it. It is the "Intel Extreme Graphics 2" integrated graphics processor. I've been planning to buy one myself, for some time. It should perform good, for Retro 3D. The audio chipset is AC97 "Sigmatel". In real dos you can use SMEMU for Soundblaster emulation (no 16bit protected mode, only real and 32bit protected mode). In Windows many Dos Games will work with audio (must use WDM audio driver). But some will only partially work, like Wolf3D. You can either use and SDL1.2 port of those games (if available), or use real Dos with SBEMU. Games like Doom and Quake worked with audio inside windows. This is because of the music being on the Disc/ISO (ReadBook).

The CF-28 is fanless and supports Win9x 3D Acceleration (i8xx series GPU). The closest one to the CF-28, that I know of, is the CF-18. But some come with i915 (no Win9x 3D acceleration) and others with i8xx (Win9x 3D acceleration compatible). You have to be careful when buying one. The issue is that you don't often (if ever) find one over 1.2Ghz. Some, with the i8xx, come between 800Mhz and 1.2Ghz. I have seen one, with the i815, advertised at 1.6Ghz; but I think they must have made a typo, or something. It was the only one I've ever seen. Both the CF-18 and CF-28 come with external VGA ports. Most older Toughbook/Toughpads do. One thing that the CF-18 does not have, is a parallel port (the CF-28 does). Both have a serial port. I should point out that the CF-28 is Pentium III, and the top CPU speed is 1Ghz (some are slower). The CF-18 is Pentium-M. I haven't done any benchmarks, but an 800Mhz Pentium-M might out perform a 1Ghz Pentium-III. Also, the CF-28 tops out at 512Mb of ram. The CF-18 at 1.5Gb. The CF-28 is also running with USB1.1, and the CF-18 is at USB2.0. There is a part number, on the bottom of these ToughBooks, that may help determine what GPU the laptop has. If you are looking on Ebay, some seller might not know how to find out what the GPU model is. So there is a chance, if they provide that model number (pictures), that you can find out yourself; provided they are selling you the one in the picture. You've gotta watch out, when some one is selling more than one. I've learned that the hard way, when buying thin clients.

I also don't know what dock means. This may or may not help; I don't know what the entire situation is. If the drive is good (no corruption), and just the O.S. integrity is lost, maybe you can just copy the XP setup files to the drive. This is assuming you have another computer you can connect the drive to. If so, you can system format the drive as a FAT32, with a Win98 boot disk or cdrom. Copy SMARTDRV.EXE and the XP setup folder i386 over. Reinstall the drive into the original machine. Boot it up, then run SMARTDRV.EXE before running i386\WINNT.EXE. After setup is complete, I think you can convert the drive to NTFS. I am at the edge of my Windows experience, when it comes to XP.

What does the error message say? Did Windows ever try to install drivers, for the USB enclosure?

2014 at the oldest, and 2016 at the newest. Western Digital Elements. It was this one, but instead of P/N: WDBUZG0010BBK-EESN it was P/N: WDBUZG0010BBK-04.

Rloew created the 137GB patch (48bit addressing mode, for drives over 137GB). But that's for IDE 48bit addressing. I don't know that you need it for USB. What USB drivers are you using? NUSB? SP3? If you have another drive to test with, or if it is not an issue to reformat your 500Gb drive, you can try a FAT32 formatting (maybe you already have?). If it works, you probably don't need a patch (not for Windows, anyway). I know that I could not mount a NTFS formatted drive, that had been prepared by Linux (older version). But once I used Paragon to prepare the driver, everything was fine. The only issue was that the partition was really slow on transfers, with Linux; it was fine with Win98. For the record, it was a 1GB NTFS USB (internally SATA) drive. I think Paragon NTFS (which is the driver from SP3) supports NTFS 1.2, 3.0, and 3.1. But I didn't think the NTFS changes, after Windows XP, were too significant. The backwards compatibility is supposed to be pretty good. But that's between different versions of Windows NT; maybe Paragon missed something. Did you format the 16GB and 500GB with the same method? What method(s) did you use? Sorry, that I can't give you better help. Maybe it isn't even a formatting issue. How new is the USB drive or Housing? I've had issues with certain combinations of SATA2USB and Hard Drive firmware, not working on every machine.

This is just a early version of the Universal Vesa/VBE Win9x driver, from Bear Windows, patched "for Intel 915GM" Later versions, of the driver, may have improved on this patched driver's capabilities. It may have 2D acceleration. But it will not have 3D acceleration. I do admire your commitment, to find one (3D driver). I've looking into writing driver, for Win9x. Video drivers look like a lot of work. I do wonder if the Bear Windows driver could be used as a base, for a modular 3D video driver. The driver could expose a basic set of 3D implements, that rely on a GPU specific module file. Maybe even include 3D capabilities, that can be disabled or offloaded to software rendering, if not actually present in the GPU. I don't know what it would be like to target DirectX. I wonder if it might be better to target OpenGL and WineD3D. Then you could support multiple versions of DirectX. WineD3D would need to be part of the driver. Even with the GPU specific implenation(s) aside, it would be a lot of work And, I'm not even sure it would really work. It certainly wouldn't perform like a vendor driver.... Just dreaming on it, a little.

I'm sorry to hear that. My T42 just stopped turning on one day. It always ran a little hotter, then I thought it should. I blamed the GPU. I still keep it around. Donated the memory to a T40 (post Win9x Intel GPU), I had to buy in a mixed Ebay lot. I hope you find something good.