• 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. 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.
  2. 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.
  3. 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.)
  4. 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.
  5. 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?
  6. 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.
  7. 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.
  8. I am running Virtual PC 2007 as Administrator and have the Virtual Machine Network Services installed. Still, MS-DOS will not connect to the internet with the Arachne browser or other network-connected programmes that use the Intel DC21140 packet driver.
  9. Hello, everyone! I have a problem here. I'm running MS-DOS 6.22 under Virtual PC 2007 with the Intel DC21140 packet driver and for some reason, the internet doesn't work when I set the first adapter to use Shared networking (NAT). For example, when I run the Arachne browser, I end up getting a Arachne Network Error (Unable to initalize TCP/IP) when attempting to access the Google homepage. Here's what the screenshot looks like: This next screenshot has the settings of what network adapter that I'm using: If I select "Lnksys WMP54G v4.1 Wireless-G PCI Adapter" and use the "192.168.254.X" IP address, I can connect to the internet under MS-DOS and Windows 3.1 just fine. But if I select Shared Networking (NAT) and use 129.168.131.x as the IP address, the internet doesn't connect at all. The Shared Networking feature works fine in Windows for Workgroups 3.11 and later. Is there anyway how to get the internet access working under MS-DOS 6.22 and Windows 3.1 using the Shared Networking (NAT) adapter under Virtual PC? Should I post the CONFIG.SYS, AUTOEXEC.BAT and/or WATTCP.CFG configurations to see what could be wrong here as well?
  10. I had to go to this page on how to resolve the Windows Update lag issue: http://wu.krelay.de/en/ The updates that I installed in the past have already been installed so far: Windows6.0-KB3078601-x64.msu, Windows6.0-KB3109094-x64.msu, Windows6.0-KB3145739-x64.msu, Windows6.0-KB3164033-x64.msu and Windows6.0-KB3168965-x64.msu The only update that I had to installed was Windows6.0-KB3177725-x64.msu. I had to reboot and in the end, Windows Update started to work again; installed five more security updates for this month and reboot again. The next update will be in the second Tuesday in September and I will be checking to see if there are any changes that were made that will cause Windows Update to not work or not. For now, the issue has been resolved.
  11. Is anyone having this problem lately? I've been trying to update the Windows Vista x64 installation and so far, when I try to use Windows Update in the Control Panel, the green glowing progress bar under Checking for Updates seems to be moving endlessly and taking hours, if not, forever to try to check for updates. Is there a easier solution to check for Windows updates on Vista without taking forever?
  12. Running SmartDrive didn't work. While Windows is capable of handling thousands of files on a FAT partition, it can only handle up to 2 GB hard disk partitions per drive. Like I said before, if I wanted to run software on a hard disks with thousands of files, I'd avoid MS-DOS Shell.
  13. Running MS-DOS in text mode has no effect when trying to list a huge number of directories and folders it has to show. I still get a "Not enough memory. Operation cannot be completed." error. It turns out that MS-DOS Shell is a 16-bit file management and menuing system program that has a lot of bugs that will never be addressed. Even if that's the case, most of the features in MS-DOS Shell are still usable.
  14. I got it from eBay for Christmas a few years back for $30 if I'm correct. It is a commercial product that is no longer sold. The product that I bought didn't even include the Use's Manual. I'm trying to learn how to use the Custom Application feature in the Menu Maintenance and the Custom Parameter Prompting.
  15. Problem solved. I switched to Fifth Generation Systems Direct Access 5.1 and everything is all good!