You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
if you use bartpe or ubcd4win on your flash drive
you can load an iso image with a plugin for bartpe (see the ubcd4win forum) however it has a 512 meg limit on the iso. so you would not be able to do this directly you would need to boot to bartpe then launch setup.
(since a slipstreamed image would exceed 512 meg)
IE copy all UWXP files and an iso image that contains bartpe or some other PE that runs a setup that is not in the iso but also on the flash drive.
I actually forgot about an old friend of ours who integrates RVM nLite and DriverPacks and supports RIS in his application.
RogueSpear's autoimage will do this for you. watch in awe.
No need to reinvent the wheel.
RogueSpear's autoimage will do this for you. watch in awe.
No need to reinvent the wheel.
Duplicate post deleted
LOL
Nice work 
official DriverPacks alpha is in codeing stage as i write this
now we have vista posts in the xp sp3 thread will the insanity ever end...
ROFL
yes you can delte the ati tag file in the OEM folder.
you shouldnt get driver errors in vmware or virtual machine as they emulate standard hardware
yes you are doing somthing wrong...
there are quite a few posts on here about this - try to search for stuff. The link below is even stickied.
here is a starter link LINK
the finisher only runs once and deletes itself and will not run again. so no you will only get drivers after KTD is used.
no control panels or start menu shortcuts or setup programs will be run. PERIOD.
I have said this at least 500 times: ( at LEAST 500 )
KTD has no useful purpose on a normal machine. Its for a Technicians Test Bed (what i call an AIR machine.) that will have cards plugged in one after the other for purposes of verifing if they are working or not. (to eliminate windows as the problem by useing a Test Machine)
Look at it like this - suppose you load a machine for an end user with KTD (which takes up 1.5 gig of disk space) and then add hardware 6 months later - do you really want a 6 month old driver @ 1.5 gig. and no control panels - Heck No! that is a huge amount of disk space to backup / defrag / virus scan / waste especially when the odds it will ever be needed is near 0%.
how often do people add "NEW" hardware and don't have the disk that came with the "new" hardware.? (scratches head bewildered)
instead create a "drivers only CD" {Search the forums} and use the search removable media feature of windows add new hardware. let's face it if your adding a new device then you are at the machine arn't you??? take the driver disk with you DUH!
no the finisher will not run post install because the finishers inf files (that come bundled in the driverpacks) are deleted when the finisher runs and only the finisher will "automagicaly" finish the drivers.
dont do this - dont try to do this - its not a good plan and it doesn't give the desired results.
I am half tempted to remove KTD as a GUI option to eliminate this FAQ and confusion surrounding it.
side note MOST drivers in the packs do not need the finisher at all (i am guessing over 90%)
side note 2 the finisher will NOT install drivers only windows does that.
KTD should only be used IF you are loading a test machine on your workbench.
counter indexes to 501 times. steps down off soap box.
perhaps after i get BartPE on the run ill work on a - RIS / syprep / OEM install - platform in to a beta.
Got it now thanks!
you read correctly... only mass storage. thus far...
this thread was actually continued from a few posts in the wrong forum
lead in posts
Now that XP SP3 is widely available, how about a modification of DP Base so it will see SP3 and not error with KB888111 saying SP1 or SP2 not installed.
@ BigBrit
Why did you put a post about windows XP in the Vista thread???
XP sp3 is not officially released yet. When it is, then we will add that.
(is there anything less stable than a microsoft beta?)
The code for detecting it will depend on its format, which is not finalized yet.IE i dont want to write a hundred of lines of code twice. especially when it may introduce problems in an otherwise stable release. the mere fact that we havent had any bugs reported since the last release is reason enough. "If it ain't broke dont fix it."
Hi Overflow,
I don´t mean any disrespect, just a suggestion:
It may be a good idea to prepare for the launch of SP3 by adding the necessary code a little in advance and play with the SP3 RC1 a little. It is RC1, not beta and I am sure the detection of a new SP will not change that much from RC to RTM.
You guys could put out a beta DP release, so people who do test the SP3 can test it and report feedback prior to the launch of SP3. If you only start working when SP3 is released you won´t have that much time to fix bugs and people might become impatient because they might have slipstreamed SP3 already and won´t have a working DP release to go with it.
Anyway, thanks for your work on the DP´s ....
My personal wish would be a complete DP solution for Vista but that´s far away I guess ... :-)
Bye,
Alex
midiboy wrote:It may be a good idea to prepare for the launch of SP3 by adding the necessary code a little in advance and play with the SP3 RC1 a little.
That's actually not that bad an idea. SP3 is supposed to be released in 2008 (As early as Jan...as late as Dec!). It's encouraging to see it go RC1 this early, which means very little will change to the content, only bug-fixes at this point. SP3 RC1 is a restricted download at the moment (I've got mine), but RC2 will probably go public either Jan or Feb so we'll have loads of testers available.
At the very least, having a DPBase beta will allow you to refamiliarize yourself with the code and there are many people with fresh ideas for the DPBase.
Something to ponder.
Vista support is still a ways off, but getting closer.
WHOOPS - I didn't realize I had posted in the Vista section.
As XP SP3 is now RC1 I agree the code is almost Gold.
I need rc1 to get the beta started
Search for drivers only CD on this forum...
and read before you post please
Please Read the READ BEFORE YOU POST in my sig
and update all missing info in your post above.
LOL Where would we put the guide (i kill myself!)
hmm... guess we will wait for jaak...
I Realize that XP SP3 is going to be released in 2008.
This is the Thread to Discuss Service Pack 3 for XP!
There is a beta available to team members. check the nightlies.
Those are available through the laptop manufacturer...
we don't provide CD's
Hello jorijo,
Welcome to DriverPacks.net and thanks for joining. We're Glad your here!
Do you have a specific HWID you are asking about?
We dont support hardware by their names, we support them by how they report themselves to windows.
IE their HWIDS. If you don't know your HWID's there is a tool for that in my sig below.
@ BigBrit
Why did you put a post about windows XP in the Vista thread???
XP sp3 is not officially released yet. When it is, then we will add that.
(is there anything less stable than a microsoft beta?)
The code for detecting it will depend on its format, which is not finalized yet.
IE i dont want to write a hundred of lines of code twice. especially when it may introduce problems in an otherwise stable release. the mere fact that we havent had any bugs reported since the last release is reason enough. "If it ain't broke dont fix it."
needing a good oops...? lol
well your not a newbie anymore now your a regular...
or perhaps you didn't notice the upgrade you recieved for having more than ten posts...
i will assign the bug to myself... tee hee..
Thanks Basil you have helped to make driverpacks that much better and i belive i speak for the entire DriverPacks Team when I say
thank you
Bug assigned to me! i had better get on it or ill have to chew myself out!
As i said you may have discovered a bug in Bâshrat the Sneaky's code.
I am in process ATM of codeing a base beta and will add this to my list of bug fixes.
PS you can report this over at bugtracker if you like!
95 percent of our users do not use method one becuse of the 4096 character limit. and Bâshrat the Sneaky himself considers it oblsolete.
I Think that it is very useful because the result of a method one slipstream is a disk that can be used by add new hardware wizard on an existing install (select search removable media). however this takes up a little over 500 meg as opposed to the 290 meg used by method two but they both are so much better than the 1.5 gig they consume when extracted. (IE new hardware was added and you need a driver but dont know which one - well its bound to be in teh packs somewhere - hee hee)
Mass storage text mode is deliberately separated from the packs because it is unique and unlike the packs.
It is in fact not a pack at all. although all the files for text mode are extracted from the current mass storage pack (as you supected) the pack itself is not needed on the destination disk at least not for a recovery cd. if you were doing an install you would suffer greatly because of the performance enhancments that exist in the PNP drivers. (16 bit vs. 32 bit drivers)
I would like to reiterate here they are not mutualy exclusive they are complimentary.
I agree that both methods should produce the same result - if text mode is the only box selected.
You are now an unofficial tester - thanks for helping us to help you.
jeff...
DriverPacks.net Forum » Posts by OverFlow
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.110 seconds, 5 queries executed ]