• 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. Problem solved. I switched to Fifth Generation Systems Direct Access 5.1 and everything is all good!
  2. Thank you for moving the thread. I appreciate it.
  3. Yikes! I posted this in the wrong category and I can't delete it! Can someone move it to the correct category? Thanks!
  4. 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?
  5. 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.
  6. 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.
  7. 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.
  8. I've been looking at finding a different file manager/menu system that will handle so many files, but no such luck. If I have found a good replacement menu system, I'll let you know and go from here.
  9. Hi there! I've been having a awesome time running MS-DOS 6.22 (and other operating systems) in the DOS Multiboot virtual machine (Virtual PC 2007). The guest machine loads the MS-DOS 6 Shell at startup and I have configured a awful lot of software to launch on that OS. The problem is that the boot drive where MS-DOS 6.22 resides has nearly 10,000 files and 450+ directories (I'm pretty luck to see that MS-DOS Shell is capable of reading up to 65,535 files before wrapping back at zero), I get this error message when attempting to view the files on the boot drive itself: Have you ever run into this issue when you have several thousands of files totaling hundreds of megabytes of used disk space on the drive alone? Is this a bug with the MS-DOS/PC-DOS Shell and it is unable to search so many files that it can find? Can this issue be corrected by the way even with 64 MB of usable memory installed?
  10. Yep. Java 6 still remains under paid (extended) support until December 2016. After it comes to a close, Java 6 will go into sustaining support which will last an indefinite period of time. According to the Java version history on Wikipedia, Oracle made paid support for customers running Java 5 until May 2015...after which that version was completely retired. Oracle stopped providing premier customer support for Java 6 last December.
  11. For anyone who is still using Java 6, Oracle has released update 115. Has blackwingcat updated JRE 6u115 to be compatible with Windows 2000? As far as I know, Oracle will continue to provide paid support for Java 6 until December 2016 after which it will go into Sustaining Support and will no longer be updated at all.
  12. Thanks for the suggestion. I no longer have the laptop now. I will keep this as a reference, in case I ever decide to get another one in the near future.
  13. That's what I've been thinking. The laptop totally lacks legacy USB support in the BIOS as well as floppy drive and PS/2 support. That doesn't make me too happy. It just wouldn't even be fair to stuff only Windows XP (requires no less than 1.5 GB of free space) on a SSD since it's the only supported OS by HP.. Right now according to NSSI, 658 MB of the 7.44 GB of disk space has been used across all partitions on the 8 GB SSD so far. I might have better luck with Windows NT 4 since it requires only 110 MB of disk space to install it. Update: I wiped MS-DOS 7.1, installed Windows NT 4.0 on the 8 GB SSD, formatted the drives as a NTFS 4 partition and those attempts were not successful. I'm now stuck with the Windows NT 4.0 boot menu and any attempts to select either options (normal or VGA mode only) throws a STOP 0x78 INACCESSIBLE_BOOT_DEVICE. Attempting to wipe the partition and recreate the partition was no use at all. The SSD is dead after 19 days of use and it appears that the IDE controller or the motherboard could be failing also. Sorry if this was a total waste of time getting the SSD working although it only worked well on a FAT32 partition under MS-DOS 7.1.
  14. I've been thinking that a PS/2 to USB adapter could work. I can't guarantee that it will work on the zt1135, because the BIOS does not fully support USB. If it doesn't work, then I could be clearly out of luck here.
  15. I'm lucky that I can only do this through USBASPI.SYS and DI1000DD.SYS as the BIOS has limited USB capabilities outside Windows. As for other USB devices such as a USB keyboard or USB mouse, I'm not so lucky since the BIOS doesn't support legacy USB keyboard and mice devices and the BIOS options are very limited.