Jump to content

eagle0042

Member
  • Posts

    18
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by eagle0042

  1. As you indicated: hd1 - does not appear

    It doesn't appear in grub4dos, but it appears once you load the ISO into memory, and text setup begins. And I know the drive shown is not the USB drive, as the drive shown at text setup is much bigger than my USB drive.

    Ask the author, if this version fail at given hardware.

    I'll see if I can contact the author and see if there is a problem with this type of laptop.

    ISO file was not mounted.

    Is the ISO loaded after the first reboot? Before the Windows XP loading screen appears? I waited 11 minutes while the USB drive light flashed, but no Windows XP loading screen...

    Open floppy image, edit txtsetup.oem and unomment fixBoot.USB line

    Done. Saw no difference. Where would I be able to see an effect of what I uncommented?

  2. Which PloP version do you use?

    I use 5.0.10, and it works. Version 5.0.11 doesn't load at all. The USB drive light just flashes, and the screen says Starting PloP Boot Manager, and Linux z-image and such, but nothing else.

    Which grub4dos verson do you use?

    0.4.4, dated 03-31-2009.

    Normal, without PloP

    Which devices does exist?

    Possible disks are: fd0 hd0 hd1 rd

    Which goes to internal hard disk and which to USB drive?

    hd0 - USB drive

    hd1 - internal hard drive

    With PloP

    Which devices does exist?

    Possible disks are: fd0 hd0 rd

    Which goes to internal hard disk and which to USB drive?

    hd0 - USB drive

    hd1 - does not appear

    Do you use a winnt.sif file?

    Yes. It appears to be generated by nLite.

    Does winnt.sif file contain a section [MassStorageDrivers] ?

    No.

    Did textmode setup comlete so far?

    Yes.

    How long does reboot takes? Several minutes?

    Depends:

    Turns out, I have an oddball laptop here. Out of 19 laptops, 18 of them are HP Compaq nx6325, while the other one is a HP Compaq 6715. With the USB drive removed, the 6715 boots into GUI setup (after 45 seconds), but displays the error below:

    "The file 'asms' on Windows XP Professional Service Pack 3 CD is needed.

    Type the path where the file is located, and then click OK."

    The path that is already in the box is: "GLOBALROOT\DEVICE\CDROM1\I386". It does the same thing if you choose the internal hard drive as the boot device, with the USB drive plugged in. However, if you leave the USB drive in during the reboot, it flashes constantly, and shows only a blank screen.

    Now, on the other 18 laptops (HP Compaq nx6325), I get nothing. No hard drive activity indicator light, no USB light flashing, just a blank screen, even after 5-7 minutes.

    Thanks for all the help.

  3. Are you using the sample menu.lst as in here:

    No. I am using this one:


    title XP setup from iso
    find --set-root /Inst/XP_RAM.iso
    map (hd0) (hd1)
    map (hd1) (hd0)
    map --mem /Inst/XP_INST.ima (fd1)
    map --mem (md)0x6000+800 (fd0)
    map --mem /Inst/XP_RAM.iso (0xff)
    map --hook
    dd if=(fd1) of=(fd0) count=1
    chainloader (0xff)

    The text setup loads too slow without Plop, but when I use Plop, i have to comment out the map entries (below) for it to enter text setup. Otherwise, it doesnt, it tells me the selected disk does not exist.

    I comment out these lines (because thats what the error 21 appears to refer to):


    #map (hd0) (hd1)
    #map (hd1) (hd0)

    And the text setup went through without a hitch.

    Here is where things just changed:

    Upon reboot, the laptop boots into the hard drive (the hard drive is before the USB, when I access the USB drive, I just press F9, and select to boot from USB), and I leave the USB plugged in, the USB light flashes, but after 15 minutes, nothing happens, it just sits at a blank screen. If I pull the USB out after the text setup completes,and before the computer reboots, and wait long enough, the computer boots into GUI setup. But, it says it cant find a file, has an option to type in where it is, but it wont continue. So then I tried the menu.lst option that you gave me. Same thing as if I would have left the USB drive in. I suppose the lines I commented out had some kind of affect on the install, but if I dont comment them out, it doesnt boot into text mode quickly.

    Sorry if I'm being dense or difficult. :ph34r:

  4. When I use the menu.lst that you gave me, using the RAMDISK method with the ISO that I made (renamed to XP_RAM.iso), I get the following results:

    • Tried booting into text setup without plop - too slow
    • Tried booting into text setup with plop - Error 21: Selected disk does not exist

    EDIT: I did notice that my ISO and IMA arent in the "inst" folder like in the example. Trying that now.

    EDIT 2: Same error. What can I do?

  5. Then something else must have changed. Booting process hasn't reached grub4dos which loads menu.lst so changes in the latter cannot lead to what you describe.

    Ah. I misunderstood you then. :blushing: It booted into grub4dos, but when I selected to boot to continue the setup, I got nothing more than a blank screen. Thats where the blank screen came from.

  6. Then you'll have to edit:

    The name \Inst\XP_RAM.ISO is the internal default.

    The name can be configured:

    The floppy image contains a file \setup\ISOimage.ini. Edit this file.

    Would it not be easier just to rename the iso to the internal default, and change the menu.lst to reflect the default as well?

    And if I already completed the text portion of the setup, would I need to re-install to reflect the name changes?

    Did you get grub4dos menu?

    Nope. Nothing.

  7. And you have to amend the appropriate files for the new file name and location of xpsp3.iso.

    My xp installation iso is named xpsp3.iso, and its in the root of the drive.

    I tried the menu.lst you posted, and did not get anything more than a black screen, and the USB drive light flashed constantly.

  8. Sorry it took me so long to get back, Thanksgiving and holiday stuff...

    What grub4dos menu entry did you use to start the GUI mode? What about the Text mode entry? Can you post your entire menu.lst, there must be something wrong or omitted in it.

    For the GUI mode you even don't have to start from USB if properly used cdob's method, ISO loading by grub4dos is also not necessary, it's loaded later on by imdisk driver, when windows USB 2.0 drivers are loaded and should not take that long at all.

    Here is the menu.lst I was using:


    color black/cyan yellow/cyan
    timeout 10
    default /default

    title Start PLoP boot manager
    find --set-root --ignore-cd /plpbt.bin
    kernel /plpbt.bin

    title XP setup from iso
    find --set-root /xpsp3.iso
    #map (hd0) (hd1)
    #map (hd1) (hd0)
    map --mem /XP_INST.ima (fd1)
    map --mem (md)0x6000+800 (fd0)
    map --mem /xpsp3.iso (0xff)
    map --hook
    dd if=(fd1) of=(fd0) count=1
    chainloader (0xff)


    title Continue XP setup
    find --set-root /xpsp3.iso
    map (hd0) (hd1)
    map (hd1) (hd0)
    map --mem /xpsp3.iso (0xff)
    map --hook
    chainloader (hd0)+1


  9. For the record- what's this machine, laptop model or motherboard of desktop?

    I'd try also firadisk method and eventually PLoP for faster loading.

    It's a HP nx6325 laptop.

    I just tried the firadisk method with PloP, because otherwise, it was too slow, and I had much success in the text mode portion of the setup. However, after the

    first reboot, I loaded PloP, and then I chose to "Continue XP Setup", and the screen showed:

    map (hd1), (hd0)

    The selected drive does not exist.

    Press any key..etc etc...

    So, I deleted the two map entries, using the grub4dos editor and it gave me a hal.dll error.

    My guess would be that the loader is checking the USB drive, and not finding hal.dll because I removed those map commands.

    So, I tried a straight "Continue XP Setup" (without PloP), and it takes forever to load the ISO into memory, and then it shows nothing but a black screen, and the

    USB drive light flashes constantly.

    Is it possible to map the drives, boot into PloP, and then choose setup like normal, with the map commands under that entry removed? Is this completely incorrect? :blink: Or is there an easier solution? :)

  10. Try the attached plpbt.bin, no need to press ctrl+a, it will auto start.

    0x6B reminds me of removed manual install and upgrade option in nLite which must not be used, at least not with 0.X.X versions of WinSetupFromUSB and USB_multiboot. Check pinned FAQs topic.

    The plpbt.bin that you attached will not load. When selected from grub4dos, it loads nothing.

    Screen says at the top:

    Booting Start PLoP boot manager

    (hd0,0)

    [Linux-zImage, setup=0x800, size=0x9f9e]

    and the USB drive light flashes constantly.

    The manual install and upgrade option is not checked, as I had seen that on the forums before I created my my nLite installation.

  11. In addition- try various PLoP versions. On my machines 5.0.10 works on one of them where 5.0.11 fails and vice versa.

    Added:

    title Start PLoP boot manager
    find --set-root --ignore-cd /plpbt.bin
    kernel /plpbt.bin

    Extract plpbt.bin to USB drive root from PLoP zip archive:

    http://www.plop.at/en/bootmanagerdl.html

    Thanks for the tip on multiple versions, as the 5.0.10 works, but it only goes about 2 steps further. At the bottom, the text mode now shows "Setup is starting Windows", where

    it waits a long time, before showing BSOD PROCESS1_INITIALIZATION_FAILED, with a STOP of 0x0000006B.

    I'll see about trying a stock SP3, maybe it has something to do with my nLite version....

    Update: Doesn't work with stock SP3 either.

  12. Hm. No, I was using 1.0beta6...I must have missed the big red letters that say *STABLE*...lol...I'll try using 0.2.3, and see if I yield any results.

    I read somewhere that the text mode setup goes into a "protected mode" right before asking for which partition to install from. Is this true? and is it related to the cause of the BSOD?

    I've tried USB_MultiBoot. but it always told me that the drive wasn't formatted correctly, even when I let PEtoUSB or the HP tool format the drive for me.

    Sticky solutions? Can you point me in the right direction?

    UPDATE: I just tried the 0.2.3 version, and I couldn't even get into the text portion of the setup. Without Plop, the USB drive either loads ridiculously slow, or not at all. The light on the USB drive flashes constantly, but nothing happens, and I let it sit for 10-15 minutes.

  13. In the small ISO file and in the \WINSETUP\XP...\I386 folder.

    @ilko_t

    Im not sure I replaced both. I'll try that.

    EDIT #1 : Alright, I just double checked the NTDETECT in the small ISO, and in the "\WINSETUP\...\I386" folder, and both match the modified hex code and file size.

    Hi... you can find some help from this link...

    http://support.microsoft.com/kb/137064

    @pankaj

    Thanks, but I've already tried that:

    ...However, after I pressed a key, the setup throws a BSOD, with STOP 0000007B error.

    I made sure that the MBR was not locked (it wasn't)....

    EDIT #2: I've tried several things since my last post. I integrated the mass storage drivers pack into the installation.

    I disabled the card reader, with no luck. I tried forcing USB 1.1 with PLOP, but only mode 2 even

    finds the USB drive. When using Mode 2, the install no longer shows a BSOD, but comes to a screen that says:

    "Setup has encountered an error and cannot continue.

    Contact technical support for assistance. The following

    status codes will assist them in diagnosing the problem:

    (0x4, 0x1, 0, 0)

    Setup cannot continue. Shut down or restart your computer."

    Also when using Mode 2, the light on the USB drive goes off for a few seconds before the screen above appears, then

    right before the screen appears, the light comes back on. The light does not go off when using standard Plop (not forcing USB1.1), but

    the setup throws a BSOD.

    Just thought I would add this infomation, in case it helps.

    My next thing to try is to test a stock SP3 on the USB, using a modified NTDETECT, but I suspect it will blue screen as well....

  14. Hello! :hello:

    I am trying to install XP SP3 via USB. I have an nLited installation (for some unattended-ness, and I added drivers, but the SP3 was built into the CD itself.)

    I am trying to install XP to (several, 19 of them to be exact!) HP nx6325 laptops. I figured that a USB installation would go much quicker. I was able to

    create a bootable USB drive, by using WinSetupFromUSB. Currently, the drive is formatted as NTFS, but I have tried using FAT32 previously, to no

    avail. The computer successfully detects the USB drive as a hard drive, and boots into grub4DOS. At first, I selected the entry for the installation, then

    on the second screen, I picked the first entry (for the text mode setup).

    However, the computer seems to freeze at "Setup is determining your hardware configuration..." (I waited for 15 minutes, and it didnt move), and the

    light on the USB drive flashes constantly. So, I then decided to try the Plop boot manager. Plop successfully gets into the setup, and very quickly

    zips thru the "Setup is determining...", as well as where all the setup files are loaded. However, right before the installation would normally begin to

    ask questions, the setup shows the message:

    "An unexpected error (769) has occurred at

    line 5182 in D:\xpsp\base\boot\setup\setup.c

    Press any key to continue"

    With a Google search, I found several things other people have tried. Some have mentioned that the message above was only a indicator that the BIOS

    supported USB booting normally. However, after I pressed a key, the setup throws a BSOD, with STOP 0000007B error.

    I made sure that the MBR was not locked (it wasn't). And I also decided to try the standard CD-ROM method (which got me past the point that the USB

    drive did). I also moved a standard XP installation to the USB drive, only for it to fail at the same point.

    So, my question is, has anyone else had this problem? and how did they fix it? :blink:

    Thanks

×
×
  • Create New...