LLXX

Ok, which Samsung would you recommend? Also, you can find some useful info HERE if you're planing to buy a new LCD monitor... Here's a few that are similar to your two choices:http://www.samsung.com/Products/Monitor/LC...=Specifications http://www.samsung.com/Products/Monitor/LC...=Specifications

I'm quite sure that would get Symantec to wake up... not to mention other anti-malware software might start adopting the same path

If we want to continue to use Win98se on newer hardware this will have to be done... SciTech has a 915 driver, but doesn't have a driver for the newer chipsets e.g. the 945GM in my laptop and I've had no success in attempting to unpack the installer and force-install 945G drivers manually (I doubt there is much difference between the G and GM anyway). They do not support 3d acceleration, and 2d acceleration support is supposed to be minimal. The Intel i800-series (e.g. 865) drivers might be worth trying to force install; although it did not work in my case, I have not investigated the issue further and it may be due to the driver looking for specific device IDs before it will operate. Providing there is sufficient backwards compatibility between the 900 and 800-series, in this case it should be trivial to edit the driver so it will recognise the device ID of the 900-series chipsets. 2d acceleration should be possible, and maybe even 3d. I have found the i810 and i815 programmer reference manuals but little documentation for the newer chipsets. The closest to documentation would be Intel's open-source Linux drivers, which, while they do show the programming interface of the GMCH, have not much in the way of explanation. That driver supports a whole range of Intel integrated graphics controllers (all the way up to the newest Q965) and if a Win98se "port" of it could be done we may have a solution. However the Linux driver architecture is substantially different, so this is going to be quite a bother... The Windows 2000 and XP drivers for the 900 series chipsets are WDM drivers; recalling Win98se supports WDM drivers, maybe it would be possible to once again force the driver to work with a little bit of editing. The only problem would be missing APIs from 98se's implementation of WDM Another method would be to disassemble the default VGA drivers and add the code (obtained from either the Linux or Win2K/XP driver) necessary to handle the 2D functions. This way we should be able to get 2D acceleration, or at the very least, framebuffer mode, working at anything other than 640x480x4. I have given up on the SuperVGA+ project (writing a generic driver for almost all VESA chipsets) but this project may take off given the fact that the 900-series chipsets are becoming quite popular (in fact mobos with 915G are cheaper than those with the 865G now) and I myself now own a 945GM to experiment on. Assistance or comments/suggestions from any users here knowledgeable in Win9x driver architecture is welcome.

http://support.microsoft.com/kb/324767

A WINXP.COM that loads Windows XP from the command prompt would be nice I tried making one to load Win2000 a while ago but never finished it.

No Samsung?

See image. http://img137.imageshack.us/img137/9050/audioyi0.jpg

Should be fine for viewing television though, as images from a camera are naturally blurry and the scaling done by the LCD won't do much to them.

If you don't understand English then it would be wise to learn it.

Old indeed... FlashGet dropped the spyware/adware since 1.5 or so... I still use a heavily modded v1.50 for downloading.

If you've read through some of the threads in the Vista section apparently there's a 5-CD version of it you could download...

I remember the ISO was around 2.5Gb for the 32-bit version, and nearly 4Gb for the 64-bit one. That would've fit on 4 and 6 CDs, respectively.

http://en.wikipedia.org/wiki/Dance_Dance_Revolution

If you set in BIOS option to emulate PATA device then it will be recognised as standard IDE disk and works fine. If you want to use "native" SATA mode then you'll need drivers.

You likely did not connect the CD-ROM's Audio Out connector to the CD-IN of the sound card. It's a 4-pin connector.

Here is where your argument contradicts itself. The need to integrate the GPU circuitry on the same die as the chipset places constraints on how complex the GPU can be, since there are limits to how big you can make the die before production turnout decreases and cost increases to become prohibitive. A GPU also consumes a large amount of power, and combining it with the chipset circuitry creates additional restrictions thermally - chipset fansinks can't grow to the sizes normally found on dedicated video cards, and the chipset fansink has to cool both the chipset proper and the integrated GPU. Thus, the lower performance of the integrated GPU. The GPU die of the 6600GT is itself larger than the entire chipset's die.

You might need to set SATA speed to SATA150 in BIOS.

poor choice LLXX. Qwerty.Msi is for NT-based versions of Windows only, excluding 9xME OSes. read the System Requirements section for Qwerty.Msi. also it requires .NET Framework 1.1 or higher installed. Works on Win98se without the kernel update... also using a very stripped down .NET framework here (I hate .NET but this is the best free .msi manipulator so far, so until I can find something better...)

I suggest you backup your data and reinstall. There isn't any explanation I can come up with for this, besides something becoming very corrupted. I am not aware of any 32MB limit.

Tried starting both of them first? I know that some apps don't start the service themselves if they're not started and set to Manual, they just wait and timeout because the service was never started in the first place.

USB port might've gotten killed... they say you can plug/unplug USB devices while they're on, but if there was a static charge on the drive or it wasn't connected/disconnected in exactly perpendicular motion the port can be damage.

DOS 7.1+ kernel (in Win95b and above) supports FAT32.

Actually, I think the problem is being caused by M$'s own shell hook for generating previews and getting info of media files.BTW, unless this is a screenshot taken mid-work with many programs open, 212M is a rather high commit charge... my system boots at ~67M and doesn't go past 150 unless I open a lot of apps.

Pay careful attention to the routing of the SATA cables. http://ata-atapi.com/sata.htm

I have mine set to 250 for WaitToKillAppTimeout, 500 for HungAppTimeout, and 500 for WaitToKillServiceTimeout. I haven't experienced any problems with this, as you should have no programs running when you're shutting down anyway. The fact that it's an IBM laptop suggests that the machine came with a lot of crap installed. I bought one a few months ago and wiped the HDD, then reinstalled XP completely.