GameX

Members
  • Content count

    26
  • Joined

  • Last visited

Community Reputation

0 Neutral

About GameX

  • Rank
    Member

Profile Fields

  • Primary Operating System
    Linux

Profile Information

  • Gender
    Male
  1. Hi, I wasn't active since a while, but this forum is really useful in case I need advanced help with Windows; So I did a few harmless partititions modifications to boot another OS (MS-DOS 7.1 next to Windows 7... Followed this tutorial, dead easy. http://www.thpc.info/dual/7/install_dos710_on_win7.html Wanted to see if it was possible at all, DOS is very basic), and it worked. I couldn't boot on DOS without a GRUB CD, so in a attempt of making this working, I've moved the Windows 7 boot files on another partition like suggested on the website, and everything screwed up (Nice...) . So after multiple attempt to fix the bootloader (I was optimistic, used to this stuff), which no one worked, I've performed what they call a "Nuclear holocaust" here: https://neosmart.net/wiki/recovering-windows-bootloader/#Attempt_Three_Nuclear_Holocaust It worked, and is good to know for the next completely dead bootloader I have to fix. I later had an error message: Windows failed to start - Winload.exe Windows cannot verify the digital signature for this file. It appear this error happen due to an older Winload file used, possibly. Might have happened when I restored the bootloader. I managed to fix this by copying a backup, that was located in "C:\Windows\System32\Boot". Then I was able to boot in Windows again, but now had the ugly Windows Vista bootscreen. I suspect this happened, because the Winload file I've copied was an English version, possibly from Vista. I now have an English bootloader, rather than a French one: https://dl.dropboxusercontent.com/u/67605655/winload.jpg Tried these solutions without success: http://www.askvg.com/fix-windows-7-boot-screen-changed-to-vista-styled/ http://www.mydigitallife.info/fix-and-restore-windows-7-boot-screen-that-changes-to-vista-style/ http://www.sevenforums.com/installation-setup/27101-boot-screen-reverted-vista-after-repair.html Would copying a fresh Winload.exe from a clean Windows 7 Pro fix this ? Thanks for the help, I appreciate it.
  2. Hi Night Hawk, I know I'm really late ( ), but I just want to tell, in the end, I never managed to get any further than that ( XD ), besides all my ressearches. I've tried a ton of differents drivers, but that won't work. I've even installed an English version, fully updated, and applied the unofficial Service Pack 5.1 and Update Rollups, no luck. Just saying. Well, at least, I got it installed! It's basically useless, and sit on my hard drive using 5GB of space, but since the last fix I did (With applying the Update Rollup 2), it does not "commit suicide". Anyways, even with working drivers, I would not have benefits of running Windows 2000, native or virtual (Except if you want to save space, comparing it to a Windows XP installation). I've got all my Windows games running on Linux ( ). Well, I've tried!
  3. Found something interesting. I've burned on a CD-RW another customized Windows 2K installation, this time containing the Update Rollup 1, a USB driver by Microsoft (Which won't work, by a normal installation, after the setup), and the official Lenovo video driver for Windows XP, unsupported on 2000. By installing the INF file (Running the video driver setup cause an error), the driver does appear listed in "Graphic card" in the Device Manager, but it's listed as non-working. I was wondering if slipstreaming the driver on the CD would make it work, but no. However, slipstreaming the Update Rollup 1 was a good choice - I've found out that with the Update Rollup 1 slipstrem, I do not get any "usbhub20.sys" error during setup, and no BSOD at all at system startup. That would confirm I'm pretty much done with random BSOD on Windows 2000 startup! My CD-ROM is still detected as usual, but USB won't work. Well, that's good to know - no more error at the setup. Taking a new image of Windows 2K installed, with the Update Rollup 1 installed, in case I need it.
  4. Maybe I'm crazy, but I have this feeling I get BSOD less often, now that Update Rollup 1 is installed. I would appreciate to obtain all the remaining updates for Windows 2K after SP4, but I can't find them (Even tougher, I need them in French, or they won't even install, wrong language..).
  5. Hey! CD-ROM is now detected! :O The only thing I did was to install Update Rollup 1 - altought I do have the SP4 preinstalled, haven't installed the Update Rollup. The installation was necessary to test a "Windows 2000 apparently compatible" Intel HD Family driver, which is similar to my graphic card - the driver won't start. I rebooted, and WOW, CD-ROM is detected! :O That's a really good thing, since I plan on using 2000 to play games (Nothing newer than 2004 or so, everything work), without having to keep a bigger Windows XP installation - it's also a personnal challenge, as I already told you. You imagine playing games.. without CD-ROM? No thanks, I do not plan on filling my hard drive with ISO files! Great, USB still won't work (Not essential. Just would be extremely useful for copying drivers), but that's another important issue solved. The SCSI CD-ROM problem was kind of scary, never thought I would be able to fix this problem.
  6. Tested different drivers.. Still getting random crashes. When I'm trying to reinstall the O.S., I can't really get past the second BlueScreen, told in my previous post, for some reason. Guess I was a bit lucky - I have an image which I keep restoring. Just too bad the image wasn't saved at the very first moment after the installation. It manage to get corrupt somehow, if I don't turn off faulty USB drivers. Well, I'll continue to look. I'll probably won't reply much, but I'll let you know if I manage to make something work - maybe that'll take 2 weeks, or 4 months!
  7. Man, I was too late. I was about to advice you to boot in IDE/Compatibility mode in the BIOS, I also did that when I installed my Windows XP (Tried both x86 and x64 versions). Assuming Dell provide SATA drivers for Windows, you probably can install these after XP installation (So you don't have to set your BIOS to IDE mode everytime you start XP - and SATA mode everytime you start 7), but in my case, I've had to install the SATA driver right after the XP installation - right after. Don't install any other driver, install the SATA driver first. Well, of course, that really depend on how the driver is build, I can't really tell. Another easier option would be to slipstrem your SATA driver on a CD-RW of Windows XP setup (Use nLite software, super easy), so that your SATA drive is automatically detected at the beggining of the installation. Glad to see it's working!
  8. That is well said; after all, I did made a small progress! I was not even expecting the system to install, I was sure that was impossible.. Anyway, first question is resolved, the system is installable. Now, is it usable for a typical usage (No Solitaire. ) ? 16 colors suck ! XD Here's a screenshot of 2000 running: https://www.dropbox....16 23.34.01.jpg Yup, I might get unlucky or not. My best bet probably are the generic/universal drivers availible, I have to find some. A friend of mine will leave me a CD full of drivers, we'll see how it goes. Probably. The goal is to get the minimum, being video display, sound and CD-ROM (Playing games without CD-ROM? Of course, there's VirtualClone Drive, but what a waste of disk space!). USB would be a life-saver, too (Rebooting on XP to copy the drivers, switch from Compatibility to SATA mode, test driver one by one drive me nuts! XD). Internet access for instance, is not required. Yes, it's a SATA. I was expecting the CD-ROM to be detected, since the detecting probably was fine after the first part of the setup. The CD-ROM was detected, and listed as G: in the graphical installation. When I've tried to install Windows 98 on my P4, it was in february. I gave up for a while, getting too many BSOD, then on july, finally managed to get the OS to work - was only because the RAM was over 512 MB... The glitches were only because of that. Maybe the same thing will happen with 2000. Couldn't get it to work now, but will 6 months later? Maybe not...!
  9. Ok! I took the full image, only Windows 7 took about 7 hours to take. XD That's all backed up! So I finally installed 2000 on the blank NTFS primary partition. The first part of the setup completed without any problem. I was really surprised when I saw that the installer haven't crashed while arriving at the graphical setup! :O I've got only one error message during the setup - I've noted it somewhere, it was about usbhub.sys. Some kind of driver issue, most probably. Luckilly, the error wasn't fatal and haven't prevented the installation from working. The setup completed succesfully. I later realise that Windows 2000 didn't even deleted GRUB, cool - easy to restore, but less fun to reconfigure all the entries.. Then I start 2000. Waow, the bootscreen! Then boom, blue screen. I was wondering is the BSOD wasn't caused by the "usbhub.sys" error shown. So I went to the "D:\WINDOWS\system32\drivers" folder on my Windows XP installation, copied the file "usbhub.sys", and replaced the original file on Windows 2000 partition. Never expected that, but that was enough, Windows 2000 is now booting! :O Well, I've counted and strangely, it takes 3 minutes and a half to reach the Desktop.. The boot screen load extremely fast (Never saw anything that fast, even in a VM), but as soon as the GUI appear (640x480 16 colors, of course..), reaching the Dekstop take 3 minutes and a half.. What work? Disk access. I can access all my Windows partitions without any problem, since the 128GB limit is fixed. What doesn't? The USB drives and CD-ROM drive aren't even detected, not a good sign. In device manager, USB is listed as non-working, and CD-ROM is absent. I should also mention that the system is very fragile. It seems that Windows 2K realize that I've modified the file "usbhub.sys", and he actually restore the file to his original state, causing a BlueScrren again. I have to restore the file many times. Also, when I try to install drivers, the system is very likely to fail to boot at next reboot. I've took a working image of Windows 2K after installation, so that's OK, but annoying a little. The common BlueScreen display error 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL. Seems related to the file "uniata.sys". According to the name, I strongly believe it is the generic SATA driver I've install. But generally, I can fix the problem by replacing the "usbhub.sys" file, or booting in safe mode (Does not always work). I've tested the official Lenovo drivers for Windows XP. Most of these won't even start - some do, and they install proprely, but no apparent change to the O.S. I should probably install more critical drivers first, but I can't find them. Most importantly, I should find a generic/universal video driver for Windows 2K.. Any idea where I could get a working one? Thanks!
  10. Great! My disk is now listed as a 300GB, and all the partitions (Except Linux - these are listed as "Unknows", normal) are detected proprely, with the correct names! The workaround is to download this file: http://www.msfn.org/board/topic/75713-48-bit-lba-on-win2k-setup/ And replace the original file on the CD-ROM, in the i386 folder. That did the trick! Windows 2000 support bigger disks if SP3 or SP4 is installed - a registry key should later be added. Of course, it was necessary for me to find the patch, since I needed all my partitions to be detected at the setup. Doing a full backup soon! I'll let you know how it goes.
  11. Sadly, my laptop won't support a second hard drive; I already have a working Windows 2000 VM - especially about the older OS, I'm really curious, and installing 2000 on the main hard drive is a personnal challenge. Just wondering if the OS could work with a really installation, that's a challenge. I was referring to the drivers provided by Lenovo, on my laptop: acutally, Lenovo provide drivers for Windows XP x86 on my laptop, and they work perfectly. But about the XP x64 drivers provided by Lenovo, that's not the same thing - they provide a video and a graphic driver for Windows XP x64, and the official drivers wouldn't even install (On XP x64, of course). I've had to install a random Intel driver, to get it to work. So perhaps I'll manage to find a working driver for 2000 - I'll look for 2000 compatible drivers, on older Lenovo Thinkpad computer (Assuming the XP drivers for my laptop won't work under 2000). Sure, I'm going to take a complete backup/copy of my entire disk, before installing anything! The only thing I've did now was to create a blank primary NTFS partition for 2000 - Pretty much at the beggining of the disk I've got a 1.5GB boot partition for Windows 7, then I've created a 2GB partition for 2000 next. The next partition is my 200GB Windows 7 primary partition. I was hoping 2000 would recognize the second 2GB NTFS partition, but it's still listed as "Unformatted or damaged", even if the partition isn't located over the 128GB barrrier - what I mean is that the first partition on the disk (The 1.5 boot partition for Windows 7, called "SYSTEM_DRV") is detected, and isn't listed as damaged or whatsover. I find it odd that the second partition, created for 2000, is listed as damaged, it's only 2GB. Well, I'll continue to check for the 128GB barrier patch - I know I must add a registry key later, but I've got to find the way to make it work on the setup. Pretty sure that's possible.
  12. Sorrry, I can't edit my previous post, apparently. So, Windows 2K detect my hard disk - I took a while, I was sure the OS simply wasn't capable of detecting it. The only "issue" is that although the partitions are listed, this isn't perfect; the primary boot partition used by Windows 7 being "SYSTEM_DRV" is detected (It's NTFS). As for my 200 GB Windows 7 partition, it is listed as "damaged" and has no label. I guess that's because Windows 2K got natively a limit of hard disk space. I know there's a workaround to fix it, assuming the SP4 (Included on the CD) doesn't fix it already. Anyways, I'm going to install it on a 1.5 GB partition, first. As for the extended and logical partitions (Windows XP in NTFS and Linux Ubuntu in EXT2), there are listed as "Unpartitionned space". Well, I'm not too sure about XP, although. For sure, the Linux partitions are listed as free space (Windows XP setup would list test as "Unknow" instead). As for the Lenovo Recovery partition (Came with my laptop, it's NTFS), it does not display a label, but it is somewhat detected as a recovery partition. Sure thing, I'll be doing a backup first!! That look like a good start, but in that case, I've got to be as much careful as possible.
  13. Thanks; I know about VM, these are seriously awesome for testing multiple OS. Hey, good news! I've heard about a software called nLite, which allowed me to customize my Windows 2K setup, and directly add the SATA driver to the CD-ROM. So I've tried packing the official Lenovo SATA Driver (Only on Windows XP. Officially "unsupported" on Windows 2000), and tested. Already tried the process on a VM with a virtual floppy, got the error "Corrupted file". Same thing go for the driver packed to the CD-ROM. Then I've heard about a generic "universal" SATA/AHCI driver for Windows 2K here: http://alter.org.ua/soft/win/uni_ata/ I've downloaded the driver, then packed it on the CD (a bootable CD-RW). I've setted the BIOS in AHCI mode, knowing that Windows 2K would recognize and "try" to load the AHCI driver automaticly. I then got... the same "INNACESSIBLE_BOOT_DEVICE" blue screen. Then I've tried one last thing, setting my BIOS mode to "Compatibility". As I stated earlier, setting the BIOS mode to "Compatibility" without adding any driver on the CD cause the same BSOD. So I started the 2000 CD-ROM again. 2000 loaded the driver, black screen with blinking cursor. (Oh, for sure, that's going to crash. Sure thing.) Man, the installation is starting! :O I've reached the first installation screen, with the "Install", "Repair", and "Quit" options! NEVER expected that! Well, that's a really good start! :O I'll try the installation in a small partition a soon as possible (Guess I should backup an OS somewhere, in case 2000 destroy Windows 7... Usually, I trust Windows 2000, but on such a modern machine..) . I'll let you know about how it goes. I've only noticed a Blue Screen when exiting the setup, after the screen "Your computer will reboot in 15 seconds.". The error is DRIVER_POWER_STATE_FAILURE. I've read about the error here: http://www.geekstogo...-state-failure/ For now, that's not much of an issue. At least, I can start the installation! If the installation is succesful, I'll try the drivers for Windows XP. And if these don't work, guess I'll check for others drivers on differents /olders Lenovo Thinkpad laptops that got official 2000 drivers. Who know, the official sound driver for Windows XP x64 provided by Lenovo isn't even installing (...). I've tried a random Intel Sound driver and.. that worked! Maybe I'll be lucky (Maybe not). Windows 2K... You're a quite old, but intelligent OS, but please don't do anything stupid (So far, you never did). (I am aware this will break my Windows XP / 7 and GRUB bootloaders. Already know how to restore them all, I've done it a bunch of times.)
  14. Thanks for your support! I'm looking for a way to boot the OS from the bootloader, not starting another OS to start 2000 later on. I don't know if that's possible, and that's what make me curious (Yeah, that's odd). The laptop was released in march 2011, so it came with Windows 7. Oddly enough, there's only one driver that is officially supported on Windows 2K, and that's hotkey display. I'll be trying the drivers for Windows XP and check if these install properly, who know. What do you mean, exactly? Sorry, I'm French. Thanks again!
  15. I'm running Ubuntu 64-Bit. Right now, the VM is extremely fluid, even in Unity mode (With the Desktop hidden). It's excellent. I have a screenlet (Widget equivalent) on my desktop, which show me the ammount of RAM used (Never goes about 20%) as well as SWAP - I can always see if the system is running out of ressources, that way. If the SWAP percentage keeps growing.. then I know I must shut the VM as soon as possible. (Never happened on VMware, yet)