ppgrainbow

That's true. It's obvious that I'm gonna have to get the IDE cables replaced as they're going bad. I believe that the bad IDE cables already destroyed the 30 GB hard drive and it's attempting to destroy the CF card even if it's fine and has only been in use for a couple of days. To make matters worse, it turns out that some adapters don't handle the ATA protocol correctly and some motherboards will NOT even recognise the CF card on the CF-to-IDE adapter.

There is no support for REMOVABLE IDE Drives. They are always assumed to be FIXED.Any switch on the CF Card would be ignored. If you want to use that CF Card as a removable drive, you need to connect it through an USB Adapter. Marginal Hardware could be the IDE to CF Adapter Card or the interface circuitry on the Motherboard. You need to run further tests to determine which or if it is a connectivity problem instead. Thanks for the help. It's obvious that SanDisk stopped supporting the option to treat CF cards as fixed disks. I apologise that I didn't respond to your comment earlier. I spent the entire weekend attempting to re-install Windows XP Tablet PC Edition on the CF-to-IDE card and remarkably, it worked. Here's what I did to make the CF card work on the TC1000: 1. In order for the CF card on the CF-to-IDE adapter to work properly I had to leave only one screw sealed on the right side of the hard drive door as having two screws to seal the hard drive door will mess things up. 2. I was able to re-install Windows XP Tablet PC, but not without only formatting the SD card to NTFS at 4 KB clusters to prevent data corruption. I used the botched Windows XP Professional setup found in the \I386 folder and although it reinstalled the OS successfully, it failed to install the Tablet PC drivers. The SD card was previously formatted as FAT32 at 32 KB clusters and ran into a Unknown Hard Error trying to move around the tablet PC display. When I shut down the tablet PC computer and powered on, the unit wouldn't boot anymore and I ended up with a "Operating System Not Found" error. The end result is that when I attempted to boot from a floppy diskette on the USB floppy, several gigabytes of data on the CF card was corrupted! So, I had to start over. 3. I attempted to use the three CD-ROMs to boot the recovery disks with the USB DVD ROM drive, however it wasn't very helpful as the installer couldn't find the drives. To work around this, I had to run the three Compaq TC1000 System Recovery ISOs through a VM under Microsoft Virtual PC 2004. I used a 10 GB virtual hard disk image as a example. The only trouble was that I had to use the host CD-ROM to restore the second disk as the recovery disks couldn't properly recognise it! 4. When it was finished, I shut down the TC1000 Recovery VM over to a ZIP file under the name TC1000.zip and in a FAT32-formatted 4,000 MB hard disk image with a date stamp of 2003-02-19. The contents of the recovery disk inside the hard disk image is not bootable and it should have at least 17,875 files in 1,415 directories with at least 9 directories on the root drive. The contents will take up at least 2.69 GB of disk space (2,866,071,172 bytes) with the \WINDOWS directory taking up almost 1 GB of disk space (1,073,242,159 bytes). If you exclude the HIBERFIL.SYS and PAGEFILE.SYS files, the contents to setup Windows XP Tablet PC was stripped down to a bare minimum of 2.08 GB (2,237,412,996 bytes). With TC1000.ZIP stuffed in a ZIP file, the file gets compressed to 1.35 GB (1,449,466,767 bytes) 5. The hard disk image was then mounted using IMDisk and it recognied the hard disk images as Drive I. The 32 GB Compact Flash card was recognised as drive H. In order to re-install Windows XP from the hard disk image to the CF card, I ran this command: The transfer rate of the files was slow as I placed the CF card on the PCMCIA adapter through a PCMCIA PCI slot on the back of my desktop computer and the end result is that it took a couple of hours to complete the transfer from the hard disk image to the CF card. When it was all done, I then placed the CF card back on the CF-to-IDE adapter faced down to the IDE controller, used one screw to seal the right side of the hard drive door, turned the tablet PC back on and Windows XP Tablet PC Edition started up again! In order for the OS on the CF card to run reliably, the pagefile and hibernation features had to be turned off with System Restore disabled. The only issues remaining is that I run into STOP errors (BSOD) when attempt to vibrate the tablet PC, as well as Event 11 errors referencing to disk, which in turn attributes to possibly either a loose or faulty IDE controller on the motherboard. Loose or defective IDE controllers are often attributed to hard disk errors, including retired sectors on the drive development of bad sectors. The CF card on the other hand is designed for extreme environments as advertised.

Hey there! I need some help here. I have installed Windows XP Tablet PC Edition 2005 from the USB flash drive onto the Compaq TC1000 tablet computer, however...I've ran into a problem to a point where Tablet PC components aren't installed and during Windows XP Professional Setup, I receive this message: Does the tabletpc.cab file exist under the \CMPNENTS directory, btw? In order to setup up Windows XP TPC, I have to boot from the floppy diskette and use the USB flash drive to set the OS up and the flash drive itself is not bootable. Right now, I'm in the process of trying to fix this. The PNY Attache 1 GB USB flash drive is 984 MB actual capacity with 147 MB remaining. In the \CMPNENTS directory on drive G, I have added \NETFX and \TABLETPC sub-directories and added the \I386 sub-directory in the two of the mentioned sub-directories, but the contents inside the directories are totally empty: \CMPNENTS\NETFX\I386 <-- Files from .NET Framework \CMPNENTS\TABLETPC\I386 <-- Files for the Tablet PC. I also have the \COMPAQ and \I386 directories on drive G as well and the files to setup Windows XP Tablet PC Edition are in the \I386 directory by default. Can you give me a full explanation of what I can do to fix this? The recovery CDs that I got with the Compaq TC1000 do not work at all, btw. Update: The files are identified as a OEM version of Windows XP SP1 with a datestamp of 2002-08-28. I'm not successfully able to find any files without having to look into the files on the recovery CDs.

The misrecognized CF Card Identification String indicates either a poor connection or marginal hardware.The deviations from the correct ID are all in Bit #1. Check your connections and reinsert the card. If this doesn't help, try a different adapter and cable. If cdob is correct, then you don't need the BOOTMAN DDO. The 48BITLBA.EXE Program should show the correct size. I knew it! I kinda had a feeling that the TC1000 either has a poor IDE connection or marginal hardware for which it adversely affects the CF card. Out of frustration, I had to re-partition the CF card and reformat the drive again. I'm currently running SCANDISK from MS-DOS to see if has any effect on the CF card itself and if it doesn't, then I might have found the culprint of what could be wrong here. I will leave the hard drive door open to see if it mitigates the problem temporary. I will also need to run the NAND Athens ID Drive Config Word Change Utility after MS-DOS finishes the SCANDISK session. I kinda have a feeling that the CF card might be set to REMOVABLE by default instead of FIXED. By the way, what do you mean by "marginal hardware" associated with the Compaq TC1000 that you might ask?

The "Maintenance and Service Guide Tablet PC TC1000" refers hard drives 40 GB 311240-001 30 GB 310668-001 The BIOS should detect the full capacity out of the box. Most likely there is another reason. Which adapter do you use? I would try another Compact Flash to IDE adapter. Unkonown Compact Flash to IDE adapter example http://www.daniel-boehmer.de/thinkpad-cf/ The model numbers for the 30 GB and 40 GB hard drives were officially designed for the TC1000. No more IDE hard drives of these exact capacities have been produced as the replacements hard drives are all labeled as used. The BIOS will be able to properly recognise hard drives (60 GB, 80 GB, 100 GB and 120 GB) and SSD compatible drives (16 GB to 128 GB) up to 128 GB due to the 28-bit LBA limit in the BIOS and the motherboard as a whole. I tried inserting a 8 GB CF card into the CF-to-IDE adapter and for while FDISK recognised the capacity as 7,625 MB, it would still revert to 24 MB if I even try to mess with it. For CF to IDE adapter as a whole, this is a hit-and-miss issue. Some CF cards on CF-to-IDE adapters will work on various laptops while some will have issues and not operate correctly, if not at all. The CF-to-IDE adapter that I bought from eBay was from Hong Kong. But after reading the article, I found it seriously insulting to find that the CF pins being on the wrong side and deliberately turned upside down. Ironically enough, I cannot tell if the 32 GB CF IDE card is being identified as either a removable or a fixed disk and it's going to be a challenging issue as the TC1000 has poor BIOS support. As a result of this, neither MS-DOS nor Microsoft Windows cannot install to removable devices and will eventually refuse to operate properly. I'm hoping to find a workaround to fix the issue with the BIOS improperly recognising the CF card on the CF-to-IDE adapter. Update: I found a utility called the NAND Athens ID Drive Config Word (Fixed/Removable) Change Utility Version 1.4 (or ATCFWCHG.COM). I don't know if it will work under MS-DOS or not, but I'm willing to give it a try.

If you check the README.TXT, you will see that BMINST.COM is not provided in the Demo. Only the DFMINST.COM program is provided. This allows you to create a Floppy Disk that can be used to run the Demo.SInce your Hard Drive and CF Card are less than 137GB in size, the DDO will automatically unload and have no further affect so you will see no difference. The standard Demo only supports 48-Bit LBA Mode and passes anything else back to the BIOS. Although I have had a few Customers for the extended BOOTMAN DDOs that you need, there never was enough interest to write an extended Demo. Thank you for telling me. I believe that there was never enough interest to write a good demo about your utility. So, it turns out that the issue might be something other than the botched 504 MB limit. For me, I tried to insert and re-insert the 32 GB CF card into the CF-to-IDE adapter on the back of the unit. However, it turns out that the BIOS was being way too sensitive to properly operate the 32 GB CF card. For a while, it would properly recognise the CF card on the CF-to-IDE adapter as 30,514 MB in capacity assuming that the BIOS recognised it as "SanDisk SDCFX-032G-(PM)", but the next time I hit CTRL-ALT-DELETE, the BIOS would misrecongise the CF card as "QalDisi QDAFX-030G-(PM)" again! I'm assuming that either the Compaq TC1000 apparently has 1. Very poor BIOS support to a point where the BIOS almost always does not recognise CF cards on CF-to-IDE adapters correctly. 2. The IDE cables on the motherboard are loose. 3. It maybe possible that the motherboard is possibly going bad and unfortunately, there might not be replacement parts available. I can always attempt to re-insert the CF card in the CF-to-IDE adapter to see if the BIOS is recognising the CF card correctly, but it turns out that the unit might not last forever.

Thanks for the help. First of all, can I have the link to the BOOTMAN DDO utility? By the way, I'm using a utility called MHDD 4.6 and detected that the CF drive has zero sectors! So, something could be wrong here. There is no link to the BOOTMAN DDO Package that you would need as it is not free.There is a Demo with documentation at: http://rloew1.no-ip.com/Programs/Bootman.htm This Demo won't work in your Computer. It extends the BIOS limit from 137GB to 145GB. Since your limit is a lot lower it won't do much. It does have an Utility called 48BITLBA.EXE that you can run to test your BIOS with your Hard Drive and CF Card. I am not familiar with MHDD. I have tested BOOTMAN2 with Windows XP and I assume BOOTMAN would also work. Thanks for the help. The CF card is far from the 128 GB limit and a couple of gigabytes far from the 32 GB limit. If I insert the CF card into the CF-IDE adapter face down, the BIOS would detect the IDE hard drive as "SanDisk SDCFX-032G-(PM)" but when I try to reboot, for some reason, it garbles up the hard disk identification in the BIOS! Edit: I tried the BOOTMAN demo utility and not only it's missing the BMINST.COM utility, the utility wouldn't even work from a floppy diskette drive.

Thanks for the help. First of all, can I have the link to the BOOTMAN DDO utility? By the way, I'm using a utility called MHDD 4.6 and detected that the CF drive has zero sectors! So, something could be wrong here.

Yes!Ditto for the Hard Drive. Thank you for telling me. Which dynamic drive overlay software utility should I use to at least boot MS-DOS 7.1 and then install Windows XP? Just curious.

Hey there! I recently got a technician to install a 32 GB Compact Flash memory card in which 29.8 GB is supposed to be usable, but I'm faced with a new problem. The BIOS isn't even properly recognising most of the 29.8 GB, but according to BootITNG 1.87 and MS-DOS 8.0 FDISK, only the first 504 MB is recognised! To make matters worse, FDISK from MS-DOS 7.1 is only recognising the first 24 MB of the CF card! I paid nearly $80 for a 32 GB CF card and an additional $4 for a Compact Flash to IDE adapter and I would absolutely hate to see that I wasted $84 on something that does not work correctly, if not at all. The Compact Flash card on the CF-to-IDE adapter is identified as a Sandisk 32 GB Extreme CompactFlash memory card with the model number SDCFX-032G-A61 and the BIOS identifies it as a QalDisi QDAFX-030G-(PM). I am using the CF card as bootable to attempt to reinstall Windows XP SP1 from the MS-DOS 7.1 prompt on the Compaq TC1000, but it turns out that the BIOS isn't even cooperating at all. In the main section of the BIOS, the BIOS version is 0F13 (BIOS date 2003-10-06) with the KBC version of 19.29. Serial number and asset tags are identified as KRD33905DJ. Would I have to use a dynamic drive overlay (DDO) to get the CF card in the Compaq TC1000 to recognise properly or other methods to get the CF card recognised at full capacity? If so, please post your thoughts as I'm looking for answers here. Update: The BIOS continues to misidentify the SanDisk 32 GB card as "QalDisk QDAFX-030G-(PM)". What's worse is the when I attempt to write the boot partition on the CF card, and when I either reboot or press CTRL-ALT-DELETE, all of the changes are lost! I already destroyed the 30 GB hard drive and is on the virge of ditching the Compaq TC1000 if issues aren't fixed.

I'm very sorry for the delay The update is ready. Check this post for details. Thank you for telling me. I will test the latest version of UURollup in a VM and report back to see if there are any problems associated with the UURollup v11 daily update.

I have run Windows NT 3.51, Windows NT 4.0 and Windows 2000 in a virtual machine before. Virtual machines such as Bochs, Qemu, VMware, VirtualBox and Virtual PC all play a role. It all depends on how much storage and memory that you assign to the virtual machine. The larger the storage and memory requirements, the better. Since Windows NT 3.1, a absolute minimum of at least 512 kilobytes of base memory (low memory) and 7 megabytes of extended memory is required in order for it to run and at least a 100 MB hard disk image for testing purposes. Windows NT 3.51 and Windows NT 4.0 will recognise up to 4 GB of system memory, however is a drawback. According to this page regarding information on large hard drives, Windows NT 3.51 and 4.0 are limited to a 4 GB partition upon setup and will not properly support IDE hard disks above 7.84 GB (1,024 cylinders, 255 heads and 63 sectors per track) without workarounds to overcome this limitation. The limitations are caused by the ATAPI.SYS driver shipped with Windows NT 3.51 and Windows NT 4.0. Speaking of Windows NT 4.0, the limit applies only to the boot partition where the OS is installed with Service Pack 4-6a applied. Even with Windows NT 4.0 SP4-SP6a installed, the OS will only properly support hard disks with 28-bit LBA which translates to 268,435,456 sectors or up to 128 GB. As far as I know, without any hacks or workarounds to overcome the 28-bit LBA limitation on secondary hard disks, Windows NT 4.0 might not properly support hard disks larger than 128 GB without a high probability of data corruption. I have yet to test these limitations when running Windows NT 3.51 or Windows NT 4.0 under VMware Player.

Okay, when I installed Windows NT 4.0 Workstation under VirtualPC, the 256 colour icons displayed on the desktop remained intact. With TweakUI installed, you could remove the annoying arrows from desktop shortcut icons and with the Desktop Themes from the Windows NT 4.0 Resource Kit, you had the ability to change desktop icons. However, installing Internet Explorer 4.01 SP2 with Active Desktop support broke the ability to add or remove the arrows on the desktop shortcut icons and eventually defeated the ability to use Desktop Themes to properly change desktop icons. To make matters worse, the security update KB313829 even broke the ability to properly remove annoying arrows from Desktop shortcut icons! While this is not a issue under all editions of Windows 95, I bet that this affected users running Windows NT 4.0 SP6a, Windows 98 and Windows Millennium Edition. Additionally after the updates to Windows 95 have been installed, you could always install Microsoft Plus! for Windows 95 to get the 256 colour desktop icons. The current version of SHELL32.DLL installed in the C:\WINDOWS\System32 directory is 4.72.3812.600 with the date stamp of 2001-12-06 14:23:20. I checked this page regarding the patched SHELL32.DLL bug and it doesn't seem to be too much of a help here. And the SHELL32.DLL fix is only designed for Windows 98 and may eventually not work correctly under Windows NT 4.0 as the size of the file is smaller. Is there a way to fix this complicated issue without having to re-install Windows NT 4.0? I know for sure that simply only removing the arrows is not going to be enough here.

Thank you so much for uploading the Mark4NTFS.zip utility! I deeply appreciate it. Because I installed NT 4.0 on a NTFS v1.2 partition, Windows 2000 touched the partition when I mounted the hard disk image using IMDisk and it upgraded the filesystem to a point where CHKDSK refused to run. I will need to revert to a NTFS v1.2 using this utility. Edit: Thanks to everyone else for helping me resolve this issue. The Mark4NTFS.zip utility will need to be available for historic purposes! By the way, I have a couple of questions regarding Mark4NTFS utility. 1. Has the utility been tested on NTFS formatted hard disks and other media larger than 7.84 GB? 2. Has Mark4NTFS been tested on Windows NT 3.51 as Windows NT 3.51 also uses the NTFS v1.2 filesystem to partition hard drives?

That's what I've been thinking. I sure hope that someone has a backup copy of Mark4NTFS.zip as it is no longer available online...even via the Internet Archive.

I don't know if the author of the defunct website regarding MARK4NTFS.zip will respond as the e-mail account associated with it was disabled or discontinued.

Thanks for the help. This is obviously a known issue. I don't know if anyone has a backup copy of Mark4NTFS.zip or not. Now as for the NTFSCHK utility, I copied the 5 files from a Windows 2000 installation ISO (autochk.exe, ntdll.dll, c_437.nls, c_1252.nls and l_intl.nls) and placed them in C:\SYSTEM32 directory. When I attempted to run NTFSCHK, I get this error message: I'll find some workarounds to correct this issue tomorrow. For now, I'm off to bed.

Hello, everyone. I recently did a fresh install of Microsoft Windows NT 4.0 Workstation inside Virtual PC 2004, allocated 64 MB memory to the VM, created a fixed 4 GB hard disk (4,095 MB) image, partitioned and formatted the hard disk as NTFS v1.2 file system. Windows NT 4.0 installed without a hitch. However, when I used a disk mounting utility called IMDisk to view the contents of the partition formatted as NTFS, Windows 2000, the host OS upgraded the NTFS partition to version 3.0. After I unmounted the hard disk image, I powered up the Windows NT 4.0 Workstation VM again and when I attempted to run the CHKDSK command, I get this error message: I looked at this page regarding Windows NT 4.0 CHKDSK refusing to check NTFS v3.0/v3.1 volumes (KB196707) and it wasn't very much of a help at all. What baffles me is that I looked at this forum thread, NT4 NTFS Versions by nt4-ever on 2007-07-19 and it mentioned hacks and workarounds including NTFSCHK, a utility to run the Windows 2000 version of CHKDSK from Windows NT 4.0 and another utility called Mark4NTFS, a Windows NT 4.0 utility to revert the partition from NTFS v3.0 down to NTFS v1.2. I tried to download a utility called Mark4NTFS.zip and found that the site that was hosted on it was gone! There was also mention of the KB872952 hotfix, but I can't seem to find the hotfix available for download at all either. Are there any good utilities or disk hex editing hacks that will help fix this problem? I know that the consequences are that every time I attempt to mount a NTFS v1.2 formatted volume with IMDisk under Windows 2000 or Windows XP, it will upgrade the version of the file system on the mounted hard disk image. Let me know what you can come up with.

Thanks for the help. I was always wondering if installing it under the \Astra directory and if possible renaming it as \Trillian would solve this or not. Edit 1: Installing it in a different directory didn't even work. I think that it would be a good time to do some investigation of what is causing Trillian 5.4 on Win2K to not work correctly as it did under Trillian 5.3. Furthermore, I somehow ran into a error when attempting to uninstall a second copy of Trillian on this machine: Until the investigation has been made, I will be using Miranda IM, Skype 4.2 and Mo-Footer. Edit 2: I downloaded the update, Trillian 5.4 Build 13 (trillian-v5.4.0.13.exe) and it finally fixed the connection failure issue!

Thank you very much for the help! I will be able to install it under the Win2K VPC soon.

Remember that you can just use the official Java installer if you've got BWC kernel or UURollup installed and I'd also recommend checking my download Archive and go to Programs/Java Okay, I downloaded jre-6u65-windows-i586.exe from the Java archive page on your site and I had little trouble getting it to work. When I attempted to install it on this machine, I get this error message complaining that the Windows Installer Service could not be accessed. Additionally, when I attempted to start the Windows Installer in Control Panel > Administrative Tools > Services and then hit Start to start the service, I get this error: Luckily, I was easily able to correct the problem by typing this command in the Start menu by typing in the Run command: msiexec.exe /regserver With that, Java 6 Update 65 installed successfully without problems. The same thing applies to Silverlight 5.1.20913.0.

As far as I know, Microsoft issued a botched security update that caused SVCHOST CPU usage to spike to 100%. Installing Update KB2879017 fixed this problem. http://www.microsoft.com/en-us/download/details.aspx?id=40390

I recently updated to Trillian 5.4 Build 12 (despite the fact that it has been complied with Visual Studio 2008) on my UURollup-patched Windows 2000 machine and I have found that I could no longer sign into my Trillian account. I'm ending up with a yellow exclamation mark next to my username and end up with the error message: Trillian 5.3 previously worked without problems and when I upgraded to Trillian 5.4, I found that I could no longer sign in to any of the IM services that I signed up. And to add insult to injury, changing the password makes no difference. Update 1: I tested Trillian 5.4 under a Windows XP SP3 VMware VM machine and it worked without problems. I might need to test the Trillian 5.4 installation under a clean Windows 2000 VPC VM to see what dependencies were added. Update 2: I did a test installation of Trillian 5.4 under the Windows 2000 Virtual PC VM and got this error message: Despite the error message, mentioned above, Trillian 5.4 did install correctly without problems. But when I tried to execute Trillian 5.4, I get this error message: As a result of this error, Trillian 5.4 under Windows 2000 refuses to proceed any further beyond initialising directories. As far as I know, the flag GetAdaptersAddresses is only supported on Windows XP SP1 and later. As for DnsFree flag, I don't know which Service Pack under Windows XP is supported. I did a search for it under Google, but it wasn't any use. When I used Dependency Walker to investigate which entry points were used in trillian.exe, SymGetModuleInfoEx and SymGetModuleEx64 were used in IMAGEHLP.DLL, I believe that they're only found in Windows XP SP2 and up. Are there any workaround to make Trillian 5.4 work under Windows 2000? If so, please let me know. Update 3: I had a look at this page regarding DNSAPI.DLL exports and has concluded that the DnsFree function is only available on Windows XP Service Pack 2, Windows Server 2003 Service Pack 1 or later.

That sounds awesome!

Chrome2K 0.60 doesn't work with Google Chrome 30 and there's no way to update to Chrome2K 0.61 right now. I was hoping that the URL link gets fixed soon. I managed to download it onto the root directory of my internal hard hard drive and it worked. I updated Chrome2K to version 0.61 and patched Chrome 30 successfully. I managed to save the CAB extension as a ZIP file on one of my USB hard drives as a backup.