Search options (Page 47 of 213)

Thank you I will take another look at it and see what i can do...

nope 5.29 is latest nightly

driverpacks is not compatable with a winnt32 setup... only Disc based setup is supported...

DriverPacks is designed to be called from setup.exe ... with that install method you are using winnt32.exe instead...

In order for it to work you would have to write a dummy winnt32 exceutable that would call presetup.cmd then exits with a call returning processing to  winnt32.exe %0

the logs? \DriverPacks BASE folder\LogFiles

search txtsetup.sif for "3wareDrv"

have a great day

Please verify the MD5 checksums of your DriverPacks... they are available on the download pages of the main site

If you don't want to receive offensive posts then don't write them and show proper respect. Simple...

Follow directions. answer simple questions. ask nicely. We have a saying here "Mess with the bull and get the horns"

Thank you... Much better!

"IF there is a problem with our code, we want to fix it for everyone."
... Agreed

It wouldn't hurt you to get the most recent version of DriverPacks BASE... there have been quite a few updates since 9.02

In fact 8.12.5 is newer than 9.02.x  (8.12.5 was released 9.06) and version 10.x is in RC testing ATM

If you are unable to describe how to cause this error then there is no way for us to fix it...

end of story.

No we don't believe we are the only ones who can create a fake setup...
However we only support OURS... Feel free to write your own finisher too

Either tell us how to reproduce this error or stop wasting our time...

Yes it is strange... and I still believe it is due to something he has done...

further evidenced by this

2010-05-24 23:41:33 : <INIT> 4. USB devices

USB\ROOT_HUB\4&11781826&0                                   : 
USB\ROOT_HUB\4&1D1F98AB&0                                   : 
USB\ROOT_HUB\4&219F0D9C&0                                   : 
USB\ROOT_HUB\4&3893AD85&0                                   : 
USB\ROOT_HUB\4&3A652E88&0                                   : 
USB\ROOT_HUB20\4&1B9E9A55&0                                 : 
USB\ROOT_HUB20\4&2BD40AA&0                                  : 
USB\VID_04F2&PID_B159\SN0001                                : 
USB\VID_04F2&PID_B159&MI_00\6&13822F80&0&0000               : 
USB-USB\VID_1005&PID_B113\B4A518000052                          : 
USBSTOR\CDROM&VEN_FLASH&PROD_BY_YIKXX&REV_1.00\B4A518000052&0: Flash by YikxX USB Device
USBSTOR\DISK&VEN_FLASH&PROD_BY_YIKXX&REV_1.00\B4A518000052&1: Flash by YikxX USB Device
12 matching device(s) found.

Pay particular attention to the last two HWIDs.

I have enough evidence to believe at this point he has Blown Up more than an INF file or two...
VEN_FLASH&PROD_BY_YIKXX&REV_1.00\B4A518000052&0
Is definitely not a valid HWID...
That looks a lot like he corrupted one or more of his devices BIOS...
All it would take is one invalid HWID to cause the program to exit the loop that creates the array of HWIDs.

I am sure that this is the result of a faulty modification he has made to an included driver INF...
without YikXx telling us truthfully and completely what he has done I can't identify his error.
However i have seen enough evidence to believe he screwed the pooch on this
No pack ever produced by us or Greg or SamLab or anyone else has ever had this issue.
Hundreds if not thousands of packs... Yet only his packs have an issue??? (GIGO)

I see no evidence of a finisher bug... at all.
I am not able to create or repeat his issue... Can you?

Since this error can not be demonstrated, I can not offer a solution. (I can't tackle a ghost.)
I am tired of asking him to provide details... Perhaps his reluctance is related to some association with unsavory activities.
He just needs to cough up the pack that causes this issue so I can show him his mistake.
The burden of proof is still on YikXx.

Until I can personally reproduce this error, it is definitely NOT a BUG. Even then it's only a BUG if its not GIGO.

The answer to this question is still "no".

I think what I should do is add some code to the finisher so that it will exit with a critical error if an invalid HWID is found, that would absolutely place the blame where it belongs ! But I don't see why i should go out of my way for someone who shows me no respect.

IE

Who said you found a BUG??? Not me... not mr_smartepants. I find this statement very disrespectful.
You're going to wait??? you haven't even demonstrated you have found a bug yet...
You should not be waiting. You need to get to work proving you have found a bug. At least if you want us to be able to help.

I NEVER said we had a BUG I said that "I wish you luck in proving you found a bug" You still have not yet proved you have found a bug. And I don't think you ever will... But 'Good Luck' trying. One person in ten million has ever found a bug in BASE. The odds of your success are almost zero. BUT... IF you actually DO find a BUG... THEN (and only then) I will tell you when you have found a BUG and then I will ask you to create a bug report at the bugtracker. THEN I will be glad to fix it. We are no where near that yet... First i need to reproduce the bug on one of the many machines on my workbench. 

Again... First you have to find a BUG... Right now all I see is user error. (GIGO)

I am convinced that this is a GIGO error (Garbage In Garbage Out error). You are dumping garbage into the finisher so you are getting garbage out... PLEASE PLEASE PLEASE feel free to prove me wrong... And I wish you Good Luck with that task! (you are going to need it). The odds I am wrong are quite slim, probably one in a million. If it happens it happens, and I will admit it. It certainly would not be the first time I was wrong and certainly won't be the last. Since It happens so rarely I can deal with it with a big smile and take my lumps like a man .

I suggest you do a process of elimination...

does your graphics pack have this error if it is the only one slipstreamed?
(I am going to bet the answer to this question is no)
If the answer to that question is yes... What change do you make that causes it to blow up?

Are you saving your files as UNI or ANSI?

I think the graphics pack issue is caused by another pack... So... What other pack used with your graphics pack blows it up. Is it the same one that has that goofy USB driver in it?

I assure you the mistake is yours. Keep Simplifying your equation until you find your issue.

At this point I am very curious to see one of your DPs_BASE.log files... Hmmm...

Now were getting somewhere!

Thanks for helping us to help you and making DriverPacks better for everyone!

@mr_smartepants... I seem to remember it took quite a while to eventually find and squash that bug to... Sorry again.

@YikxX When we're wrong we admit it! Just be aware that it doesn't happen very often. It has taken mr_s several years to score less than a handful of bugs and he is here every day . With that in mind... Please accept my best wishes for your success followed by my apology .

Jeff

PS Bad English is no problem! Just do your best. If it does not translate well then I will just ask you to try again. Usually I can understand what you are attemting to say just fine. Don't worry about it at all. The best thing you can do is to tell me as much as you can. I don't care about how well written it is. It is only frustrating when I am not given the whole story. Tell us as much as you know and don't worry about if it is good english. It's much better to go through a bunch of bad English than to not get the whole picture.

Let's see the entire DPsFnshr.log please - unedited
Please also include the output of the HWIDs tool linked in my signature.

(this may require you to split the file into multiple posts or for you to provide a link to it on rapid share, or a similar site)
Please use code tags. you can edit your post to see how that is done.

Thanks for following up with better details. In order to find and fix a bug it is necessary to be able to repeat it. From Rule #0:

Clearly the answer to that is, NO (No terse responses or LOL's when you follow the rules / guidelines... fair enough?)

Help us to help you... It's called "read BEFORE you post" for a reason. (AKA "Rule #0")

I still don't have enough info to help you. Although it seems (from the limited info you provided) as though a HWID was not matched I am still not in a position to be able to cause the issue to happen here on my bench in my presence. Then debug the input, process, and output. Then identify the problem and provide a fix / workaround or expose user error (by user error I mean a mistake in the OEM INF or your packs INI or the packs layout or whatever - AKA GIGO)

In Example (IE) since you updated the pack with a driver, then please link us to that driver... If you edited the INF, please also include a copy of the entire INF that includes your edits. Same thing for the packs INI, Please provide the section(s) you edited - Even better if you provide the entire INI file. - We need to be able to reproduce the error by testing it for ourselves. - (The very best option is to provide your custom DriverPack to us for review)

Do you now understand what I need from you... and why?
Do you understand now why what you did was frustrating for me / us?
I realize that your primary language is Russian.
Just to be clear we were not being mean or hateful. We were not ignoring you or putting you off.
Just giving you a deliberate shove in the right direction.
I really don't care about grammar or vocabulary. Many of our users do not speak English as their primary language. I would rather struggle through bad English than to not have enough info to go on. Capice? 

Regards
Jeff