• 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. 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.
  2. 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.
  3. 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?
  4. 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.
  5. 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?
  6. 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.
  7. 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.
  8. 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.
  9. Problem solved. I switched to Fifth Generation Systems Direct Access 5.1 and everything is all good!
  10. Thank you for moving the thread. I appreciate it.
  11. Yikes! I posted this in the wrong category and I can't delete it! Can someone move it to the correct category? Thanks!
  12. If you're using PC virtualisations such as Virtual PC, VMWare Player/Workstation, Microsoft has a tiny utility for MS-DOS called IDLE. I'm gonna tell you why you shouldn't use that utility if you have a mouse installed. It's only bytes in 128 bytes size and it's only meant to slow reduce CPU utilitisation of the first core, because DOS does not properly utilise the HLT command thus always consuming 100% of the CPU. However, when you run DOS-based programmes and have the following: 1. The IDLE driver installed. 2. A compatible mouse driver installed. 3. Move the mouse around and type random keys. The mouse acts and jumps around erratically even if you barely move the mouse! The only way to fix this is to uninstall and reload the mouse driver. To prevent this from happening, get rid of the IDLE utility and use the FreeDOS APM driver, aka FDAPM (7.3 KB) and type FDAPM ADV:REG at the command prompt. The utility takes only 928 bytes of base memory. I'm wondering if using FDAPM will have a negative effect on some DOS software or not. Thoughts?
  13. GIMP 2.8.18 has been released. However, without any tweaks, the latest version of GIMP will not run on Windows Vista. To get GIMP 2.8.18 running on Windows Vista and overcome these restrictions. 1. Right click your mouse and click Properties. 2. Select Compatibility tab. 3. In the Compatibility mode, select Windows Server 2003 Service Pack 1 and press OK. I'm wondering which entry points for GIMP exist in Windows XP SP3 and Windows 7 SP1, but NOT in Windows Vista.
  14. I don't think that switching to FreeDOS is going to help. I'm fine with MS-DOS 6.22 and the 2 GB FAT16 limitation. Unfortunately, FreeDOS's CHKDSK program is riddled with bugs on FAT16 formatted hard disks. I'm also using FreeDOS on the 8 GB FAT32 partition (first hard disk), but only as doing maintenance work.
  15. Thanks for the help. I did post in the Vogons forum late last year. It wasn't until MS-DOS 7.1/Windows 95B that FAT32 support became mainstream. FAT32 was introduced as early as MS-DOS 6.23, but it was only available for the US government, military and banking institutions.