this problem ONLY occurs when useing HFSlip...

So we know where the problem lies... Awsome!

Thanks for reporting


PS. I am not going to publish in public what the routine is...
I don't want to allow cheating.
If your filesystem is valid it will be detected.
If it is corrupt it will not be used... This is a GOOD thing.

This routine has gone unchanged for three or more years...
HFSlip is corrupting something

perhaps you could narrow it down to a specific hotfix / package and we can work from there??

Hey!

Yeah, I have been following grumpys thread over there... wink
[He has actually become quite familiar with DriverPacks BASE]
The team is not in the loop though,
so thanks a million for the excellent details.
Make that awsome details!

Can I trouble you for one more small bit of info?
We really need the HWID of that device to see what we can do...
(HWID's tool in my signature)

Do you know if the card is detected useing SAD or
useing a DriverPacks slipstreamed install on that machine?

Welcome to DriverPacks and have a great day... 

Jeff

that is the result of the way IE was installed...

We have seen similar issues a couple of times before.
The fix was to change the order in which the IE7 was added with nLite...

I forgot where the posts were, but if memory serves me correctly,
One person did all their other updates first, then ran nLite a second time, and added IE last and alone.
The other one just changed the order of the updates in the nLite list...

In the past this has been attributed to nLite
(IE if you run DriverPacks on your source without nLite you won't have an issue either)
It seems it is the combo of the two that on rare occasions will spit out a file.
This issue WILL NOT occur if IE7 is not slip-streamed...
This issue will probably not occur again if you change the load order in nLite... big_smile

I hope that helps and please report back with any additional info or results
We would love to hear from you... especially with any good clues or your solution.

Awesome first post - excellent details and version info - big_smile

Welcome to DriverPacks and have a great day!

no there is not a simple fix...
the detection program (code/module) was written by signet.
the code is quite involved and multi-tiered.
it checks different files based on OS an SP levels ect...
It is likely that it is unable to determint the SP level becuase the slipstream was in some way corrupted.
the detection algorithim Siginet wrote is rock solid...
if your OS is reported as "why does this not have a value"
My guess would be you have a corrupt copy of the OS -
Start over with a clean copy and try again... this time dont corrupt it. wink

2gig of ram is not enough to run vista... get at least another 2 gig.. or downgrade to xp

2,481

(18 replies, posted in Other)

That's what i meant to say... big_smile    Thanks KA!


----

PS my frustration lies in him not finding out what the finisher does without me typing it out... again.
IT'S IN the FAQ forum for Pete's sake! how hard is that to find... hmm
- the finisher is the core of DriverPacks
   Bâshrat the Sneaky wrote  (in that FAQ forum post you did not find) http://forum.driverpacks.net/viewtopic.php?id=364

DriverPacks Finisher: this program handles all exceptions (mainly control panels, but it also fixes some drivers that would always get installed incorrectly), KTD and the cleanup.

there are better descriptions but i am not going to spoon feed you. (any more)
you need to be able to find what is already stickied / a FAQ or in the tutorials, and otherwise well documented, on your own.
DriverPacks has always had a low tolerance for noob like behavior

I have already given you the answer (you need to use the finisher to succeed with the DriverPacks) 
If you continue to chose not to believe me then I can't, and won't try, to help you...
the finisher is how we fix many of the reported issues we get. without it many drivers will not install properly.

and now that you have forced me to explain YET AGAIN what the finisher does... Now I'm annoyed.

2,482

(18 replies, posted in Other)

dpinst is not localized...
you are not using the SAD's DP_Inst_tool because if you did you would find it is setup for multilingual.

Finisher is required (please search the forum)
I am not going to explain this again here in this thread...
it has been explained 1000 times...
several hundred by me... use search.

select DriverPacks during install is already done and has a GUI...
http://forum.driverpacks.net/viewtopic.php?id=2936
- I am really starting to get annoyed that you will not use the search feature of our forum.
- I am one step away from closing this thread...
start reading the existing material that is already posted here or i will close this thread.

SAD m2 only uses 350 meg for the main packs... not 2 gig or even 600 meg...

add these two lines in presetup.cmd and your done...

SET TAGFILE=\OEM
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET CDDRIVE=%%i:& GOTO DPsFound
:DPsFound

 COPY /Y %CDDRIVE%\OEM\*.* %SystemDrive%\OEM\
 SET CDDRIVE=%SystemDrive%

you don't need to make it any harder than that...
KISS method (Keep It Simple Stupid method)
If you insist on renaming the folder, you can do that from guirunonce or runonceex (before or after the finisher)

optionally include the - "[Add-on] Select desired DriverPacks during M2 install or after install" - I linked to above

You must be running this on a 386 machine if it is taking an hour...
it takes about 10 min for me (with all the main packs) on a slow P4 with an IDE HDD. (no KTD)
If it is taking an hour you have horribly screwed something up...

Yes you're right I can see that SAD is NOT the same as your tool.
- SAD is much better, and so is the pack selection GUI.

Perhaps you should try that AND using the search feature before you post again.

PS I am not a Kid as you refered to me above...
I have been involved with computers since 1968...
My kids are probably older than you are wink

Mess storage... that must be a pack i haven't tried yet LOL

2,484

(18 replies, posted in Other)

no you must use the finisher to succeed...

you must not use the KTD function as this is what takes forever...

I did not release the KTD function... that was done before i was here...

I wrote SAD and it is the replacement for KTD wink ..

in order for you to get what you were trying to do,
just copy the OEM folder to the HDD... simple...
then run DP_Inst_Tool.cmd when you add new hardware....
does the same thing you were trying to do
and it uses the finisher, which is critical to installing many drivers successfully big_smile

Yes i belive you have hit on something that must be done
I am REALLY tired of wasting my breath telling people not to use KTD
I should jsut eliminate it.
That would certainly solve the problem for all the people who refuse to read the many posts about it in the forums.

Normaly i am reluctant to remove existing features from base but...
in this case i am running out of patience arguing the point with people who don't even know what the finisher does.

2,485

(9 replies, posted in DriverPack Sound)

old creative drivers mght be included with windows...

strange r3 was extracted... but not installed... wonder why ... answer is in api log

G\I1 and G\I2 were not extracted but should have been... strange...

which packs did you use Ian? i looked at the official releases mr s lokked at teh nightlies

2,487

(18 replies, posted in Other)

no... I meant no offense.  the thanks for playing was a genuine thank you.

and Yes I/We do not have time to troubleshoot / evaluate code that duplicates what we already provide...
I doubt i would even have the time if it was something we did not already provide.

I was put off by the fact that someone who does not help us wants us to help them...
You want help from us then you need to help us. 
When a user posts an issue about DriverPacks that helps everyone.

When you just stop by and say
"hey guys I did my own version of what you do and it is not complete will you look at it."
it's not complete because it doesn't use the finisher
I assume he did not use the finisher because he does not understand it.
his problem was the KTD not the finisher...
yet he was unable to arrive at that answer on his own...

He created a problem by useing KTD which we have been saying for years is a dead feature and was replaced by SAD.
He Should have asked for help before he started... not after he invested a bunch of time in duplicating existing work.
this indicates to me he does not do good research before or during going off an a tangent. this strains my patience.
Hey if you want to do somthing as a learning tool fine... but we don't need or want to evaluate it.
that is why i tried to keep my answer short...
I did not want to seem terse, which is something I do fall into easily without meaning to.

His post would have been better recieved had he asked for help first, before he spent days of his time reinventing the wheel. wink

He said his initial problem was the finisher took so long to complete...
that issue he created himself by enableing KTD... had he simply disabled KTD his problem would have been solved wink

it could be that the drivers did not get extracted too...
what folders are they in, do you know off the top of your head mr_s?

nm i found them in i1 i2 and i3
and sound r2

Ian can you verify that the folders did get extracted (since the finisher doesn't run you could just look)...

2,489

(18 replies, posted in Other)

Um... what you have done is already a DriverPacks BASE feature...

we call it SAD...

but thanks for playing

2,490

(14 replies, posted in DriverPack Mass Storage)

sata mode = sata mode , it shows 4 sata channels, when i chose sata mode = disable , it shows 2 channels.why is that ?

Because IDE only supports two devices per controller.

It would seem that your MB does not support AHCI mode... Contact them for further support.
We support Drivers, We don't support specific hardware. If you need configuration info about your MB the best source for that is the manufacturer, not us. althoug we would be interested in hearing if AHCI mode is truelyu not suported for your MB...

The ICH8 chipset has been supported by DriverPacks for years... i don't think drivers are your issue, i think the MB settings are not correct, again please contact foxxcon for support of your MB. I belive once you have selected teh best setting available to you then the DriverPacks will find your HDD.

2,491

(41 replies, posted in Universal Imaging)

LOL ... yeah, wifes are good for that wink

Um this thread is over a year old... and no longer relevant...

very helpful

I replied you should be able to use whatever you like to attach an email to me now! big_smile

Ohhh... for me it shows the email... i guess cause im an admin...

send me an email without an atachment through the forum and i will respond to it then you will have my address!

wink

I get enough spam already with out posting my email on a forum that is googled daily wink

http://AdaptivePC.com/Email.jpg

RIGHT click on it and select properties...

click on "E-mail" (to the left of this text...) It will bring up your E-mail client, with my address.

or you could right click on it and select properties and simply read it wink

MOre preciesly the forum does not have email... just my address linked right under the avitar

it's in my profile. A link is under my name, to the left of this post wink

Why do you laugh?

SAD can be local on a machine just like KTD,
Plus it does not use makePNF, (no driver signing issues as a result)
plus the DPInst.exe and DriverPacks Finisher are both there if needed.
Plus it takes half the space on the HDD.

to me that is superior

here skim this topic... http://forum.driverpacks.net/viewtopic. … 065#p30065
(this topic is in this forum, it's about 8 posts down from this one... but this title is MUCH better wink)

especialy note these two posts...

post 8 http://forum.driverpacks.net/viewtopic. … 710#p29710

post 12 http://forum.driverpacks.net/viewtopic. … 755#p29755

PS I did not put the two things together
Not until you specificaly told me that it does work in 8.12.3 but it does not in 8.12.4.
That was what triggered my memory, and I went looking for that post.

Summary
I think I compiled 8.12.4 with a newer version of SCITE / AutoIt.
So although I made no changes to the code, the newer AutoIt may have altered the output of our unchanged source.
I have seen / been bitten by this before. DriverPacks uses an SVN server and all changes are logged and the sources are bit for bit identical.

Now that more than one person has reported it (with enough of the crucial details), I agree that I really need to look at what changed with AutoIt. Sometimes they change the list of included modules or perhaps see if there is a patch.

Look's like i have homework
- But so do you... SAD is the replacement for KTD