"Setup cannot find the End User Licensing Agreement (EULA)" and SLP Question

Discussion in 'Windows XP / Older OS' started by hyphenateddigital, Dec 26, 2018.

  1. hyphenateddigital

    hyphenateddigital MDL Novice

    Dec 22, 2018
    8
    1
    0
    #1 hyphenateddigital, Dec 26, 2018
    Last edited: Dec 28, 2018
  2. vanelle

    vanelle MDL Expert

    Sep 22, 2014
    1,009
    733
    60
    #2 vanelle, Dec 27, 2018
    Last edited: Dec 27, 2018
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. hyphenateddigital

    hyphenateddigital MDL Novice

    Dec 22, 2018
    8
    1
    0
  4. Sp0iLeDBrAt

    Sp0iLeDBrAt MDL Novice

    Dec 14, 2015
    21
    10
    0
    Just to chip in: from experience with nLite, you only need to select one for point A3. It will copy the same files to a folder anyway. Make sure you only integrate one AHCI driver into the image and, if you are also integrating other drivers, make sure it is the first one on the list (for e.g. first select the AHCI one manually, then select the whole folder with the other drivers). To make sure the integration went well (after install) you can check system32\NLDRV folder. If the subfolder 0001 contains the AHCI driver, you are doing it right. Maybe it is also possible to find the NLDRV folder on the image as well beforehand, I just don't remember any more.

    Cheers
     
  5. hyphenateddigital

    hyphenateddigital MDL Novice

    Dec 22, 2018
    8
    1
    0
    @Sp0iLeDBrAt

    Thanks for the information. I may end up having to provision a new image in that case.

    Now, onto my next issue. How would one go about adding SLP strings to my particular BIOS, extending OEM functionality to my XP image? @Serg008, do you have any ideas? I noticed you worked on a couple of UX51VZ bios in the past. None of the tools one would typically use to go about doing so have been updated in nearly a decade, at least the programs posted here. I'd really hate to mod my bios, considering the last time I made such an attempt, I had to buy a new motherboard. :oops: I've cycled through about 4, so far. :oops:
     
  6. hyphenateddigital

    hyphenateddigital MDL Novice

    Dec 22, 2018
    8
    1
    0
  7. vanelle

    vanelle MDL Expert

    Sep 22, 2014
    1,009
    733
    60
    #8 vanelle, Dec 27, 2018
    Last edited: Dec 27, 2018
    OK
    1. Your hardware is too new and not suitable for server 2003 / 2003r2
    If you have solved the problems with the SATA driver, then certainly comming up more problems with the CPU (Intel Core i7)
    2. XP x64 is a Server 2003 / server2003r2 client product and not a XP Product - so it is totaly different from xp
    IT is better to call it Server2003 x64 client and not XP x64 - this helps to find solutions coz you have to loock on server2003 web sides (and not on xp)
    therefore
    - install x86 for testing do not solve your problems or help to find solutions
    - there is no sp3 for xp x64 coz there is no SP3 for server2003 released
    3. if posible. dont use this f** nlite - you get more problems then solutions
    try to install the SATA driver manualy during early setup (During the Windows Server 2003 install, press [F6] when the system asks if you need to provide additional storage drivers.)
    or use a winnt.inf
    4. disable SATA Native Mode in BIOS

    all in all
    i agree with @Serg008 use win7 (it is still supported)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. hyphenateddigital

    hyphenateddigital MDL Novice

    Dec 22, 2018
    8
    1
    0
  9. urie

    urie Moderator
    Staff Member

    May 21, 2007
    8,824
    3,177
    300