The process is about 500~1000 lines of code, it's to complex to explain here wink
IE it is not a simple matter of checking for the presence of a file or two... smile

the platform is thouroghly verified
- it really is an intense validity check -

furthermore the routine is different for each of the versions of XP,
and each of the versions of Win 2k
and each of the versions of Win 2k3...

the original code was written by Signet, then adapted by Wim, and finally tweaked by me.
it took years for multiple authors to develop into its current (nearly flawless) form wink

(no you can't fool it wink )

why?

is the volume accessable at all?

What is the HWID of the device? (tool in my signature)

its not a flaw... it is a known limit wink lol 

If you work for IBM they call that a feature ROFL

2,630

(18 replies, posted in Other)

Jaak wrote:

XP clients can/will run in virtual machines in corporate low budget hardware. Clients cheap, network bandwidth increased, securised access, higher server CPU utilisation. lower (so they say) TCO and lower fossils burn (or carbondioxide output) because of lean machine with lower risk (but some 'network' congestion can be expected, even with IPV6)

they call that a terminal farm, Citrix wrote the book ms read to get on to that trick.  Kinda like the Netscape/IE debocile.
Citrix stole the idea from WYSE... shall i go on wink

without being able to reproduce your process myself
(you seem reluctant to reveal your steps to duplcate this issue - i have asked)

there is not much chance I nor anyone else will be able to help...

try this... i have not tested it but i belive it will work similarly...

use RIS as normal  AutoImage  DriverPack MassStorage but not the rest of the packs, just mass text mode.

put  a SAD M2 folder in the $OEM$\1  IE  "..\$OEM$\1\Drivrpks.net"
then use cmdlines.txt or copy/runonce type setup to call the DP_Install_Tool
- tool calls finsher - it should be lovely...

PS you could try to call DP_Inst_Tool from the cmdlines.txt directly with SAD @ $OEM$\DrivrPks.net
if this works as expected it should install the drivers then be auto-deleted with the $OEM$ folder.

the tool can be run over the network but you have to be connected first wink tongue big_smile
a network location would be more logical than KTD
Because you dont really need to "keep the drivers" after the install is done wink
but you could actually just 'keep' the DriverPacks.net folder on the machine - literaly KEEPING the drivers

the tool will install the drivers useing the redistributable MicroSoft tool "DPinst.exe" and then run the finisher -
I belive this will work perfect as the $OEM$ folder gets copied and will be local which is the key to success.

2,633

(2 replies, posted in Other)

Please read the tutorial (in my signature) and some of the other topics in teh FAQ forum and support forums.

These types of questions are well documented already...

the Short story is
- the 400 meg of packs are extracted takes 3~4 min and results in about 2gig of drivers
- then the HWIDS in the machine are used by setup which chooses the best one. but obviously it takes additional time to compare local hardware to 2 gig of drivers wink
- after setup the files are deleted (when windows installs a driver it copys it to windows so they are not needed anymore)

basic install questions are best answered at MSFN not here wink
We will be glad to answer advanced driver questions or questions related to missing drivers. or problems with DriverPacks BASE or the DriverPacks.
the mechanics of it we expect you to be aware of already wink

IE if it is not covered in this manual then it is a fair question. http://unattended.msfn.org/unattended.xp/view/web/1/
conversely if it is covered in that manual then it is not an appropriate question big_smile



Welcome and have a great day.

couple of things there is no dpfnsr.exe in any version of DriverPacks BASE

what version of DriverPacks BASE are you useing, you didn't mention?

KTD is considered dead... it has been replaced by SAD. Please take a look at that new feature. wink

http://www.ss64.com/nt/set.html

pertinent exerpt from above link...

Changes made using the SET command are NOT permanent, they apply to the current CMD prompt only and remain only until the CMD window is closed.
To permanently change a variable at the command line use SetX
or in the GUI - Control Panel, System, Environment, System/User Variables

Changing a variable permanently with SetX will not affect any CMD prompt that is already open.
Only new CMD prompts will get the new setting.

You can of course use SetX in conjunction with SET to change both at the same time, but neither SET or SetX will affect other CMD sessions that are already running. When you think about it - this is a good thing.

It is also possible (although undocumented) to add permanent env variables to the registry [HKEY_CURRENT_USER\Environment]
(using REGEDIT)

System Environment variables can also be found in [HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment]

Have a great day M8

2,636

(18 replies, posted in Other)

Wow... a Hero retires, this is sad news. But a retired hero is still a hero! we luv ya!

so Mac or Linux?

you are only presented the rest of the screens if you select a valid location.
If you do not select a valid location DriverPacks BASE is unable to determine which screens will need to be displayed next and it will display NONE except the updates.

IE If there is no platform then there are simply no choices for you to make! wink big_smile
All of the other screens depend on your platform and location selection.
If you don't select a valid platform and location then the only thing available for you to do is check for updates!

This is by design (IE the program can not read your mind)


PS this is why the select platform and location screen is one of the first
- the rest of the screens depend on those selections wink no (valid) selections no screens big_smile

PSS Cross posting is considered bad manners!
this was also already answered politely in your other post ! (did you read it)
http://forum.driverpacks.net/viewtopic.php?id=3565

You failed to follow the directions at the bottom of the location page...
- "Disc: the directory that contains the I386 directory." -
(Not the I386 folder itself...) We call this user error.

Excellent to know... you are correct 7zip must be run in a dos shell...
Autoit uses a command called rundos() to do this.

I am not really interested in updating hundreds of references in the base program to force checking the command interpreter.
IE test to see which one your using then attempt to locate CMD then verify it is a valid CMD ect...

Since you must force the change to command
the ball is in your court to be aware that this will cause you issues and
for you to then have to correct any problems you create by doing so.

However I am sure you are not the only one who has or will do this.
this post can serve as help to others who find themselves in your situation.
I will update your title so it will serve that purpose

Thanks so much for sharing the problem and the solution with DriverPacks

Welcome and have a great day!

PS I could be convinced to program the DriverPacks BASE to exit with a "critical error" if the command interpreter is not CMD wink

PSS it might make better sense for you to write a batch file (wrapper) that
sets your comspec to command
calls the CAD app
resets comspec when the CAD program exits wink

Those entries are created by DriverPacks BASE automaticaly...

From your Log 2009-02-22 10:00:51 : <GUI>  No OS could be detected.

enough said? (it looks like you meant to select E:\XPSP3S)

Thanks for providing your log it is so helpful in providing good answers... Well done!

Welcome to DriverPacks!

PS if you read the "description" at the bottom of the "Select location of Platform" you would not have needed to ask wink

Um... mass storage is unzipped for M2... so the files can be cabbed and integrated...

please try as Helmi suggested and verify the MD5 on the mass pack...

and disable QSC or delete the QSC folder or both - please report the result afterwards!

Excellent details for a first post Well Done!

2,642

(15 replies, posted in News)

I am on board... i agree that a vista finisher would be the ideal learning tool for the next viable OS (Win7)

2,643

(36 replies, posted in Other)

Hey we forgot Bâshrat the Sneaky! sad

Sorry no can do...

winnt32 installs are not supported... You are welcome to keep us up to date on your results...

PS how do you get the DriverPacks to work with winnt32?
(it will not work unless you did something manualy to force it to work)
can you describe your process in more detail...

PS let me repeat the only way to see if the MFT space is properly returned is to FILL the drive to it's FULL CAPACITY with files!
IE until free space shows as like 10 meg wink In Example: If it is a 400gig drive copy 100 DVD's to it wink


Moved to "other" forum since this is not a DriverPacks BASE related issue, and is unsupported.

2,645

(18 replies, posted in Other)

Well I hope Muiz does not read this ... wink

last time i went trolling for stats for Fuel... Why I chose not to support Vista.
I landed at several universities and google (at the time google still published that info).
- I choose four that vista showed up on.

http://forum.driverpacks.net/viewtopic. … 523#p10523

There were more users browsing the internet on Win98 than Vista....
4% of the hits was for Windows 98... Twice as many as Vista at 1.9%

It's still not doing very well! http://www.thecounter.com/stats/2009/January/os.php
(wow 98 still had 529,387 users)

http://www.w3schools.com/browsers/browsers_os.asp
2008           WinXP  W2000  Win98   Vista     W2003   Linux   Mac
December   71.4%  1.7%     0.1%   15.6%    1.7%     3.8%   5.3%

One thing is clear MS Windows accounts for 90% of internet browsing hits.

If something works well (is quality) then it will become and remain popular. No amount of marketing will change this.
I love the Mac comercial where the MS guy has two stacks of money. One to fix Vista and one to market it.
The Mac guys says "That is not enough money to fix Vista" and the MS guy says
"yeah your right" and moves the repair money to the marketing stack! - LOL -
So True! They could have fixed it for the money they spent to try to convince us it was not junk!
(by this i mean if Vista were transparent to older Apps then business' would have adopted it, and a larger share of end users)

I expect that Windows 7 has the potential to either become like Windows Win2k  (Released with 64,000 known bugs) or
to become the next XP / 98se... Given MS's new trend to produce a quality product, as we have evidenced with the XP SP3 release.
I expect that W7 wil be the product that we can recomend to clients with confidence. (is it just coincedence that quality became important when Bill left)

If we take it as a Given that W7 will be like 98/XP.
Win 98 survived another five years after the release of XP.
We can then project that XP will survive until five years after the release of W7. 2009 + 5 = 2014.
(amazing how I just arrived at the same year as the crititcal update cutoff suggested by MS) wink

Jeff

2,646

(18 replies, posted in Other)

I am sticking to my guns on this one it effectively becomes dead when they pull the plug on Critical Updates wink
at that point it becomes a stationary target for hackers wink on the other hand they will perhaps have moved on to greener pastures (Vista / Win7)

they are removed by the finisher...
if the finisher does not run then they are not deleted...

you tested it... hmm - i don't think so...

IE you filled the drive to it's "full capacity" with files?

perhaps you should investigate ADS as a possable leak...

many defrag programs will show the MFT, like O&O defrag for example wink

2,648

(18 replies, posted in Other)

i think the updates was 2015 but don't quote me wink

the MFT is the equivalent of the old File Allocation Tables (FAT)...
Master File Table (MFT) can be thought of as the table of contents for the file system smile
http://en.wikipedia.org/wiki/NTFS

the finisher is used to install control panels and other Setup.exe programs that certain programs require.
My favorite example of this is the ATI Control panel...
It also cleans up all of the uneeded files as you already know.
it uses the autoit commands dirRemove() and fileDelete() to do so, these commands are not different than the DOS commands RD and DEL. and have the same "fit, form and feel" (they are almost identical, in fact they may actually be just a wrapper for them)

I think it is important to note here that as your Disc fills up the MFT space will be de-allocated for use.
The MFT is "reserved" which is totaly different than allocated (or used). if the space is needed it will be relinquished wink The MFT space will be "given back" (all except what is absolutely neccessary) IF it is needed tongue

Helmi is right you need not concern yourself with this, it is not a problem.

Just to be clear DriverPacks BASE will only remove Mass Storage drivers that were added by DriverPacks BASE
and only if you did not make any changes after you integrated DriverPack MassStorage

I hope that helps!

PS other drivers may be removed manually by editing the txtsetup.sif and dosnet.inf
Do this at your own peril wink there is a wealth of useful info at msfn if you need help with that