• Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About ppgrainbow

  • Birthday 12/31/1975

Contact Methods

  • Website URL
  • ICQ
  • Yahoo
  • Skype

Profile Information

  • OS
    Vista Ultimate x64
  • Country
  1. This issue is still happening. It seems that it's getting harder and harder to update Windows Vista until the very end. I will be abandoning Windows Vista in a few weeks when I do a in-place upgrade to Windows 7 using the Fully Packaged Product (FPP). Sad to say that Windows Vista will lose all support in April 2017.
  2. You're welcome! That's why I don't use RAIDS in the first place. I run the hard drives without any RAID support. The full version of Windows 7 Ultimate has already been ordered and it should arrive by next Wednesday. eBay had it on sale for just $79 and it's one of the few copies that are brand new and unused. I can't wait to get the copy of it on Christmas Day!
  3. Thank you very much for the clarification! I appreciate it. It's one of these reasons why I should never use RAID software to upgrade to Windows 7.
  4. Thanks for the heads up. That's why I removed SVG Viewer in the first place. I'm gonna be downloading the drivers for the chipset, video, audio and LAN before upgrading and install the drivers after. Why is it very important that you do not do a in-place upgrade if you have a RAID array installed?
  5. Thank you for telling me! I think that I will get the go ahead and purchase Windows 7! I will install Windows 7 SP1 after upgrading to Windows 7. By the way, can you provide a list of updates that we all must stay away from? I'm sure that it caused nothing but problems to Windows 7 SP1 users. After installing Windows 7 RTM and updating to Windows 7 SP1, I'm sure that there will be features updates that were published before Windows 7 lost Mainstream Support in January 2015.
  6. Hello everyone! I have few questions regarding doing a in-place upgrade from Windows Vista to Windows 7 and keeping all of the files. 1. I currently have the 64-bit version of Windows Vista Ultimate with Service Pack 2 installed and I'm getting close to planning on upgrading to the 64-bit version of Windows 7 RTM. Is possible doing a in-place upgrade to 64-bit Windows 7 Ultimate RTM using the full retail version of the Windows 7 Ultimate RTM DVD (SKU: GLC-00182)? The lowest that I can find on eBay is $85 for the in-place upgrade version, but this is the last one that cheap. The full version only cost $89. If I officially get it, I'm gonna have to find a way to spend the remaining $115 out of the $200 budget elsewhere if I can. 2. I heard that I will lose disk space and Windows upgrade have always been a bit iffy by nature. I have concerns that applying Windows updates during the Windows 7 installation may not work as intended, especially since I updated Windows Vista via Windows Update for the past couple of years. Would it be possible to turn Windows Updates off when upgrading to Windows 7? 3. The Windows 7 Upgrade Advisor has found at least four issues that I may need to address. Here's a screenshot of what it looks like: The Upgrade Advisor is unable to find any compatibility information with Adobe SVG Viewer, EVGA Precision 2.0.0 and PlayReady PC Runtime x64. Also, the Upgrade Advisor is telling me that action is recommended if I want to update the Linksys WMP54G v4.1 PCI adapter to make it compatible with Windows 7. What should I do? Let me know your thoughts, because if miss out in upgrading from Windows Vista to Windows 7, it's too late after this year and I will risk being on a unsupported operating system come April. Update 2016-11-27: Updated PlayReady PC Runtime x64 to version 1.3 and uninstalled Adobe SVG Viewer. Two remaining issues will be dealt with when I plan to upgrade to Windows 7.
  7. Regardless of how old the bug is, it got flagged as RESOLVED DUPLICATE of bug 1315083. This is one of the reasons that I'm gonna have to abandon Windows Vista soon as it is going to reach end-of-life in April of next year.
  8. The latest Nightly version of Firefox 53, build 20161119xxxxxx+ will no longer start on Windows XP/Server 2003 or Vista since it now requires AVRT.dll from Windows 7. Apparently, without any unofficial fixes, the last good build 20161118030222 is the last to work on these OSes. Infact, Nightly builds of Firefox 53 through 20161118030222 will not work correctly, if not at all.
  9. Okay, I managed to solve the "Windows Protection Error" while the IOS device is being initalised: 1. Start Windows 95 in Safe Mode. 2. Go to the Control Panel. 3. Click on the System Properties icon. 4. In Performance > Advanced Graphics Settings, disable hardware acceleration. 5. Go to Performance > File System > Troubleshooting and checkmark the following: * Disable protect-mode hard disk interrupt handling. * Disable all 32-bit protect-mode disk drives. * Disable write-behind caching for all drives. After Steps 4 and 5 are taken, restart the virtual machine. After the virtual machine is restarted, Windows 95 setup will continue and setup any plug-and-play devices that are installed in the VM. After Windows 95 has been installed, the protect-mode hard disk interrupt handling, 32-bit protect-mode disk drives and write-behind caching can be re-enabled. Hardware acceleration can be re-enabled as well. This was tested when running the original release of Windows 95 with the -vga isacirrus parameter using Neozeed's patched Qemu 0.15.1. I've noticed that even if I manage to work around the Windows Protection error bug in Qemu 2.7, the Cirrus graphics drivers in Windows 95 will not work correctly.
  10. The amount of RAM that I tried out was 65,536 KB (or -m 65536K) which is equivalent to 64 MB. I'll see if leaving out the -cpu switch helps. If not, then I'll install QEMU 0.9.1 first and then see if I can get to work under QEMU 2.7 from there.
  11. I have a problem here. I got as far as the first half of the setup phase when attempting to install the retail upgrade release of Windows 95 (v4.00.950) on top of Windows 3.1 under the latest version of QEMU (v2.7). When I restarted the virtual machine, Windows 95 throws this error message when attempting to continue Windows 95 setup: Simply copying the IOS.VXD file into the \WINDOWS\SYSTEM\VMM32 sub-directly didn't help. Here is the current configuration used to attempt to boot up Windows 95 under Qemu 2.7: I'm wondering if this is a bug when attempting to install OS or not. Are there any workarounds on how to get the IOS.VXD error when attempting to start Windows 95 under Qemu? Thanks. (I'm sorry I had to find a way to use quotes and clean up the messy formatting. That's why I had to edit this thread.)
  12. Update 1: tried to do the following: Delete the following registry subkeys: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Config HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Adapters\ {<var>GUID</var>} HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{<var>GUID</var>} I also completely uninstalled the Linksys WMP54 v4.1 driver (including deleting the driver software for the device) and rebooted. Reinstalled the Linksys WMP54 v4.1 driver and got this error: I had to do a System Restore to revert the damage. And still the Loopback Adapter won't install. Isn't there a better way to fix the problem that causes the Microsoft Loopback Adapter to not install? I'm wondering if it has to do with one of the security permission issues or something... Update 2: Here are the logs on why the Loopback Adapter failed to install: 1. setupapi.app.log 2. setupapi.dev.log Update 3:After going through a lot of frustration, I found that in the setupapi.dev.log that the Add Hardware setup tried to copy the loop.sys file from the windows\inf sub-directory and it obviously wasn't even there. The loop.sys file was originally found in C:\Windows\winsxs\amd64_netloop.inf_31bf3856ad364e35_6.0.6001.18000_none_5d1a50f205e9484a sub-directory. I had to copy to the C:\Windows\inf sub-directory. After that I proceeded by installing the Microosft Loopback Adapter from the Add New Hardware section and it worked.
  13. Hello again! I've been trying to re-install the Microsoft Loopback Adapter from the Add New Hardware section, but for some reason, I end up getting this message according to this screenshot: I have tried to follow instructions from this page on how to fix this issue, but it hasn't worked. One user had reported that the issue was caused by security templates. Any ideas how to fix this issue?
  14. Firefox 53 will officially be released on 18 April 2017 according to the release calendar. At that time, Firefox will start adopting a nine-week rapid release cycle. And it will come just one week after Microsoft officially drops Windows Vista support. Since Firefox 53 will no longer work on Windows XP, Windows Server 2003 or Windows Vista, there will be dead code that the developers will have to remove. This will most likely make it difficult, if not impossible to get Windows XP/Server 2003/Vista working beyond FF52. After the release of Firefox ESR 52.8, these OSes will be EOL by Mozilla sometime in May 2018. That puts is over 1 1/2 years before Microsoft officially drops Windows 7 support in January 2020. Such a change comes after Mozilla ended Windows 2000 and Mac OS 10.5 support in February 2013 and Mac OS 10.6-10.8 last month.
  15. Right now more than 9% of internet connected users still remain on Windows XP and just barely over 1% of internet connected users are on Windows Vista. Extended Support for Windows Vista ends on 11 April 2017. Firefox 52 is already in nightly testing right now and if the bug was marked RESOLVED FIXED, Firefox 51 (which would be supported until 7 March 2017) would be the last mainline version. Firefox 52 ESR EOL would be sometime in April 2018. Mozilla still has more than 100 Windows XP test machines in production. While adding new features to Windows XP/Server 2003 is becoming increasingly difficult, it's still a bit too early for Mozilla to make a final decision on when Windows XP/Vista support will be curtailed. I would rather wait until early 2018 when there is a lot less Windows XP/Vista users from where it is now.