danafik

Member
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About danafik

Profile Information

  • OS
    none specified
  1. @laddanator, well, now it's working though to make it work TXTSETUP.OEM file's "[Defaults]" stanza needs to be modified to include default single driver name, it allows to proceed without pressing F6, as windows setup automatically copies default driver. As for f6.img and floppy.img, they are the same. I just renamed the file.
  2. @ilko_t, thank you for pointing me to the right direction. And thank you for your great program, WinSetupFromUSB. So, I succeeded in installing AHCI driver (single) from virtual floppy during Windows XP Pro SP3 installation. Both approaches to mapping virtual floppy work equally well (see below), as I performed two complete/full windows XP installations for testing purposes on this machine. For start, I downloaded stock/original Intel AHCI drivers from Intel's website http://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=2101&DwnldID=20625〈=eng&iid=dc_rss Modified TXTSETUP.OEM as following: [Defaults] scsi = iaAHCI_9RDODH And copied TXTSETUP.OEM with other 5 files (iaahci.cat, iaahci.inf, iastor.cat, iastor.inf, iastor.sys) to empty floppy image file. And then proceeded to installation. Note, that I didn't press F6 during setup. This works (contents of /bootws/2.lst file): map (hd0) (hd1) map (hd1) (hd0) map --mem /f6.img (fd1) map --mem (md)0x6000+800 (fd0) map --hook dd if=(fd1) of=(fd0) count=1 ls (0xff)/ && root (0xff) ls (0xff)/ && chainloader (0xff)/I386/SETUPLDR.BIN ls (0xff)/ || rootnoverify (hd0) ls (0xff)/ || chainloader (hd0)+1 boot This works too (contents of /bootws/2.lst file): map (hd0) (hd1) map (hd1) (hd0) map --mem /f6.img (fd0) map --mem /f6.img (fd1) map --hook ls (0xff)/ && root (0xff) ls (0xff)/ && chainloader (0xff)/I386/SETUPLDR.BIN ls (0xff)/ || rootnoverify (hd0) ls (0xff)/ || chainloader (hd0)+1 boot UPDATE: Virtual floppy with default single driver needs to be mapped only during the first part of windows setup (txt mode).
  3. That's exactly what I did, and it's not working. Now reading the stuff ilko_t suggested, will report later.
  4. Hi again. Is it possible to insert Intel AHCI drivers from grub4dos emulated floppy during Windows XP Pro SP3 setup? I don't want to slipstream them using nLite, cause I'd like to keep installation files as generic and unmodified as possible (suitable for wider range of machines). So I created floppy image with mtools: mformat -C -f 1440 -i floppy.img :: mcopy -i floppy.img iaAhci.inf iaAhci.cat iaStor.inf iaStor.cat iaStor.sys TxtSetup.oem :: And then in grub4dos before "/bootws/2.lst" gets executed, I map that floppy image: map --mem /floppy.img (fd0) map --mem /floppy.img (fd1) When windows setup starts, after pressing F6, I'm able to select desired AHCI driver, but when setup completes drive formatting, following message is displayed: Insert the disk labeled: Intel(R) Rapid Storage Technology Driver into drive A: * Press ENTER when ready. Hitting Enter does nothing Am I doing something wrong? Why setup doesn't see floppy anymore?
  5. Glad to help. Without Plop: grub> read 0x8280 Address 0x8280: Value 0x0 grub> calc *0x475 & 0xFF 1 (HEX:0x1) grub> root (fd0,0) Filesystem type is fat, partition type 0x20 grub> root ( Possible disks are: fd0 hd0 rd grub> find /usbdrive.tag (fd0,0) (fd0) With Plop (output with 5.0.11 and with 5.0.13 is exactly the same): grub> read 0x8280 Address 0x8280: Value 0x80 grub> calc *0x475 & 0xFF 2 (HEX:0x2) grub> root (hd0,0) Filesystem type is fat, partition type 0x0C grub> root ( Possible disks are: hd0 hd1 rd grub> find /usbdrive.tag (hd0,0) Yes, the reason for the mysterious/weird behavior after running /BOOTWS/1.st is that "cat --locate=a --replace=b" modifies TXTSETUP.SIF in the iso file permanently. See above. I performed two complete full windows xp installations (one with Plop 5.0.11, other with Plop 5.0.13), both went successfully till the very end (usable windows desktop) without any hiccups. The program installs grub4dos MBR, did you select the advanced option "do not check and install grub4dos MBR"? WinSetupFromUSB installs grub4dos to MBR? I didn't know that. No, I didn't select any advanced options, so this means that grub4dos indeed was installed to MBR. Good to know this. Because earlier (before I knew about WinSetupFromUSB) I was using RMPREPUSB 2.1.630 to make bootable USB flash drive to play with some linux isos, and the only way I was able to make it bootable was to install grub4dos to partition boot sector (PBR), not MBR.
  6. That's very nice machine...What's motherboard model and make? It's a barebone laptop from Uniwill, model 223ii. Intel Pentium-M, 855GME, ICH4-M, ide hdd, ide dvdrw (dead; cannot be disabled via BIOS), no floppy drive. http://www.uniwill.com/products/other/223ii0/223ii0_print.php I use not altered, stock winsetup.lst (except, that I do not use "savedefault"/"default"): color black/cyan yellow/cyan timeout 10 #default /windefault title Back to Main Menu configfile /menu.lst title First part of Windows XP Professional SP3 setup from partition 0 map --unmap=0:0xff map --unhook ls /WINSETUP/XPpSP3.ISO || find --set-root --ignore-cd /WINSETUP/XPpSP3.ISO map /WINSETUP/XPpSP3.ISO (0xff) || map --mem /WINSETUP/XPpSP3.ISO (0xff) #savedefault 2 checkrange 0x00,0x01 read 0x8280 && configfile /BOOTWS/fd.lst checkrange 8 calc *0x475 & 0xFF && configfile /BOOTWS/8.lst checkrange 7 calc *0x475 & 0xFF && configfile /BOOTWS/7.lst checkrange 6 calc *0x475 & 0xFF && configfile /BOOTWS/6.lst checkrange 5 calc *0x475 & 0xFF && configfile /BOOTWS/5.lst checkrange 4 calc *0x475 & 0xFF && configfile /BOOTWS/4.lst checkrange 3 calc *0x475 & 0xFF && configfile /BOOTWS/3.lst checkrange 2 calc *0x475 & 0xFF && configfile /BOOTWS/2.lst checkrange 1 calc *0x475 & 0xFF && configfile /BOOTWS/1.lst boot map --unmap=0:0xff map --unhook title Second part of 2000/XP/2003 setup / Boot first internal hard disk checkrange 8 calc *0x475 & 0xFF && configfile /BOOTWS/8.lst checkrange 7 calc *0x475 & 0xFF && configfile /BOOTWS/7.lst checkrange 6 calc *0x475 & 0xFF && configfile /BOOTWS/6.lst checkrange 5 calc *0x475 & 0xFF && configfile /BOOTWS/5.lst checkrange 4 calc *0x475 & 0xFF && configfile /BOOTWS/4.lst checkrange 3 calc *0x475 & 0xFF && configfile /BOOTWS/3.lst checkrange 2 calc *0x475 & 0xFF && configfile /BOOTWS/2.lst checkrange 1 calc *0x475 & 0xFF && configfile /BOOTWS/1.lst boot grub> read 0x8280 Address 0x8280: Value 0x0 grub> calc *0x475 & 0xFF 1 (HEX:0x1) No, I do not have any options to set USB disk emulation in BIOS. In setting boot order menu, it's just "Removable dev.". I used RMPREPUSB 2.1.630, set MS-DOS bootable, FAT32, and no other options set (this means 1 partition, not 2), and install grub4dos to partition boot sector, not to MBR. Because this is the only way I can make USB flash drive bootable on this machine. So here's the rest of my story. I use WinSetupFromUSB 1.0beta7, and make XP PRO SP3 setup. When I boot this made USB drive on that machine, I get the error (I think that at this point BOOTWS\fd.lst gets executed): The system encountered an I/O error accessing multi(0)disk(0)rdisk(1)partition(1). Setup cannot continue. Press any key to exit. The good thing is, that if I load Plop boot manager and then choose boot from USB, it works! Setup continues without errors (root drive/partition becomes hd0,0). The next is a complete mistery to me. If I don't use Plop, setup throws "I/O error", as mentioned above. If I enter grub edit mode (press 'e') on file winsetup.lst, and temporarily remove (press 'd') the line: "checkrange 0x00,0x01 read 0x8280 && configfile /BOOTWS/fd.lst", then (I think) the BOOTWS\1.lst gets executed, and I get the error "biosinfo.inf could not be loaded". Next, If I reboot/shutdown, and let grub4dos to proceed without modifications I always get the "biosinfo.inf" error. I did not made any permanent modifications, but somehow boot process gets modified permanently (and Plop doesn't help this time, even after loading it, setup also throws "biosinfo.inf could not be loaded" error). Mistery to me. The only way I cant revert to the original behavior, that is "I/O error accessing multi(0),etc." is to completely recreate USB with WinSetupFromUSB. The reason I need that original behavior is, that Plop can work around that error and setup can proceed error free. But this (recreation) is time consuming, pretty slow process.
  7. I also have this error: File \WINSETUP\XPpSP3\I386\biosinfo.inf could not be loaded. The error code is 14 Without any mappings usbdrive.tag is on: grub> find /usbdrive.tag (fd0,0) (fd0)