26

(3 replies, posted in Other)

Bâshrat the Sneaky wrote:

Why would you want that? It's already dated, just not exactly. For instance: DriverPack MassStorage 6.08 is released in the 8th month of 2006. Isn't that sufficient?

Sorry, I didn't know it was a special code to know date big_smile !!!

27

(3 replies, posted in Other)

Hello the creator,

May I ask you a little thing ? Okay, thanks, let's go  ;D
Displaying Version of a pack on the home page of each one is of course very important, buut would it be possible to add the DATE of release ?
Thnaks a lot

Regards from Cote d'Azur (South of France) .....
http://img162.imageshack.us/img162/4159/palmiermi8.gif

Bâshrat the Sneaky wrote:

I meant DriverPack Sound B 6.08 wink

Ahhhh - SO I'm not as fool as I thought big_smile
When will it be available ?

Bâshrat the Sneaky wrote:

It's fixed in 6.08: no one has reported this bug again!

I use 6.08 both for CHIPSET & CPU ! Maybe bad manip from me !.......

Bâshrat the Sneaky wrote:

I've submitted it to the bugtracker now: BUG #84.

I think I've found the solution, but still have to test it.

Maybe this new snapshot can help you :

http://img141.imageshack.us/img141/7745/driverpackerrorwb8.gif

Whatever, thanks for all your great work...

I have the same problem (see picture below), but I've found a quick and simple solution.
At the end of Windows installation, I simply use this script :

:: ============================================================================
RD /S /Q %SystemDrive%\D
DEL /F /Q %SystemDrive%\CloseDSP.exe
DEL /F /Q %SystemDrive%\hideMakePNF.exe
DEL /F /Q %SystemDrive%\robocopy.exe
DEL /F /Q %SystemDrive%\WatchDSP.exe
IF EXIST %SystemDrive%\KTDpaths.cmd DEL /F /Q %SystemDrive%\KTDpaths.cmd
IF EXIST %SystemDrive%\KTDpatterns.cmd DEL /F /Q %SystemDrive%\KTDpatterns.cmd
DEL /F /Q %SystemDrive%\addUsepmtimer.exe
DEL /F /Q %SystemDrive%\agrep.exe
DEL /F /Q %SystemDrive%\devcon.exe
DEL /F /Q %SystemDrive%\fnsh_log.cmd
DEL /F /Q %SystemDrive%\DPs_fnsh.cmd
DEL /F /Q %SystemDrive%\DPS_fnsh.log
:: ============================================================================

http://img481.imageshack.us/img481/9850/driverpack9nt.gif

chertoianov wrote:

May be in the next release. I think it is so close!

So, good news big_smile !!

And about the name of this topic:

SOLVED: Critical error while slipstreaming using method 1

What is ... SOLVED ???

I have found the bug :


Just compare the folder displayed on the error message :

http://xpcoccinelle.fredisland.net/images/temp/Critical3.gif


... with the tree: two "D" folders, instead of ONE ! Is that normal ?


http://xpcoccinelle.fredisland.net/images/temp/Critical2.gif

Bâshrat the Sneaky wrote:

My solely possible explanation:

Blame Windows smile

wink tongue

Really no clue...

Hello ther',

I have the same problem, only with chipset drivers, no matter the length of the path :

http://xpcoccinelle.fredisland.net/images/temp/Critical.gif

So I took the resolution to ... not include theses drivers ! The other ones work...

Whatever, thanks to Bâshrat the Sneaky for his really good work ...

Fred, from France