Search options (Page 87 of 213)

Well if you are installing with sp3 you do not need to provide a key at all to install...
you validate after the install...

with sp2 or earlier there are lots of variables... OEM, retail, MSDN, VAR, Corp, ect... plus there were multiple encodings. (not all keys will work with all discs)

Make sure you have slipstreamed sp3 to avoid many issues with your key being accepted.
And be sure you have the same version of windows that your key is for - retail key requires retail disc

Is this re Wims suggestion to switch to a new programming language for the Win7 tool?

I did not think that anyone jumped on that idea at future.signet... is there another disscussion that i missed?
IDK if everyone will jump ship given that all of us are already quite comfortable with autoit.
I have forgotten more languages than most people ever learn... So i don't care, switching languages for me is like switching cars... not the same at all, but so much alike it only takes minutes to get on the road .

What do you think of it? Are you useing it for something or jsut playing?

I like the idea of all of us useing the same platform for our app (or apps)...
this has always been a benifit to us. We have several shared code modules now, Siginet wrote the OS detection routine that Wim and eventualy I modified for BASE

That is very helpful info... we will need to compare those drivers to the packs...
Since you included your HWIDs above that should be a good start...
the only other clues would be contained in the setupapi.log...
It is too huge to post here but you could go through it and post anything that looks like it is related (search for HWID of failed device )

well if you did not select a location on the 'Location' page it crated DriverPacks.net in the root of the HDD you ran DriverPacks BASE from

However your log clearly states

2009-07-01 08:38:35 : <SEL>  Selected Location E:\WINDOWS\DriverPacks.net.

(I love it when users include their logs it clears up so much confusion )

your SAD CMD file is at E:\WINDOWS\DriverPacks.net\dp_inst_tool.cmd

PS We will ask Galepo to add a link to his guide... (Please)
PSS any reason you skipped video and sound packs?

"I'm not sure if or how it even injected the drivers. If it did inject them, why would I even DriverPacks BASE SAD feature?"

well you could search for a Mass Storage driver name that is not included with windows... 3waregsm for example
the process is extremely complex so i am unable to summarize it for you...
I do know that it is used by many users without issue (thousands perhaps)

You need SAD because offlinesysprep is only adding Mass...
Many drivers in the packs will fail if the DriverPacks Finisher is not run... Offline sysprep does not call the finisher

I am stumped too... let us see if the rest of the team has any ideas...

PS you may be able to find clues in your %SystemRoot%\SetupAPI.log

it is a huge file and you will not be able to post it here in its entirety...
However if you were clever you could find the sections of the file that are relative and post them
Hint - Use the HWIDs (perhaps device names) to search the file

alcohol does have an ODD emulator... that would be it...

I create my images and test them in vmware... you could use virtual box or other VM software if you like...

I would have created the image on the "new" machine.
I would have tested it with VirtualBox or VMWare before burning.
burn after test load on VM passes... (you could test the burned DVD in the VM too if you like)
Then test on live metal... old machine or laptop or...

Qt GUI creator ?

no you will not need to remove drivers... just make sure the MB (MotherBoard) is not powered when you are playing

I belive you may have some kind of emulator running like Daemon tools, a virtual ODD software of some type. Several companies offer virtual ODD software...

Your "new" machine does not have a burner? (is this the laptop you refered to above?)

The thread must be followed and absorbed... it has a couple of sister posts that are stickied too...

That info is as complete a guide as has been submitted to date...
There is a Sysprep version of BASE released to the testing team ATM...
The Guide will be updated after the new platforms support is released in this forum and as a news item on the home page.

I will sumarize for you....

The best plan is
use Galepos offline sysprep for our mass storage pack
then use the DriverPacks BASE SAD feature with Method 2, calling dp_inst_tool.cmd from runonce or guirunonce reg entry added when the machine is resealed.

Did you burn your DVD using the burner that is known to be problematic?

Well we all knew nothing at one time you are polite and respectful and thoughtful... that buys you some lattitude with regard to our posted 'no noobs' policy. Its the noobs who want to pretend they know it all that will ususally buy themselves a helping of 'the treatment' .

So I understand your reluctance with no experience and no mentor to watch over your shoulder...
Let's put it like this...
Suppose you took a brand new DVD burner and laid it in the driveway and smashed it Flat with your car...
That would cost you Twenty dollars... Oh well... that is less than dinner for one at a nice restaraunt...
I Don't want to seem mean but i am going to say it anyway... You could buy a machine just like yours for about $100...
You really don't have anything to loose as long as you have BACKED UP YOUR DATA.

Go for it Buy a New DVD burner from NewEgg.com have it delivered to your doorstep.

I always leave the PC plugged into the wall this grounds the case and prevents ESD (static)
with newer machines you must pull the 20+ pin cable from the Mother board to power it off if you don't have a power switch on the power supply.

Install the DVD (super easy, look at old ribbon cable note direction, replace cable same direction on new drive... (red wire is pin 1 ALWAYS))

vacuum out your case (a canister vac with a hose works just lovely in a pinch - not optimal, but OK) Don't burn out the poor little fan bearings by spinning them at ludicrus speed for an extended time with the vacuum.

If you burned your disc on that questionable DVD then i am certian it is your problem - replace it = No Brainer.
   I would replace the cable first, but I am going to bet you don't have an extra one laying around... You can "thumb" your existing cable to be sure it is secure in its sockets. Cables often will wiggle loose. Especialy if the machine is transported (IE "tower flex" )  The drive is the more likely candidate to fail - Since it has moving parts )

Both the IDE Cable and the DVD burner are Cheap and Easy and consistent with my "Cheapest Easiest First" Rule...

You are still prolonging your pain... I told you i knew you had a Hardware issue. You responded with "Yeah that drive has given me problems before." ... ... ...  I could give you a bunch of techno mumbo jumbo about why it might verify in windows and then fail in textmode but spare both of us

Yes i am seeing issues with the graphics b 9.06 and the language pack...

I thought it was jsut a bad upload on those two since I just did them...

What other packs did you have issue with?