Jump to content

ilko_t

Patron
  • Posts

    1,720
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by ilko_t

  1. OK, thanks a lot for the tests and the patience. There must be something unusual with this stick, wild guess is that Setup marks it as "needing reboot" in order to be functional, when installing drivers for it or for the USB bus it's on, or installation of some other USB devices are affecting it. I've pointed you to a similar case, sorry I have no further explanation for now, nor a workaround/fix, apart from replugging the device as you figured out. As for the USB boot- there is a major difference between 0.x.x and 1.x versions- former versions and method needed second boot from USB for the second part, latter do not- second boot for the GUI mode could be from the internal disk, as boot,ini is properly generated during the first part. To make it clear- with 1.0 beta8 you most likely were not booting from USB for the second part, you just haven't noticed that because there is no error if you don't. Program, or what's on the USB stick has no such control over BIOS, if F8 boot menu starts USB, whether stick was prepared with 0.2.3 or 1.0 betaX should not matter, it should boot or not the same way in both cases. Unless this particular BIOS reads what's on the USB device (maybe check for a known MBR/start sector or MBR/start sector start bytes?) and decides to ignore the USB boot, but that would be very unlikely in my opinion. Another point- WinSetupFromUSB prepares the USB stick in a friendly for Setup manner,since it's not USB install aware at all, using number of tricks and cheats and that's it, the rest is in full control of Setup. If Setup does not like that USB key for some reason, it's must be issue with the combination XP Setup, USB drivers, BIOS etc. etc. and this particular USB stick. There could be a workaround or fix for this combination, and that would be yet another trick or cheat, for this particular case.
  2. Which boot.ini do you edit? On the internal hard disk, or on the USB stick? The latter should already have all those entries, just below the line "Try entries below if getting HAL.DLL/NTOSKRNL.EXE not found errors". Are you actually booting from USB for the second part? Do you select Second part of Setup from grub4dos boot menu?
  3. You would also need to make sure you boot from USB for the second part, the GUI mode, NOT from the internal disk.
  4. Did you start the First part of Setup? Did it go through? Did you see grub4does menu entries- First and Second part of Setup, on cyan/light green background? This error message may appear if the Second part is launched and boot.ini entries are not proper ones. Details are here, Q4/A4: In addition, as reminder- always disconnect unnecessary mass storage devices such as card readers when installing from USB, no matter what Windows version and what program prepared the USB disk, as they may affect and often do, where Setup places boot files and where exactly the Windows installation is.
  5. For some reason Setup disconnects that drive, probably marking it as restart needing, wild guess. Similar issue, combination of a particular USB stick, Server 2008 and Dell Latitude E6400: http://reboot.pro/9076/page__st__50#entry123824 As a last request- can you try vers. 0.2.3 and the Verbatim USB stick?
  6. Do you have a chance to test with another, preferably USB 2.0 stick? Such issue haven't been reported yet, it's quite interesting.
  7. You may look at Windows Setup log files and seek for clues around that time: http://www.windowsitpro.com/article/installation2/what-log-files-does-windows-xp-create-during-installation- Does this happen with unmodified/vanilla XP source, on this motherboard and using the same USB stick?
  8. Simply no way, there is no such option, nor there could be such. The only software could damage an USB disk in such way, if it is damaged indeed, is software, which works on firmware level, i.e. software from USB disk or memory controller manufacturer. None if the programs included in WinSetupFromUSB, nor it has such "powers".USB sticks has limited number of write cycles, good ones have way more, bad ones have less, or much less. 3 cheap Samsung USB sticks died on me in less than a week, 3 good one- made by Buffalo, Lexar and Transcent, purchased the same time, 5-6 or more years ago, heavily used and abused, are still in perfect shape... But again, first test it on another PC.
  9. Have you tried it on another computer?
  10. You might search this topic for 'DPMS' Hints- first post in topic, about the issue with iastor and DPMS: http://www.msfn.org/board/index.php?showtopic=120444&view=findpost&p=1002473
  11. That means those ISOs are not grub4dos compatible, in terms of ability to boot from an emulated CD (by grub4dos) and finish booting without need of extra steps. To rephrase- one cannot boot ANY ISO this way. You may want to try Sardu, which supports many types of AV rescue disks, or create manually menu.lst entries for each ISO you want to boot, many examples could be found here: http://www.rmprepusb.com/ http://reboot.pro/5041/ http://reboot.pro/forum/66/
  12. 1) Integrate in your source the appropriate mass storage (SATA/AHCI) driver, apparently Intel one, using nLite for example, then recreate the USB disk. 2) Integrate in your source BTS mass storage driver pack and recreate the USB disk: http://driverpacks.net/docs/beginners-guide-windows-xp Make sure "DriverPack Mass Storage text mode" is checked. 3) In BIOS switch SATA/AHCI mode to IDE/compatible if there is such option.
  13. As for multiple sources- latest beta8 for example- up to 99 XP/2000/2003 sources. One PE1 (XP/2003) based. Unlimited PE2/3 if added as "grub4dos compatible ISO" and the PE supports booting that way, or one if added as extracted ISO, the option for Vista/7/8 setup. For multiple PE1- you better use ISO + firadisk/winvblock virtual floppy loaded by grub4dos, I think you
  14. Pleas try this version. WinSetup_test2.zip
  15. Ok, thanks for the logs and the report. Give me some time and will post another version.
  16. Can you try the version attached? Just copy the two files in D:\WeissJT\Downloads\Programs\Win Setup_1_0_beta8\ and launch either of them. You may also rename D:\ISOS\Linux+Windows\ to D:\ISOS\Linux_Windows\ just in case.
  17. Windows 7 entry is for your Windows 7 install, previous Windows versions is self explanatory as well. You were seeing boot menu because you had 2 entries. Deleting only "earlier Windows versions" from those 2 entries would have been more than enough. Anyway, hopefully you learned something new.
  18. Did you delete Windows 7 entry as well?
  19. Please don't shoot the mosquito with a nuclear weapon. Install EasyBCD or any of the other tools mentioned. Edit the BCD settings and get it done properly, quick, and in a way you learned something new.
  20. Windows 7 Setup detected a previous Windows OS present and added it to the boot menu, nothing wrong in that. Do you still have the XP? If not- press start button, type "msconfig", go to BOOT tab, delete the "previous operating systems" entry and/or reduce timeout to 0 or 1. May also use EasyBCD, or BootIce for this task.
  21. Can you take a picture of this Windows Boot Manager and post it here?
  22. There is a bug in beta7, either fix it as described, or redo the USB disk using beta8. F6 drivers you can obtain from motherboard/laptop manufacturer. Keep in mind there are some limitations in this method- only the default driver referenced in txtsetup.oem could be used if it supports multiple drivers. Amend txtsetup.oem accordingly.As for ntdetect.com: http://www.msfn.org/board/index.php?showtopic=112630&st=0&p=738009entry738009 Q3/A3 Do you need it? Do you get BSOD 0x0000007B when starting setup?
  23. If you don't touch the other partitions everything should be fine, just make sure which partition is which, as drive letters do not describe which is which and Windows 7 for example may and will name them differently. Open disk management, look at partition order and size, make notes and use their size and place to distinguish them.
  24. How did you prepare the USB disk? Which boot loader are you using? Did you use winnt.exe in DOS to prepare ~BT and ~LS folders on the internal disk? Did you try simply to boot from the internal disk for the second part, the GUI mode? What was the result?
  25. Triple check your BIOS setting, try also the hotkey (F11, F12, etc. ) for boot menu.
×
×
  • Create New...