Jump to content

Xiaopang

Member
  • Posts

    8
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

About Xiaopang

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

961 profile views

Xiaopang's Achievements

0

Reputation

  1. Alright, I got it working The reason for why my x86 and x64 versions of XP didn't work with WinSetupFromUSB was probably because they contained slipstreamed service packs via an old nlite-version from 8 years ago. I gave it a shot with original, unmodified XP x86 and x64 versions and both worked instantly. I then used the latest version of nlite to slim down XP x64 and was able to install that with WinSetupFromUSB without any problems as well. Looks like nlite's removal process improved a lot since 2009. I also used the chance and slipstreamed proper AHCI-drivers into the setup and the installation went through without any problems in AHCI mode. Yeah, I figured as much. Still, it's strange that you can easily start the installation via a simple boot sector on a CD, but not on a hard drive. You'd think that after so many years someone would have developed a simple loader that would allow for that. Back in the day I created many BCDW-powered multi-OS installation DVDs to always have all my necessary admin and maintenance tools ready on one disc. The XP x64-versions I tried, also came from such a disc. With tools like WinSetupFromUSB it's unfortunately absolutely impossible to boot such multi-discs from a USB drive and I'm just absolutely amazed that booting the iso directly via grub is the only way to make use of these discs if no optical drive is available any more. This error was courtesy of an nlite version from 2009. The hal.dll error occurred with the x86 version, but the x64 one errored out completely differently. Somethig about a failed NTOSKERNEL if I recall correctly. At that point my frustration was too big to properly document the error, especially since I wanted to see first if the original XP versions would throw the same errors. The difference of errors between both versions was a good indicator that this wouldn't be the case which proved eventually correct. Anyway, thank you to all of those who helped, especially you, Jaclaz. I learned a lot today
  2. True. Though I never asked for help with those tools in the first place, so this shouldn't be a problem. Also, as a copyright lawyer I don't consider them "warez" per se since they aren't an illegal carbon copy of an existing product, but they are their own products that commit certain copyrights violations. Just for the sake of pickiness Thanks for the heads up. I love reading stuff like that I absolutely agree. I don't have a Sata Raid. Anyway, I made some progress. I integrated FiraDisk into the x86 and x64 setups et voilà I had access to my hard drives The FiraDisk developer explained the problem I experienced over at Reboot Pro: XP needs a special driver if the iso is being run off a RAM-Drive which is exactly why I integrating AHCI drivers and switching to IDE didn't work. Anyway, after I integrated the driver, Windows setup would finally proceed and allow me to install the setup files to the hard drive, but that only introduced new problems. The DOS-based part of the setup finished properly, but after the necessary reboot, the GUI-part of the setup couldn't be started due to missing hal.dll, though that couldn't have been the case... I then switched to giving WindSetupFromUSB a shot. The x64 installation errored out with NTDETECT failed. The x86 one worked better, but didn't find a ton of files during the GUI-setup, but since I'm after installing the x64-version anyway, I gave up guessing paths after a few files. I'm stumped that it's so hard to install XP off a hard drive or a stick... I think I'm gonna give Rufus a shot now. Is there any other software that doesn't try to intelligently analyze the OS to build its own setup onto the USB drive, but just enables me to boot the content of the iso by directly booting the CD boot sector off the drive? There must be some. The NT boot manager seems to be able to do just that...may be I'll have to meddle with it if nothing helps : /
  3. My SSD and a 300GB Samsung (HD321KJ) are not AF and SATA II. How this is relevant to the problem is beyond me though, since the problem is apparently that Windows can't even access the storage controller correctly. The KB-article only applies to Vista, not XP and also only to an already installed OS, not raw installation files. Yes. May be I should explain my setup a bit. The SSD is my system drive with a regular BCD, so I added the XP iso to the boot menu via EasyBCD which works. I then try to install XP to the above mentioned 300GB Samsung HDD which consists of two 37GB and 260GB partitions. The first partition (37GB) is empty and XP is supposed to go on there. By now, I reformatted it to 32GB FAT (was 37GB NTFS before), installed Freedos on it, copied the XP x86 setup over and started it. Windows copies some pre-installation files, but gets stuck on a screen where it claims it's copying the Windows files now, however there's no progress bar or copied file names on the bottom. It just seems to sit there doing nothing. I end up with an NT-bootloader that doesn't work ("Disk error" - "Enter proper boot media"), can see the temp installation folders ($WIN_NT$.~BT + LS), but they only consist of 260 files occupying 14MB. It's kind of odd. If there was some form of document that listed which files are being copied in which order to the temp install folders, I could check which one made Windows choke. It's strange though. It almost seems like it was only able to copy those files that fit into the HDD's cache. Is IsotoUSB any good? It seems to work. RMPREPUSB makes me shudder, because it reminds me of wasted hours of not getting anything usable out of it, but I'll give it a shot if nothing else helps. And since you mentioned PE, I also gave Hiren's Boot CD a shot and the Mini XP was able to access the drives just fine. May be I could run the Win-version of the installation from there. Don't worry, I'm extremely persistent. As long as there are methods left, I will try them out Thanks! I already have the hunch that it's my Bios that is screwing things up for me without a way to fix it. Is there any special tool I can use for that, or will the Device Manager suffice? Update: Checking the device manager in Hiren|s MiniXP I can see that all disks are being identified as SCSI drives which they aren't. However, that might be tight to the fact that the OS uses FiraDisk Virtual Disk Enumerator instead of dealing with the real hardware. May be I can find a way to integrate this virtual controller into the installation... That's a good idea! That'll be the last option I try, because I have zero experience with installing anything as old as a PE3 to a hard drive xD
  4. Thank you for the suggestions. CSM was already activated, but I hadn't chosen "Other OS". Though, that didn't change anything. I also removed all other drives to no effect. The mainboard manual merely stated that the board is compatible with XP and recommended to use SATA port 5 or 6 for the optical drive to run the installation from. I hooked up the HDD to Port 1 and 5 to no avail. I even reseted the mainboard back to default settings, just in case an instability from OCing might interfere, but no change. By now, the only thing left that I can see as a culprit could be the fact that I boot the iso via EasyBCDs iso-boot function due to lack of an optical drive. Though I can't make out a reason how this setup could interfere with the installation's access to the storage devices. I guess I'll transfer the iso to a USB-drive and try the installation from there. That's the only thing that comes to mind that I haven't tried yet. Edit: Another way to cut out USB entirely would be to run the setup directly from the HDD I want to install XP to. Is there a way to trigger the XP setup by loading the boot sector of the iso directly from the HDD? I doubt it would be possible to start the setup directly via BCD from the boot menu, at least not for XP x64 due to the missing winnt.exe.
  5. I want to install XP x64, but I'm running into the 0x0000007b error during installation that indicates XP's inability to deal with the AHCI mode. I switched my SATA drives to IDE in the bios of my Asus M597 R2.0 mainboard, but the same error occurs. I slipstreamed the XP-compatible SATA AHCI-drivers from the Asus website, but the setup still throws the same error. I tried a 32bit version of XP, same problem. I used VMWare to install XP directly to the hard drive and installed the AHCI drivers manually, but upon booting the from the drive natively, I get the same error. Pressing F6 during setup should show the mass storage drivers that Windows would otherwise use, but it only shows "<none>", regardless of whether I run my drives in IDE, AHCI or whether I slipstream my drivers into the installation or not. Googling the mainboard, it seems that merely switching the drives to IDE should be enough to get through the installation without any problems, but for some reason that doesn't work in my case. I'm at my wit's end. I have a Samsung SSD (840 Evo) and two HDDs in my system (SATA ports 1,3 and 5) and none get recognized by the setup. I even set the Bios to use legacy boot instead of UEFI, just in case. Nothing. Does anyone have any idea what I can do or which settings in Bios I can change to make this work?
  6. I switched to SoftPerfect's RAM Disk which solved my problem with Install_Wim_Tweak not properly removing packages. It's quite a bit slower, but apparently more accurate. I'd still prefer IM due to its painless implementation and higher speed, so any bugfix for Install_Wim_Tweak would be very much welcome.
  7. I experienced a strange bug when storing the wim-file and the mount folder on a RAM-drive created by ImDisk on Windows 10 x64. Install_Wim_Tweak supposedly runs through successfully, removing the specified packages in the process, but in reality no packages are removed and no errors are reported. I didn't experience any issues when all files were located on my SSD. I somehow have the feeling that it's a path issue due to the way IM implements the RAM-drive, but then Install_Wim_Tweak should at least throw some errors. Anyway, thanks for this tool. I found it to be very useful
×
×
  • Create New...