problems with nlited xp pro

[wildthing4]

I had a fire where a guest was smoking in my house against my wishes and fell asleep with the cig. long story short all 7 of my computers are now fubar'ed. So, I need my old gateway laptop inorder to work which creates an additional problem, my wife had lent it to her son and he installed some pirated crap on it and it to is fubar. It needs a new clean install which I cannot do as all the media to do this was in the fire and the subsequent hosing down. A friend of mine had an install cd of win xp pro and lent it to me and as the laptop in question had a legitimate xp pro install and key I accepted this offer and tried to clean in stall however it stops the install...why you ask, well it is older and it is asking for a bios file and a crap load of drivers as it appears it will not accept the default ones on the wixp pro cd. where are they..well thet are on the gateway support page listed here: http://support.gateway.com/support/drivers/search.asp?st=pn&param=3501373. I tried to us nlite to put these drivers in and I have now wasted 4 cd/dvd's . I am obviously less then half asse'd and cant get it right nor can I locate a/n appropriate description on how to accomplish what is necessary. So, what do I want to do? well I want to take the offered win xp pro sp3 cd and slipstream all the driverpacks from the gateway support link above and enter in my legitimate cd key and change nothing else and create an install to wipe this laptop clean with the obviously expected create cd. all the driver packs from the support site listed are in exe format and I have not found any less then 2 bazillion opinions as to how to nlite a particular thing and none of them explain what I am looking for...at least not that I have found yet. My eyes are blurred I have a headache and I am about ready to cook the cat. I am very un-tech and obviously doing something wayyyy wrong. all I want to do is just put in the drivers and serial and burn and go...may I impose upon all of you to assist me?

thank you all very much for any assistance.

Mark

[johnhc]

wildthing4, please don't cook the cat. I am afraid we are hard pressed to help you, since it sounds like what you (and your friend) are doing is a violation of the MS license agreement. What kind of legal XP Pro key do you have? What kind of CD does your friend offer? Please post the Pid value in the setupp.ini file on the CD (open with notepad). Unless yours is a Retail key, it is not legal to use it except on the original machine it was installed on. I am very sorry for your damaged home and machines, but it would seem to be an insurance problem at this time. Your insurance company should replace the machines and the OSs to go with them. What happened to the OS that came with the laptop? Usually it comes with a recovery CD or partition and the appropriate drivers to get the machine back up. Was it burned also in the fire? Newer machine come with a recovery partition on the HDD and therefore should be intact even if the current installed OS is damaged. Perhaps you can get the insurance company to quickly allow you to buy an OEM CD to install on the laptop. We can certainly help you there. What was the original OS on the laptop? Sometime newer machine with Vista present a real problem finding XP drivers. Good luck and please let us know where you stand. John.

[wildthing4]

wildthing4, please don't cook the cat. I am afraid we are hard pressed to help you, since it sounds like what you (and your friend) are doing is a violation of the MS license agreement. What kind of legal XP Pro key do you have? What kind of CD does your friend offer? Please post the Pid value in the setupp.ini file on the CD (open with notepad). Unless yours is a Retail key, it is not legal to use it except on the original machine it was installed on. I am very sorry for your damaged home and machines, but it would seem to be an insurance problem at this time. Your insurance company should replace the machines and the OSs to go with them. What happened to the OS that came with the laptop? Usually it comes with a recovery CD or partition and the appropriate drivers to get the machine back up. Was it burned also in the fire? Newer machine come with a recovery partition on the HDD and therefore should be intact even if the current installed OS is damaged. Perhaps you can get the insurance company to quickly allow you to buy an OEM CD to install on the laptop. We can certainly help you there. What was the original OS on the laptop? Sometime newer machine with Vista present a real problem finding XP drivers. Good luck and please let us know where you stand. John.

it is the key from the bottom of my laptop that goes to xp pro it is a retail key as I never buy a computer with a recovery partition I always, always make them install a retail out of the box and send it along, granted I pay xtra for it but that is my call.. there is no violation of terms of service. I legitimately bought and own it. I , likewise bought 2 xtra sets of recovery media or rather the driver cds which were also hosed. The disk is his retail xp pro install minus his serial. figures that the first thing that someone speaks of are how forthright everyone is and how I must be doing something naughty. However , my REAL JOB, is I am a/n copyright /patent and trademark attorney and I can assure you , positively, that what I am asking is absolutely 100% legal. It is actually the retail key everyone is paying for. Do you work for ms sales and want to obtain commission by suggesting I spend more money on ms products then I already have? If you are implying that I am using warez then more likely then not, I would not have had to ask for assistance nor would I have been so open in reference to what I was about. The question was how to integrate the drivers and nothing more. but know...far be it from any forum member to actually answer a question directly. So, as long as I am not using an oem manufactured and deployed version it matters not as long as I paid for my version and The key I have is paid for. So you can assist me or not as you see fit but do not continue to make baseless and blanket statements requesting information unnecessary to have in order to answer the question/query.

Mark Bellamy JD.

Brighton Law Group[retired]

Edited April 17, 2010 by wildthing4

[johnhc]

wildthing4, I am not going to fight with you and I am sure when it comes to legal matters, you know much more than I about these aspect of things. The fact is that the forum rules restrict us from helping people who are violating the forum rules or laws. I am certainly not an MS employee and doubt anyone else kind enough to donate their time here is either. As I said earlier, we will be glad to help. Please answer the questions that I asked in my first reply, attach your Last Session (as requested in bold RED letters above) and we will do our best to help. I should point out that the key and CD need to agree. Both would need to be retail, in this case. Enjoy, John.

EDIT: I took a look at the web site and have some more questions: What model laptop do you have - 9520303.exe - Gateway 600YG2, 600YGR, 450SX4, 400SD4? What kind of HDD (SATA, PATA, AHCI), video, Sound, modem, and wireless? What kind of BIOS file was it asking for? Please give us more details about the install errors you get. Tomorrow I will try to extract the MB drivers I DLed.

Edited April 18, 2010 by johnhc

[jaclaz]

Brighton Law Group[retired]

Which one? The one in NY?:

http://brightonlawgroup.com/Home.html

I knew a chap that used to work in there, cannot remember his name right now, Klagefeld, or something like that, do you know him?

jaclaz

[cluberti]

Getting an XP CD from another person (an actual physical disc) is a gray area in the US, but it's been a protected way to get access to things not software in the past, so this is probably in the clear. Since we're making a copy of something legally owned (that's what the CoA sticker proves), and we didn't acquire the disc by means of downloading from a source other than Microsoft, the post is legit and should be answered. I see we've made progress, but let's not go overboard here - until the courts say otherwise, borrowing an OS install disc shouldn't be considered in violation of the rules (assuming one owns a legitimate copy of said OS, of course).

[Ponch]

different problems here

-meaningless tittle for this thread (I usually stop here).

-borrowed cd probably not matching hardware and/or original key

-multiple exe drivers to be extracted

(-no hardware description)

-self confessed non techie user will need lots of "clear" explanations on "grey area" operation.

[wildthing4]

different problems here

-meaningless tittle for this thread (I usually stop here).

-borrowed cd probably not matching hardware and/or original key

-multiple exe drivers to be extracted

(-no hardware description)

-self confessed non techie user will need lots of "clear" explanations on "grey area" operation.

Lets clear it up for the record as I do not wish to fight either, but I took exception to the post for what ever reason.

Computer model: Gateway laptop model 600yg2. I never buy a computer right out of the box. I buy the operating system retail boxed and have them install it and forward said os to me and place the lic.sticker on the bottom of laptop. I have them send the driver install separate of which I was provided one cd and one xtra which I paid for , total of 2. Both fubared in the fire or subsequent hosing.

ponch: However meaningless the title maybe , it explains ,thesis-wise what the problem is briefly. borrowed software need not match as it is retail and my setup is retail and lacks tech configuration /deployment. It is user configured and retail. no oem pre-install deployment, no recovery partition. This I also stated briefly. I am not so un-savy..just nlite ignorant. I am a member of technet and I could create this using deployment tools but it takes longer. I ended up using just an install dvd that came with one of my monthly technet mailings and just inserted it and installed using my PAID for license key and voila , it wiped the slate clean and I just installed the driver pack exe files separately. As far as the coa is concerned...no matter what an agreement states or how many where as and what for, it boils down to , you can have one back up copy, and you can only have the original install on one working computer at a time with out obtaining a multi - user or volume license. I am abiding by this. and since I gave the dvd back to my friend and came across the sp3 all in one , which works like a new windows 7 dvd where it installs and validates based on your license not configuration, I have been able to restore this computer. as far as no hardware description goes I posted a link directly to the my drivers and download page which contains therein a description of the os and hardware specs in the adobe reader document.

PID: there is no pid as I was creating iso files and viewing them in a virtual clone drive then running them in vm and when they did not work..being the p*** pot and cantankerous person I am, I deleted them as I was also using someone elses computer and was creating quite a clutter.

I have not violated msfn rules..are you going to tell me that all the people on this forum that are nliting are using there own hard copy of an os, neither borrowed nor found or recovered using winbuilder iso by winfuture.de? And I would not intentionally violate these rules and I would admit to my misdeeds if I thought I had. You can use any win xp pro cd to create an nlite, I have an original win xp pro sp0 from my first gateway as well as an sp1 and 1a and sp2. I could have used any of these to create the build and in fact there are numerous posts on this forum and others that define such. as long as you are using what is rightfully your to use. But I just cannot grasp the nlite thing as , even the nlite tutorials at "how to heaven" jump around so much that it is very confusing.

SO......I am not trying to alienate anyone. I apologize, and I absolutely mean it. I am sorry. But I just did not think it was necessary to allude to warez production , which is how it came across to me. I still would like to make an nlited production changing nothing except adding the 12 driver exe files from the support page at gateway. I believe I can get to the part where the driver need to be inserted but I run into problems extracting the appropriate files and allowing nlite to place them. May I ask for assistance with this ? Please! with sugar on top. If there is something posted somewhere that I am unable to locate please direct me and I will do my best to follow the directions.

Brighton law international..world court and war crimes representation. now absorbed and defunct in its original "LLC" capacity.

Again , I am sorry.. I am just seeking assistance from the number one google hit spot when asking for help with nlite.

Be well.

Mark

Edited April 18, 2010 by wildthing4

[johnhc]

wildthing4, I have managed to extract the drivers from the MB chipset. The trick is to run the DLed .exe in a command prompt with switches of " -A -A" (without the quotes, notice the blank before and between). This will extract the drivers into a folder called InfInst inside the Intel folder in your Program Files folder. From here you can decide which driver(s) you need and point nLite to it/them. You still have not answered most of my questions (Pid in the setupp.ini file, etc). There are several sound and wireless drivers and we need to know which hardware you have. I really want to see a Last Session file, even if you make another nLite run just for that purpose. When you run nLite, please always start with a fresh copy of the CD files/folders and run nLite only once against it. Testing under VM is a great idea and allows you to post screen shots even of the install errors you might get. Knowing your specific Gateway model, I will take another look at the link you provided. Remember, please that more imformation is much better than less. Enjoy, John.

EDIT: I hope you have seen the newer nLite Guide in the Stickies, above.

EDIT: I just DLed the video drivers and extracted the .exe with 7-Zip with no problems - no tricks required. You can DL all the drivers and extract them as needed and point nLite to them. There is a modem driver, if you ever use dial-up, or you can go into the BIOS and disable this modem. It would be OK to place all the sound and wireless drivers into the mix using nLite. Windows Setup will only include the drivers into your installed Windows that have corresponding HW. I need to warn you that I have an obligation this afternoon and will probably not be responding after an hour or so.

Edited April 18, 2010 by johnhc

[RichardStrong]

different problems here

-meaningless tittle for this thread (I usually stop here).

-borrowed cd probably not matching hardware and/or original key

-multiple exe drivers to be extracted

(-no hardware description)

-self confessed non techie user will need lots of "clear" explanations on "grey area" operation.

Lets clear it up for the record as I do not wish to fight either, but I took exception to the post for what ever reason.

Computer model: Gateway laptop model 600yg2. I never buy a computer right out of the box. I buy the operating system retail boxed and have them install it and forward said os to me and place the lic.sticker on the bottom of laptop. I have them send the driver install separate of which I was provided one cd and one xtra which I paid for , total of 2. Both fubared in the fire or subsequent hosing.

ponch: However meaningless the title maybe , it explains ,thesis-wise what the problem is briefly. borrowed software need not match as it is retail and my setup is retail and lacks tech configuration /deployment. It is user configured and retail. no oem pre-install deployment, no recovery partition. This I also stated briefly. I am not so un-savy..just nlite ignorant. I am a member of technet and I could create this using deployment tools but it takes longer. I ended up using just an install dvd that came with one of my monthly technet mailings and just inserted it and installed using my PAID for license key and voila , it wiped the slate clean and I just installed the driver pack exe files separately. As far as the coa is concerned...no matter what an agreement states or how many where as and what for, it boils down to , you can have one back up copy, and you can only have the original install on one working computer at a time with out obtaining a multi - user or volume license. I am abiding by this. and since I gave the dvd back to my friend and came across the sp3 all in one , which works like a new windows 7 dvd where it installs and validates based on your license not configuration, I have been able to restore this computer. as far as no hardware description goes I posted a link directly to the my drivers and download page which contains therein a description of the os and hardware specs in the adobe reader document.

PID: there is no pid as I was creating iso files and viewing them in a virtual clone drive then running them in vm and when they did not work..being the p*** pot and cantankerous person I am, I deleted them as I was also using someone elses computer and was creating quite a clutter.

I have not violated msfn rules..are you going to tell me that all the people on this forum that are nliting are using there own hard copy of an os, neither borrowed nor found or recovered using winbuilder iso by winfuture.de? And I would not intentionally violate these rules and I would admit to my misdeeds if I thought I had. You can use any win xp pro cd to create an nlite, I have an original win xp pro sp0 from my first gateway as well as an sp1 and 1a and sp2. I could have used any of these to create the build and in fact there are numerous posts on this forum and others that define such. as long as you are using what is rightfully your to use. But I just cannot grasp the nlite thing as , even the nlite tutorials at "how to heaven" jump around so much that it is very confusing.

SO......I am not trying to alienate anyone. I apologize, and I absolutely mean it. I am sorry. But I just did not think it was necessary to allude to warez production , which is how it came across to me. I still would like to make an nlited production changing nothing except adding the 12 driver exe files from the support page at gateway. I believe I can get to the part where the driver need to be inserted but I run into problems extracting the appropriate files and allowing nlite to place them. May I ask for assistance with this ? Please! with sugar on top. If there is something posted somewhere that I am unable to locate please direct me and I will do my best to follow the directions.

Brighton law international..world court and war crimes representation. now absorbed and defunct in its original "LLC" capacity.

Again , I am sorry.. I am just seeking assistance from the number one google hit spot when asking for help with nlite.

Be well.

Mark

[RichardStrong]

wildthing4,

Seems you are experiancing a lot of greif over this. My suggestion, forget the ulcer, forget nlite. You seem to know the drivers you need

and you seem to be able to get your hands on them,so you could just put them on a seperate CD and install them from there. You don't do it very often.

Yes I use nlite, but am not up to explaining it, I just find my way and would but am not up to giving directions. Even so, I have 18 computers in my home lab and I still have a CD pack with drivers in it and sometimes use them for a new install. Hey, it's just easy and quick.

Good luck,

Richard

[submix8c]

As johnhc correctly states, the PID info within SETUPP.INI (the ROOT of the CD) is important. If you are using a Retail Key (you stated so) then there are certain files you may need (in addition to the correct PID info) depending on the "borrowed" CD. Dell was notorious for "altering" the CD in such a fashion as to not even have usable OEMBIOS.xxx files (in the I386 folder) as they intended that you (generally) use CD#1 to boot from, then "copy" files from it and then the "supposed Full XP CD" (lacking needed files). It is possible to construct a Retail CD from it, however.

I believe (in light of several other topics in reference to these "special files") that assistant can be provided.

1 - Open up the SETUPP.INI and list the contents (4 lines)

2 - Provide a list of the ROOT of the CD

3 - Provide the type of PC that the CD was initially used for ("borrowed" from)

4 - Can you provide the initial Service Pack Level of both your COA sticker and the "friend's" COA sticker (there are some minor variations in the I386 "special files" depending on this). The COA's should indicate this.

After that, it may be possible to create a "true Retail" from files directly from MS.

[wildthing4]

As johnhc correctly states, the PID info within SETUPP.INI (the ROOT of the CD) is important. If you are using a Retail Key (you stated so) then there are certain files you may need (in addition to the correct PID info) depending on the "borrowed" CD. Dell was notorious for "altering" the CD in such a fashion as to not even have usable OEMBIOS.xxx files (in the I386 folder) as they intended that you (generally) use CD#1 to boot from, then "copy" files from it and then the "supposed Full XP CD" (lacking needed files). It is possible to construct a Retail CD from it, however.

I believe (in light of several other topics in reference to these "special files") that assistant can be provided.

1 - Open up the SETUPP.INI and list the contents (4 lines)

2 - Provide a list of the ROOT of the CD

3 - Provide the type of PC that the CD was initially used for ("borrowed" from)

4 - Can you provide the initial Service Pack Level of both your COA sticker and the "friend's" COA sticker (there are some minor variations in the I386 "special files" depending on this). The COA's should indicate this.

After that, it may be possible to create a "true Retail" from files directly from MS.

Using the win xp pro sp3 cd I received from technet sometime back I was able to format and clean install and just apply the retail key from the bottom of the old gateway laptop. One of the problems was that I kept trying to install the x64 winxp pro and use the key from the computer and I was able to locate the original paperwork for this computer and it is x32[x86] so the key and the drivers would not work and nlite could not make it do something it is bot designed for. There is not enough ram and or cpu/gpu power to use x64 and I was , however unintentionally, trying to force this install of the x64 bit version. I kept failing do to user[me] error not any part on the nlite . However, I still would like to learn to do this correctly. I actually received assistance in creating a valid copy of windows xp pro x86 from ms themselves. They assisted me in just altering or changing a few files and then re-applying or changing the product key so the cd contents and key match. anyway I now have a cd specific to this computer but without the drivers integrated.

Thanks. If there is a place on this forum that specifically address's inserting the drivers please direct me to it and I will try to learn it , otherwise, the computer is up and running.

Mark

[johnhc]

wildthing4, use of nLite, including drivers, is discussed in this forum. I have posted earlier how to extract the drivers and use them. Please read my post, answer my questions and then ask specific questions concerning any problem(s) you still have. Enjoy, John.

[Ponch]

If there is a place on this forum that specifically address's inserting the drivers please direct me to it and I will try to learn it , otherwise, the computer is up and running.

Here you need to download the corresponding exe's from the site you linked to,

run them to get them packages they are to extract themself, and (like I tried for the WiFi) create a folder (in this case "C:\cabs\") where you will find .inf files.

When you've got inf for all devices you need (the exe might extract differently), run nLite and point to them inf.

-do not copy those driver files in the CD's directory

-do not copy them on the desktop as some user reported strange side effects.

If all inf are in a same subdir, you can use the "include multiple drivers" option to have nLite search for those inf files inside one folder.

When you have all thos inf files in the drivers window, remove those that are not for XP x86.

Cheers.

My first post would not have been that bad if it was not coming after the others.