ppgrainbow

Probably because online demand for Windows NT 4.0 no longer warrants keeping Q323172i.exe patch online. If you still need this patch, it can be found on other sites such as this one: http://am.net/lib/tools/Microsoft/nt/Q323172i.exe Do a search for Q323172i.exe referencing to Windows NT 4.0 and you'll find the correct patch for that OS. The size of the file is 268 KB and has a Digital Signature timestamp of 2002-07-29 11:23:23. The date of the file, if uploaded on other websites for historical purposes, will eventually have a later timestamp as it is uploaded onto their servers, yet the file size and original Digital Signature timestamp are retained. I hope that this helps.

Thank you for telling me. Flash 12 should run okay with at least 384 MB to 512 MB of memory. Because I recently switched to a new computer at the end of February, I can no longer test installations of newer software under Windows 2000 even with UURollup until I use it under a virtualisation environment such as VirtualBox, VirtualPC or VMware Player.

Thanks so much for the help everyone. Like I said before, I already solved this issue by using StartAffinity and HStart. With StartAffinity, I made VirtualPC 2007 start with only Core 0 active. This problem applies to Windows NT 3.51 and neither Windows NT 3.1 nor Windows NT 3.5.

Okay, I've been having a issue regarding a PCMCIA to PCI card connected to my computer. The computer is working 100% perfectly, however...the new computer recently got hit with a power outage that occurred earlier this week. The PC is connected to a surge protector...so, it survived the power outage. When there is a electrical storm, if it is snowing or there is high winds occurring in my area (usually during the late Fall, Winter or early Spring), I have to put the computer to sleep or hibernate it or turn it off in any event a power failure occurs. The problem is that when the computer comes out of hibernation, a Event 9 error referencing to pcmcia followed by a Event 11 error referencing to disk are logged into the Event Viewer one second later. I used a utility called MyEventViewer from Nirsoft and this is what I got: Event 9 (error): pcmcia (2014-04-24 20:13:55) Event 11 (error): disk (2014-04-24 20:13:56) By clicking on Properties for the Ricoh R/RL/RT/RC/5C475(II), R5c520 or Compatible CardBus Controller (StarTech PCMCIA to PCI card) in the Device Manager, what puzzles me is that the PCMCIA drivers have a date stamp of 2006-06-21 and the version of the driver is 6.0.6002.18005, the driver file details show that the driver files are: C:\Windows\System32\drivers\pci.sys C:\Windows\System32\drivers\pcmcia.sys To be realistic, doing a search for the files in Windows File Manager revealed that the pcmcia.sys and pci.sys files are not even listed in C:\Windows\System32\drivers sub-directory. Three copies of pcmcia.sys and pci.sys are found in the C:\Windows\winsxs sub-directory instead. Additionally, after putting the computer out of hibernation, SpeedFan 4.49 reports that the SMART information on my "ULTIMATE CF CARD" is garbled and I have to reinsert the CF card in the the PCMCIA slot in order to make it work again. Is there a way to fix the Event 9 pcmcia and Event 11 disk errors occurring every time I awake the computer or put it out of hibernation?

Anyone had any luck trying to install Windows NT 3.51 Workstation or Server under Virtual PC 2007 with a multi-core processor? For example on the AMD FX-3800 processor running Windows Vista Ultimate x64, after attempting to install Windows NT 3.51 on a FAT or NTFS partition with the Virtual PC.exe process having all four cores enabled, this example error message appears in a blue screen: The temporary solution would be to allow Virtual PC 2007 process to use only one processor. For instance, I used Process Explorer and right =click Virtual PC.exe, set the Processor Affinity to only use CPU 0. By setting the Processor Affinity to use only CPU 0 under Windows NT 3.51, I was able to install Windows NT 3.51 successfully. Once I close VirtualPC 2007 and restart it, VPC gets defaulted to use four cores which in retrospect that causes data corruption on the Windows NT 3.51 guest to appear. Other OSes such as MS-DOS, FreeDOS, Windows 3.0, Windows 3.1 and OS/2 Warp all work without problems. It seems to me that Windows NT 3.51 guest under Virtual PC 2007 doesn't even like multiple cores. Is there a permanent solution to overcome this issue? I'm sorry if my comment clearly didn't make since or that I wasn't being all that specific, but I'm tired and I'm heading for bed soon. Update 1: Nevermind. I solved it when I stumbled upon this article regarding running Virtual PC 2007 on multi-processor and/or multi-core processors. Have a look: http://virtuallyfun.superglobalmegacorp.com/?p=154 I've learned that operating systems such as Windows for Workgroups 3.11, Windows 95 and even Windows NT 3.51 won't work correctly leading up to long latency, disk and data corruption errors to a point where the operating system will not even boot at all. When Microsoft Virtual PC was a Connectix product it was mean to run on a single CPU or single core (up to 4.29 GHz). And now since newer computers with multi-core processors are replacing older computers with single core processors, the fix would be to set the Virtual PC.exe CPU affinity to a single core before any virtual machines are started. Now to overcome this limitation, I downloaded a utility called Start Affinity. It can be found on this page: http://www.adsciengineering.com/StartAffinity/ StartAffinity is a freeware tool that is designed to start software by restricting it to certain CPU affinity masks. Since Virtual PC is not designed for multi-processor/multi-core computers, I had to enter this command to make sure Virtual PC 2007 always starts on CPU processor 0: I hope that that setting the CPU affinity to use only core 0 solves the data corruption/failed installation of Windows NT 3.51. Update 2: For some reason, StartAffinity shows the command prompt window for a brief moment upon starting Microsoft Virtual PC 2007 with only Core 0 enabled. To get rid of the command prompt window, I had to modify the shortcut properties and add this line: By using HStart with the /noconsole and /idle switches, HStart will make StartAffinity start without the command prompt window and lower the CPU priority to idle status. The Hidden Start utility can be found on this page: http://www.ntwind.com/software/hstart.html If there are any questions regarding this thread, let me know.

Thanks for the help. I rebooted my PC and I don't know if the problem went away. Windows 3.1 does work fine without the generic SVGA drivers under VirtualBox. I don't know if anyone has filed a bug report on this issue at this time. :\

Although I have Windows Vista x64 running, I will soon be installing Windows XP inside VirtualBox.

Okay, I have a problem running Windows 3.1 in the latest version of VirtualBox (v4.3.10). When I run Windows 3.1 using the patched generic SVGA drivers, VirtualBox crashes and throws this error message: To make matters worse, my Windows Vista host PC even froze for several minutes before I got a chance to use Ctrl-Alt-Delete to stop a non-responsive VM. The current settings that I have configured are the following: MS-DOS 5, 8 MB memory, 1 MB VRAM, 1 GB SCSI hard disk and CD-ROM, Windows DirectSound, SoundBlaster 16 and a AMD PCnet-PCI II NAT adapter. Windows 3.1 with the Generic SVGA drivers works well in Standard Mode, but doesn't work correctly in 386 Enhanced Mode and crashes. I recall that I used to sign-up for the VirtualBox forums years ago, but Oracle acquired VirtualBox from Sun and introduced a single login and now...I can't use my acocunt in the VBox forums anymore. Hopefully, someone will file a bug report to see what could be wrong here. I'm wondering if this is a bug with the Generic SVGA drivers not cooperating in the latest version of VirtualBox or not and that there is a workaround to it. Should I post the CONFIG.SYS and AUTOEXEC.BAT settings and determine what could be wrong with it? If not, then I will end up removing Windows 3.1 from the hard disk image until this issue gets fixed.

Hmm...I was wondering if the drivers that came from the Linksys WMP54G v4.1 and the updated November 2008 revision from Windows Update caused my computer to hang all along. With the November 2008 version of the Linksys WMP54G v4.1 drivers, if I select Normal Mode or Safe Mode with Networking, the computer will hang minutes after it starts up. But if I shut off networking and don't browse the internet, then the computer works. I did a search for "Linksys WMP54g 4.1" and "hangs" on Google and I found that people were having a lot of problems using the network card under 64-bit OSes (including Windows Vista and up). So, I'm wondering if the digitally signed drivers from 2009-08-24 did the trick: https://sites.google.com/site/linksysupdateddrivers/rt61/driver/download The file name is Linksys-rt61-200908-24.zip. I took further measures by downloading Prio, a utility to permanently change the CPU and I/O priorities, hence I had to set the CPU priority from Normal to Idle and the I/O priority to Background and limit the transfer rate from Auto down to 2 Mbps (256 KB/s limit). I kinda feel that it would save me a lot of hassle having to get a better network card that will work with Windows Vista x64, because the network card still has a lot of dust and it might need cleaning soon. I'm still also considering upgrading my power supply unit to further increase stability. Anyways, to play things safe, do not use the Linksys WMP54G v4.1 drivers from the CD on a computer running Windows Vista (or later), they may not work 100% correctly. I'll try rebooting and turning the computer off to see if the computer will still hang or not. If the problem continues, then something could be wrong with the PSU or the motherboard, preferably the CPU. Update: So far, so good. The computer is working really well, because of the updated WMP54G v4.1 drivers from August 2009. I might want to check the Event Viewer to see what other problems are found.

Okay, since I downloaded all of the updates available for Windows 2000, I think that it would be good time to download all of the files and burn it to a CD-ROM ISO incase Microsoft ever decides to de-commission the Windows Update website in the near future. Tramtrist, since I already installed Windows 2000 under VirtualBox, I currently don't have a problem accessing Windows Update under Windows 2000. I will try to reproduce this when doing a test installation of Windows 2000 under Microsoft Virtual PC 2007 x64 to see if this issue persists and if it does, then I'll get back to you.

I uninstalled AI Suite II and the services associated with it. I'm gonna look into disabling the NVIDIA Display Driver Service and reboot to see if this will fix the problem. The graphics card EVGA 8400GS is made by NVIDIA. What's unfortunate is that this graphics card is only DirectX 10 capable and NVIDIA is going to pull the plug on support for these DirectX 10 graphics cards on 1 April 2016. Anyways, I sure hope that disabling the NVIDIA Display Driver service solves this problem. However, if the problem persists then I'll get back to you and post a update. Update: Disabling NVIDIA Display Driver Service had no effect. My computer would usually be stable without being able to go online or have the network disconnected. The hard lockup usually occur when I visit the Google News page (it can be tested on browsers such as Internet Explorer 9) when almost all of the pictures get loaded and when it does, the computer stops responding (hangs). The PS/2 mouse will respond for a few seconds longer and then it freezes hard. Simply hitting the RESET button is not going to fix the lockups since it will occur again. The cause of the lockup minutes after reboot is difficult to pin down and it eventually has been that way since I got this computer over a month ago. I suspect that the problem might either be the following: 1. The Linksys Wireless-G PCI network card (model number: WMP54G v4.1). 2. Defects in the Fractal Design Integra 500 watt power supply unit (PSU). 3. Defects in the AMD FX-4300 quad-core CPU. 4. Defects in the ASUS M5A97 R2.0 motherboard overall. For which I hope that it's not that. To fix the hard lockup as a temporary solution, I had to do the following: 1. Power down the computer, wait a few seconds and then turn it back on. 2. Wait at least 10 minutes for all of the processes are initalised and then go online. 3. Browse the internet. The computer will remain as-is until I restart the computer and then the lockups start up again.

Hey again. I'm starting to have a annoying and serious problem here. Minutes after starting up my computer, I typically go online and browse the internet with my Linksys Wirless-G PCI network card and when the network connection attempts to load the images, the computer hangs hard and the mouse freezes. Looking at the CPU activity on the LCD display part of the Logitech G510 gaming keyboard, one or more of the four cores of the CPU spike up to 100% and remain there indefinitely. The only way to fix this is to shut off the computer and then turn it back on after several seconds. If the disk activity remains inactive and all of the USB devices get initalised, the computer works as-is and I can browse the internet without problems until I reboot. The operating system that I'm using is Windows Vista Ultimate x64 SP2, I have a ASUS M5A97 R2.0 motherboard with 8 GB memory and a EVGA 8400 GS graphics card. What puzzles me is that the display drivers are up to date, the memory, CPU and hard disk drive is all good, but something could be causing the computer to lock up hard just minutes after reboot. Could it be the Linksys Wireless-G PCI network card or the router that we have in the family room? The model number of the PCI network card is WMP54G v4.1. Does anyone have any idea what could be causing the computer to lock up when browsing the internet minutes after startup? If so, how would it get fixed? Unfortunately, since I bought this custom computer from AVADirect, I'm not allowed as the end-user to fix things myself as the warranty will end up being void. I spent almost $700 on a new PC and I hate finding something and replacing things that don't work correctly.

Hello again! I installed one of my favourite analog clock screen savers, Analog Clock-7 from Style 7 on Windows Vista Ultimate x64 and when it was first installed, it appeared on the screensaver list, ready to activate in 15 minutes. However, when I right click on the desktop screen by clicking Personalize > Screen Saver in the Control Panel, the screen saver is set to (None) and Analog Clock-7 does not appear on the screen saver list. Analog Clock-7.scr can be found in the \System32\ and \SysWOW64\ subdirectories. When I right click on Install, the Analog Clock-7 screen saver pops up once and that's it and then it disappears again when I access the screen saver feature in the Control Panel, although the screen saver does run when when I right click Test or Configure on the Analog Clock-7.scr file. Is there any way to fix this issue of 3rd party screensavers not showing up on my 64-bit Vista installation? Update: I solved my problem by moving Analog Clock-7.scr from the \System32 and \SysWOW64\ sub-directories to the main C:\Windows directory as a workaround under a 64-bit operating system. I expect that this workaround to work in other 64-bit Windows operating systems. Did anyone have any problems getting 3rd party screensavers working under 64-bit Vista? If so, please let me know.

Thank you very much for the help. Everything is all good to go until I either reinstall Windows Vista or replace this Dell M782 monitor.

Thank you very much! I added 1600 x 1200 as the standard resolution and it worked without problems. I will reboot the computer to make sure that this resolution sticks and update to see if it works or not. Be right back. Update: I rebooted the computer and it worked! That was pretty easy thing to do.

Hey there again! I installed the latest NVIDIA GeForce driver (version 334.89) on this ASUS M5A97 R2.0 motherboard and prior to installing the drivers for the EVGA 8400GS 1 GB GDDR3 graphics card, I was capable of getting display resolutions up to 1600 x 1200 @ 65 Hz on this Dell M782 CRT monitor. But when I installed the drivers, I was limited to 1280 x 1024 resolution @ 75 Hz. When I used Windows 2000, I had no problems getting resolutions as high as 1600 x 1200, but this is not the case with Windows Vista x64 running on this new graphics card. Is there a way to get around this limitation?

That's the tool that I already installed on my new machine. As I said before, all of the updates installed successfully without a problem.

Compress the log file using 7Zip or the compressor of your choice, upload the file to the file sharing service of your choice (such as mediafire), then post a link to that file here. Cheers and Regards Thanks for telling me. I compressed the CBS.log file as CBS-2014-03-03.zip and uploaded it to my 4shared account. You can find it here: http://www.4shared.com/zip/CUwrhdZTba/CBS-2014-03-03.html I will remove the link once you look over the logs.

Okay. The CBS.log file has grown to 46.5 MB since I updated my computer. I will have to do a SFC /SCANNOW routine in a elevated command prompt to know what could be causing it. With that said, I will have to delete the CBS.log file. When the SFC /SCANNOW procedure is done, the log will be recreated. I'll post the results when I'm finished. Update: I ran SFC /SCANNOW and here's the message that I received: I have tried to upload the CBS.log file here, but I got a error that the file was too big to upload. The CBS.log file quickly grown to at least 885 KB and I can only upload up to 500 KB of files. Sorry about that. I wished that I gotten around this somehow.

Thanks again! Windows Vista would run far much better with memory maxed out at 32 GB RAM. On some motherboards, mainly server ones, Windows Vista will run with up to 128 GB RAM. If more than 128 GB of memory is installed, Windows Vista 64-bit will only recognise 128 GB unless the OS is upgraded to either Windows 7 or Windows 8. By the way, I had to apply Windows Vista SP1 first and then update it to SP2.

Okay, it's been nearly two days since I did a clean installation of Windows Vista Ultimate (x64 version), I installed most of the updates from the Windows Update applet. But, I ran into problems trying to install the remaining 15 updates listed below: I get a error code 80070490: Windows Update encountered an unknown error. However, this eventually means that the CBS Manifest file that is needed to install updates is corrupt. I've noticed that some users even receive the 80070490 error code when trying to reinstall/repair Windows or perform a factory reset. As I may have to manually download the files listed above and determine if it will work correctly on this machine or not, iIs there a way to get around this error? Update: To get around this, I had to manually download each of the files individually to get around the 80070490 error. The error may re-appear when Microsoft issues the next round of updates on Patch Tuesday in more than a week from today.

The reason is power consumption and speed issues. When I was on Windows 2000 on a unicore processor with 2 GB DDR RAM, it prevented me from browsing the web and running flash player at native speed regardless of the fact that I had UURollup installed. As for power consumption, I simply not have to use so much electricity as I will soon have to get rid of the old 60 watt CRT TV in favour of a PCIe TV tuner card. With that said, I backed up all of the data to a hard disk image, wipe all of the data and is now planning to either sell the old PC or recycle it completely if no one is interested in it.

I know how you feel. The good news is that I'm finally on my first new desktop computer in more than 13 years!

Good for you! The desktop computer that I used originally came with Windows Millennium pre-installed and it was originally branded as a HP Pavillion 8770c with only 128 MB of memory (512 MB maximum). The Pavillion 8770c had a 850 MHz AMD Athlon processor. However when I first used it, the desktop computer frequently locked up, because the processor was faulty. That was more than 13 years ago and this is now. It will only be a matter of time when I finally get the new computer.

Jaclaz, the limitation issues involving the RAM that I'm facing on this laptop. Right now, FinitySoft Memory Manager is reporting just 3.11 MB of RAM remaining. By the way, your comment is very brilliant! I chose the MS-DOS family of operating systems, because it's plug-and-play (PnP) compatibile. I can plug in devices to one of the two PCMCIA slots on this laptop and Windows 95 will be able to recognise them right away...that is if the hardware still supports it. The Linksys WPC11 PCMCIA v2.5 wireless network card and the 8 GB SanDisk Ultra Compact Flash card both work under Windows 95 OSR2 without problems. Windows NT 4.0 on the other hand has no PnP support by default, but is much more stable than Windows 95.