1 Reply by Coccinelle

(13 replies, posted in Feature Requests)

Bâshrat the Sneaky wrote:

Set in your DPsFnshr.ini:

[Settings]
splashScreen = false;

This should be better documented, I know, but documentation will be closely integrated in the next website (on which is being worked, obviously wink smile).

It'me, agaaaaaaaaiiiiiiiiiiiiiiinnn !

No more splash screen. But here's chapter two : how to remove the new one :

http://img169.imageshack.us/img169/2964/driverpacksplashscreenlh0.gif

My DPsFnshr.ini:

[Settings]
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! (may NOT contain any spaced, if it does, all exceptions must be adapted to be compatible!)
DPsRoot	= "%SystemDrive%"
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU!
KTD = ""
; system variables supported (see remarks for a list) one location cannot be used as
; KTDlocation: the root directory specified in[Settings]\DPsRoot
KTDlocation	= "%SystemRoot%\DriverPacks"
; system variables supported (see remarks for a list)
logLocation = "%SystemRoot%"
; enables/disables debug mode (enabled by default)
debug = "true"
splashScreen = false;

Do we have to set splashScreen = 0 instead of splashScreen = false  ?

Go to forum: Feature Requests

2 Reply by Coccinelle

(13 replies, posted in Feature Requests)

Bâshrat the Sneaky wrote:

Set in your DPsFnshr.ini:

[Settings]
splashScreen = false;

This should be better documented, I know, but documentation will be closely integrated in the next website (on which is being worked, obviously wink smile).

Merci m'sieur !

Go to forum: Feature Requests

3 Topic by Coccinelle

(13 replies, posted in Feature Requests)

Four month ago, in this [CLOSED but NOT SOLVED] topic : http://forum.driverpacks.net/viewtopic. … 4478#p4478,
our friend Bâshrat the Sneaky said :

Bâshrat the Sneaky wrote:

Probably I'll make it a manual option in the next version to disable it - so those who feel so annoyed when they see it, can disable it. In the future, you'll be able to configure it from within the DriverPacks BASE, but not just yet.

But, in DP 7.01.2, there's no such option. Or maybe I didn'ts see it. I'm really sorry to open a new topic about that, but really ... would it be possible to have this option in the next version of DP ?

Thanks for all your great work ....

Fred

http://img173.imageshack.us/img173/4663/coccireadyct1.jpg

Go to forum: Feature Requests

4 Reply by Coccinelle

(102 replies, posted in DriverPack Mass Storage)

Coccinelle wrote:
Bâshrat the Sneaky wrote:

You may have to update to the last BIOS version that is provided by Silicon Image!

ruudboek wrote:

Yes, bashrat is correct, regrettably a silicon driver from a specific version will only function properly in combination with a specific version of the controller-BIOS.

Since most people will probably not update their controller's BIOS frequently, it will most likely be necessary to first update the controller's BIOS prior to using the driverpack masstorage on systems with silicon controllers.
Maybe we should make a FAQ for that.

Currently the latest driver for sil3112r (1.0.56.1) is included in the masstorage driverpack. The matching biosversion for add-in cards (not integrated silicon controllers) is 4.3.79.

After BIOS upgrade, could you please post your results in this topic?

Thanks for all your support. As soon as the new test is realized, I tell you the result ... CU soon on line :-)

Everything's okay ! :-)

Go to forum: DriverPack Mass Storage

5 Reply by Coccinelle

(102 replies, posted in DriverPack Mass Storage)

Bâshrat the Sneaky wrote:

You may have to update to the last BIOS version that is provided by Silicon Image!

ruudboek wrote:

Yes, bashrat is correct, regrettably a silicon driver from a specific version will only function properly in combination with a specific version of the controller-BIOS.

Since most people will probably not update their controller's BIOS frequently, it will most likely be necessary to first update the controller's BIOS prior to using the driverpack masstorage on systems with silicon controllers.
Maybe we should make a FAQ for that.

Currently the latest driver for sil3112r (1.0.56.1) is included in the masstorage driverpack. The matching biosversion for add-in cards (not integrated silicon controllers) is 4.3.79.

After BIOS upgrade, could you please post your results in this topic?

Thanks for all your support. As soon as the new test is realized, I tell you the result ... CU soon on line :-)

Go to forum: DriverPack Mass Storage

6 Reply by Coccinelle

(102 replies, posted in DriverPack Mass Storage)

ruudboek wrote:
Protonus wrote:

I would love to test this!  Can you shoot me a link for the files I need, and tell me how to update the XP distrib I have with it?  I have a 3112r as noted.

@protonus,

The sil problems should be fixed now with the new publicly available driverpack base + driverpack masstorage.
Could you please test and post your results in this topic?

DiverPackBase (7.01.2) + MassStorage (701) + Asus A7N8X deluxe 2 + silicone image 3112r = BSOD !!!!

Test realized today : BSOD again and again and again .........  ! Is there any solution ? Is there someone on earth able to fix it ?

Go to forum: DriverPack Mass Storage

7 Reply by Coccinelle

(23 replies, posted in Feedback and Support - DriverPacks Base)

rayw69 wrote:

I posted this in another thread:

"By default, the driver pack does not have the JMicron controllers set up correctly. You need to edit the txtsetup.sif with the CC_0104 and CC_0106 suffixes, and also add CC_0101 to the exclusion list of both the jraid and jahci INF files."

Could you post a global topic to explain in details what exactly you modify in txtsetup.sif to use JMicron controler ? Thanks for all
Best regards from France...

Go to forum: Feedback and Support - DriverPacks Base

8 Reply by Coccinelle

(25 replies, posted in Feedback and Support - DriverPacks Base)

jtdoom wrote:
hamza wrote:

It seems to be a combination of this driverpack with Ryan's update pack.

I have it working with a dutch SP2 release

First make a new copy of your windows cd

then first slipstream the driver pack, after this slipstream de Ryan's update pack. After that all works fine (but...still that desktop.ini issue smile )

Hi
erm,  better first do RVM with Meulc's oktober pack, and after that do DriverPacks-Base streaming.

what causes the desktop ini thing when one does KTD is still a mystery.
I am ready to run a test with KTD with the pattern one finds in the FAQ section.

May I think Ryan's update pack is NOT concerned, because I don't use Ryan's pack (it's in english, and I only use french Windows XP).
So, guilty is nLite OR DriverBase....

I'm going to make some more tests ....

Fred

Go to forum: Feedback and Support - DriverPacks Base

9 Reply by Coccinelle

(25 replies, posted in Feedback and Support - DriverPacks Base)

Hello,

Just to tell you I have the same problem: newdev.dll is missing ! Never had this before, with same base & mass storage files versions. ... But before what ??? I have added some missing KB, slipstreamed with nLite. Maybe one of them is wrong ? I don't know how to solve that .....

Go to forum: Feedback and Support - DriverPacks Base

10 Reply by Coccinelle

(78 replies, posted in Feedback and Support - DriverPacks Base)

Bâshrat the Sneaky wrote:

@felipegeek: Just extract the DriverPacks you use to %systemdrive%, copy DPsFsnhr.ini there too and also extract DPsFnshr.7z to %systemdrive%. Now execute DPsFnshr.exe and that should work too.

Bâshrat, what does EXACTLY do DPsFnshr.exe at the end of an installation ?

Let's take a simple example: MassStorage + Mono system + Method 1 (with Winnt.sif) + GUIRunOnce + NOKTD + No QUickStream

Does it ONLY delete files like theses :

DELETE \D Folder
DELETE %SystemDrive%\CloseDSP.exe
DELETE %SystemDrive%\hideMakePNF.exe
DELETE %SystemDrive%\robocopy.exe
DELETE %SystemDrive%\WatchDSP.exe
DELETE %SystemDrive%\KTDpaths.cmd
DELETE %SystemDrive%\KTDpatterns.cmd
DELETE %SystemDrive%\addUsepmtimer.exe
DELETE %SystemDrive%\agrep.exe
DELETE %SystemDrive%\devcon.exe
DELETE %SystemDrive%\fnsh_log.cmd
DELETE %SystemDrive%\DPsFnshr.exe
DELETE %SystemDrive%\DPsFnshr.log

And then bye bye ?

Because if it only does that maybe a simple batch script could solde the error message "Could not delete element from array" instead of using DPsFnshr.exe , waiting for a day the solution is found....

It's just a suggestion .....

Go to forum: Feedback and Support - DriverPacks Base

11 Reply by Coccinelle

(3 replies, posted in Feedback and Support - DriverPacks Base)

Bâshrat the Sneaky wrote:

As I said before, it's NOT a nag screen, it's just a small splash screen that only remains active for the duration of the DriverPacks Finisher. It shows the current action.

I know it's not beautiful... I wish I had your graphics skills wink Probably I'll make it a manual option in the next version to disable it - so those who feel so annoyed when they see it, can disable it. In the future, you'll be able to configure it from within the DriverPack Sound B, but not just yet.

Yes I know it's not "nag", but I didn't find another word with my online dictionnary smile !
So I'm waiting for you to remove the splash (yes, better than "nag") screen. I will be patient ....
Thanks once more ...

Go to forum: Feedback and Support - DriverPacks Base

12 Topic by Coccinelle

(3 replies, posted in Feedback and Support - DriverPacks Base)

Hello World,

As I continue to update my Windows unattend (next issue in the few months, see work in progress below)), I try to TOTALLY remove DOS windows or any message/windows which could stare at the installation. It must be clean AND beautiful. So, when on windows desktop I see such window ...

http://img246.imageshack.us/img246/2930/dpsfnshrxt9.gif

... I'm in the mood for crying !

Bâshrat, please my boy, REMOVE THAT, it's ugly and you don't need it to finish installation ... And as I said in a previous topic, you are THE ONE which provides such great tool to slipstream drivers, so you don't need to say "Hello, I'm here" at screen !

However, a solution would be to not compress exec DPsFnshr.exe in order to include our own logo if we want (for example with Reshacker) instead of yours !

Well, I'm french and my english is not as good as I would, but I hope to be understood !

Kisses from France ....

http://img246.imageshack.us/img246/8773/xpcoccinellemetamorphose01sg7.jpghttp://img246.imageshack.us/img246/5679/coccinelleanimtransparentnj0.gif

Go to forum: Feedback and Support - DriverPacks Base

13 Reply by Coccinelle

(19 replies, posted in Feedback and Support - DriverPacks Base)

muiz3 wrote:

Whow awesome prog...where can we find it?

It's part of the Windows XP Coccinelle... It't not really a stand alone program...

Go to forum: Feedback and Support - DriverPacks Base

14 Reply by Coccinelle

(19 replies, posted in Feedback and Support - DriverPacks Base)

Verdict: everything works fine now, except a little error message saying it can't delete element from array, while the H-O-R-R-I-B-L-E SNAG SCREEN is staring at my beautiful desktop !? Why such nag screen ? You do not need ad, you are the one to give us such wonderful work, you have no competition on the scene ! Please, remove it ....

Her's the final part of final DPsFnshr.log

2006-09-23 17:35:48 : <INIT> Logging of HWIDs complete.
2006-09-23 17:35:48 : <CRIT> Could not delete element from array!
2006-09-23 17:35:58 : <CLNP> Deleted the DriverPacks, which were located in 'C:\D'.
2006-09-23 17:35:58 : <CLNP> Deleted 'C:\DPsFnshr.ini'!
2006-09-23 17:35:58 : <CLNP> Deleted 'C:\devcon.exe'!
2006-09-23 17:35:58 : <CLNP> Deleted 'C:\makePNF.exe'!
2006-09-23 17:35:58 : <CLNP> Deleted 'C:\addUsepmtimer.exe'!
2006-09-23 17:35:58 : <CLNP> Deleted 'C:\ATICCC.ins'!
2006-09-23 17:35:58 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2006-09-23 17:35:58 : Program terminated.

Go to forum: Feedback and Support - DriverPacks Base

15 Reply by Coccinelle

(19 replies, posted in Feedback and Support - DriverPacks Base)

Bâshrat the Sneaky wrote:

You're misunderstanding the problem. The file fnsh_log.cmd is no longer used since version 6.08 of the DriverPack Sound B! It's only used in versions before that. That's why I've been asking where you've referenced it. And that's why I've now suggested to rebuild your uwxpcd as the easier way to fix this problem.

It's really crazy .... My unattend is made from scratch with a XP Pro SP2 version, my DrivePack Base and drivers are updated, and I never use such file like fnsh_log.cmd . I don't understand ...... OOOHHHHHHHHHHHHHHHH  !!!!!!!!  ******** FLASH ****** THAT'S IT !!!!!!!!!  I'VE SUDDENLY FOUND THE SOLUTION WHILE WRITING THIS MESSAGE !!!!!

AFTER MAKING THE ISO FILE, I USE A SPECIAL PATCHER TO INCLUDE SERIAL LICENSE DIRECTLY IN ISO IMAGE.
AND THIS PATCHER USES THE OLD WINNT.SIF !!! sh*t !!!!!!!!!! I'M STUPID !!!!!!!!!!! But your message gave me the clue .......

Here's is the line in the old winnt.sif :

[GUIRunOnce]
  command9="%SystemDrive%\fnsh_log.cmd"

The patcher :

http://img238.imageshack.us/img238/6671/coccipatchermx3.jpg


And the photo of the culpable smile :

http://img65.imageshack.us/img65/7572/gogol01ha3.jpg

AHHHHHHHHHHHHHHHHHHH -------------- XP IS INSTALLING NOW ----- I WILL POST A MESSAGE IN A FEW MINUTES TO CONFIRM IT WORKS NO !

Go to forum: Feedback and Support - DriverPacks Base

16 Reply by Coccinelle

(19 replies, posted in Feedback and Support - DriverPacks Base)

Bâshrat the Sneaky wrote:

1) It's not referenced in the GUIRunOnce section of the winnt.sif file.
2) You're absolutely positive that you're not using RunOnceEx.
3) You're not using anything such as WPI or XPlode to install applications or whatever other tasks.
4) It's not referenced in the batch file you're using for cleanup.

BUT it has to be referenced SOMEWHERE. You must be overseeing something. The easiest solution in this case (since you cannot find the reference), is to rebuild your installation CD/DVD. Then the problem should vanish automatically.

Here's how the installation works:
- Installation of Windows
- Editing the name of the administrator and the others users (the different blues screens)
- Installation of my different applications
- Just before Windows desktop appears, a key is created to launch another program : REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run /V 1 /D "%APP%\XPSP2+_03_Finalise.exe" /f
- Windows desktop appears
- The new program is launched
- A new key is created to delete all temp files after reboot: REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce /V "2" /T REG_EXPAND_SZ /D "%windir%\system32\XPSP2+_Nettoie.cmd" /f
- Reboot
- During boot, message error from DriverPack : fnsh_log.cmd NOT FOUND

So, it seems to have a conflict between MY Run/RunOnce and yours ....

Question: May I use:

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run /V 999 /D "%APP%\XPSP2+_03_Finalise.exe" /f
instead of
REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run /V 1 /D "%APP%\XPSP2+_03_Finalise.exe" /f

to avoid conflict ?

Go to forum: Feedback and Support - DriverPacks Base

17 Reply by Coccinelle

(19 replies, posted in Feedback and Support - DriverPacks Base)

Bâshrat the Sneaky wrote:

Is the fnsh_log.cmd referenced insice your batch file (XPSP2+_Nettoie.cmd)?

Absolutely not, I didn't know it existed before the error message !
I don't know if it can help you, but I just noticed after full installation of Windows that DPsFnshr.exe works fine (it deletes all work files, including 'D' folder), except a little error message I didn't have the time to note.... Could you tell me what is the exact registry key which is created to perform the files deleting after next reboot ?

Go to forum: Feedback and Support - DriverPacks Base

18 Reply by Coccinelle

(19 replies, posted in Feedback and Support - DriverPacks Base)

Bâshrat the Sneaky wrote:

Grrr unbelievable! Are you also using RunOnceEx for something? Or anything else to install applications, apply registry tweaks... ?

Ooooooh YES !!!!
In the batch file used just before my last reboot of Windows, I use the line:

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce /V "2" /T REG_EXPAND_SZ /D "%windir%\system32\XPSP2+_Nettoie.cmd" /f

So it seems it tries - and successes (!) - to replace something you put in "2" .... too !

Go to forum: Feedback and Support - DriverPacks Base

19 Reply by Coccinelle

(19 replies, posted in Feedback and Support - DriverPacks Base)

Bâshrat the Sneaky wrote:

Please post your winnt.sif. You've still got an old entry in it, somehow.

Here's my WINNT.SIF, and thanks again for the time you take to solve this trouble :

[Data]
  AutomaticUpdates=0
  MsDosInitiated="0"
  UnattendedInstall="Yes"

;[Display]
;   BitsPerPel=16
;   Xresolution=800
;   YResolution=600

[GuiUnattended]
  OEMSkipRegional=0
  OemSkipWelcome=1
  TimeZone=85
  EncryptedAdminPassword=NO

[IEPopupBlocker]
  BlockPopups=Yes
  FilterLevel=Medium
  ShowInformationBar=No

[PCHealth]
  ER_Display_UI=0
  ER_Enable_Applications=None
  ER_Enable_Kernel_Error=0
  ER_Enable_Reporting=0
  ER_Enable_Windows_Components=0
  ER_Include_MSApps=0
  ER_Include_Shutdown_Errs=0
  RA_AllowFullControl=0
  RA_AllowToGetHelp=0
  RA_AllowUnsolicited=0

[RegionalSettings]
  LanguageGroup=1
  SystemLocale=0000040c
  UserLocale=0000040c
  InputLocale=040c:0000040c

[Shell]
  DefaultStartPanelOff=Yes
  DefaultThemesOff = No
  CustomDefaultThemeFile = "%windir%\Resources\Themes\Luna.theme"

[UserData]
    ProductKey=
    FullName=
    OrgName=
    ComputerName=

[GUIRunOnce]
	command9="%SystemDrive%\DPsFnshr.exe"
	
[Unattended]
  ForceHALDetection = Yes
  FileSystem=*
  OemFilesPath="..\$OEM$"
  OemPreinstall=Yes
OemPnpDriversPath="D\D\M\3\1;D\D\M\3\1\O;D\D\M\3\2;D\D\M\3\3;D\D\M\A\1;D\D\M\A\2;D\D\M\A\3;D\D\M\A\4;D\D\M\A\5;D\D\M\A\6;D\D\M\A\7;D\D\M\A\8;D\D\M\AD\1;D\D\M\AD\2;D\D\M\AD\3;D\D\M\AD\4;D\D\M\AD\5;D\D\M\AD\6;D\D\M\AD\6\C;D\D\M\AD\7;D\D\M\AD\8;D\D\M\AD\9;D\D\M\AD\A;D\D\M\AM;D\D\M\AR;D\D\M\AT;D\D\M\AU\1;D\D\M\AU\2;D\D\M\AU\3;D\D\M\AU\4;D\D\M\AU\5;D\D\M\D;D\D\M\E;D\D\M\H\1;D\D\M\H\1\R;D\D\M\H\2;D\D\M\H\3;D\D\M\H\4;D\D\M\H\5;D\D\M\H\6;D\D\M\H\7;D\D\M\H\8;D\D\M\I\1;D\D\M\I\2;D\D\M\IN\1;D\D\M\IN\1\O;D\D\M\IN\2;;D\D\M\IT;D\D\M\J\1;D\D\M\J\2;D\D\M\L\1;D\D\M\L\2;D\D\M\L\3;D\D\M\L\4;D\D\M\M;D\D\M\N\123;D\D\M\N\4\I;D\D\M\N\4\R;D\D\M\N\4INTEL\I;D\D\M\N\4INTEL\R;D\D\M\N\590SLI\I;D\D\M\N\590SLI\R;D\D\M\N\TM;D\D\M\P\1;D\D\M\P\2;D\D\M\P\2\A;D\D\M\P\3;D\D\M\P\4;D\D\M\P\5;D\D\M\P\6;D\D\M\P\7;D\D\M\P\8;D\D\M\Q\1;D\D\M\Q\2;D\D\M\Q\3;D\D\M\Q\4;D\D\M\S\1;D\D\M\S\2;D\D\M\S\3;D\D\M\S\4;D\D\M\S\5;D\D\M\S\5\A;D\D\M\S\6;D\D\M\S\7;D\D\M\S\8;D\D\M\S\9;D\D\M\S\A;D\D\M\S\B;D\D\M\S\C;D\D\M\SI\1;D\D\M\SI\2;D\D\M\SI\3;D\D\M\V\1;D\D\M\V\2;D\D\M\VM"
  DriverSigningPolicy= Ignore
  NonDriverSigningPolicy= Ignore
  OEMSkipWelcome=1
  OemSkipEula=Yes
  Repartition = No
  TargetPath=\WINDOWS
  UnattendMode=ProvideDefault
  UnattendSwitch=No
  WaitForReboot=Yes
  AutoActivate=No
  CrashDumpSetting=0
  DUDisable=No
  DUStopOnError=No

[Identification]
  JoinWorkgroup=

[WindowsFirewall] 
  Profiles = WindowsFirewall.TurnOffFirewall
 
[WindowsFirewall.TurnOffFirewall]
  Mode = 0

Go to forum: Feedback and Support - DriverPacks Base

20 Reply by Coccinelle

(19 replies, posted in Feedback and Support - DriverPacks Base)

And then, the same message :

http://img456.imageshack.us/img456/160/fnshlogud4.gif



And what is on my root directory after Windows installation :

http://img71.imageshack.us/img71/4891/image2io3.gif

Go to forum: Feedback and Support - DriverPacks Base

21 Reply by Coccinelle

(19 replies, posted in Feedback and Support - DriverPacks Base)

Bâshrat the Sneaky wrote:

That's not your slipstream log. I need the DPs_BASE.log of the time that you actually SLIPSTREAMED the DriverPacks. May I ask you to slipstream again with the exact same settings? (The slipstreamed and edited files will be deleted, the original files will be restored.)

Re-made from scratch :

2006-09-22 18:51:11 : <INIT> DriverPacks BASE 6.08.6 initialized.
2006-09-22 18:51:11 : <INIT> Host environment: WIN_XP Service Pack 2 on X86 CPU.
2006-09-22 18:51:11 : <INIT> Detected settings file "E:\CD_XPSP2+\XPSP2+_PREPARATION\03_Pilotes\DriverPacks\DPs_BASE.ini".
2006-09-22 18:51:11 : <INIT> Windows XP Professionnel -  OEM SP2 detected.
2006-09-22 18:51:11 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2006-09-22 18:51:11 : <INIT> Imported settings from settings file.
2006-09-22 18:51:11 : <INIT> Detected DriverPack MassStorage 6.08!
2006-09-22 18:51:11 : <INIT> Could not detect any 3rd party DriverPacks.
2006-09-22 18:51:11 : <INIT> DriverPacks scanned sucessfully.
2006-09-22 18:51:11 : <INIT> QuickStream Cache directory not found!
2006-09-22 18:51:11 : <GUI>  Initialized GUI.
2006-09-22 18:51:11 : <GUI>  Created a list of all available language files.
2006-09-22 18:51:12 : <GUI>  Set the last used language, French, as the GUI language.
2006-09-22 18:51:26 : <GUI>  Refreshed UpdateChecker with success.
2006-09-22 18:51:27 : <GUI>  Refreshed UpdateChecker with success.
2006-09-22 18:51:42 : <GUI>  Saved settings!
2006-09-22 18:51:42 : <GUI>  Closed GUI.
2006-09-22 18:51:42 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m1.
2006-09-22 18:51:47 : <PREP> Removed all attributes from \I386.
2006-09-22 18:51:47 : <PREP> Generated \I386\winnt.sif file.
2006-09-22 18:51:47 : <PREP> Created a backup of \I386\txtsetup.sif.
2006-09-22 18:51:47 : <PREP> Created a backup of \I386\dosnet.inf.
2006-09-22 18:51:47 : <PREP> Created temporary working directory.
2006-09-22 18:51:52 : <SLIP> Extracted DriverPack MassStorage.
2006-09-22 18:51:52 : <SLIP> Started CAB compressing DriverPack MassStorage (estimated 1.3 minutes).
2006-09-22 18:52:27 : <SLIP> Finished CAB compressing DriverPack MassStorage.
2006-09-22 18:52:32 : <SLIP> Extracted DriverPack MassStorage to a temporary working directory.
2006-09-22 18:52:47 : <SLIP> Slipstreamed DriverPack MassStorage text mode drivers.
2006-09-22 18:52:53 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2006-09-22 18:52:54 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2006-09-22 18:53:40 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2006-09-22 18:53:40 : <SLIP> Extracted bin\DPsFnshr.7z to \$OEM$\$1.
2006-09-22 18:53:40 : <SLIP> Created OemPnpDriversPath entry. The length is 1008, which does not exceed the 4096 characters limit.
2006-09-22 18:53:40 : <SLIP> Added OemPnpDriversPath entry to \I386\winnt.sif.
2006-09-22 18:53:41 : <SLIP> Updated \I386\winnt.sif to support method 1.
2006-09-22 18:53:41 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2006-09-22 18:53:41 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2006-09-22 18:53:41 : <SLIP> Slipstream finished in 1 minutes and 59 seconds.
2006-09-22 18:53:47 : <CLNP> Temporary working directory successfully deleted.
2006-09-22 18:53:47 : Program terminated.

Go to forum: Feedback and Support - DriverPacks Base

22 Reply by Coccinelle

(19 replies, posted in Feedback and Support - DriverPacks Base)

Bâshrat the Sneaky wrote:

You've done something very odd. fnsh_log.cmd was used in version 6.05 and later, but is no longer in use since version 6.08 or later.

Please post your DPs_BASE.log.

2006-09-21 22:47:57 : <INIT> DriverPacks BASE 6.08.6 initialized.
2006-09-21 22:47:57 : <INIT> Host environment: WIN_XP Service Pack 2 on X86 CPU.
2006-09-21 22:47:57 : <INIT> Detected settings file "E:\CD_XPSP2+\XPSP2+_PREPARATION\03_Pilotes\DriverPacks\DPs_BASE.ini".
2006-09-21 22:47:57 : <INIT> Windows XP Professionnel -  OEM SP2 detected.
2006-09-21 22:47:57 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2006-09-21 22:47:57 : <INIT> Imported settings from settings file.
2006-09-21 22:47:57 : <INIT> Detected DriverPack MassStorage 6.08!
2006-09-21 22:47:57 : <INIT> Could not detect any 3rd party DriverPacks.
2006-09-21 22:47:57 : <INIT> DriverPacks scanned sucessfully.
2006-09-21 22:47:57 : <INIT> QuickStream Cache directory not found!
2006-09-21 22:47:57 : <GUI>  Initialized GUI.
2006-09-21 22:47:57 : <GUI>  Created a list of all available language files.
2006-09-21 22:47:57 : <GUI>  Set the last used language, English, as the GUI language.
2006-09-21 22:48:24 : <GUI>  Refreshed UpdateChecker with success.
2006-09-21 22:48:48 : <GUI>  Closed GUI.
2006-09-21 22:48:48 : <GUI>  Saved settings!
2006-09-21 22:48:48 : Program terminated.

Go to forum: Feedback and Support - DriverPacks Base

23 Topic by Coccinelle

(19 replies, posted in Feedback and Support - DriverPacks Base)

Hello World,

http://img399.imageshack.us/img399/9200/fnshlogac1.gif

This message appears after - of course - Windows installation. Translated from french it says: "Windows does not find fnsh_log.cmd ...".

Mehods used:
* installation platfom: disc
* DriverPacks slipstreamed: just one: MassStorage 6.08 with text mode
* method 1 (with winnt.sif)
* GUIRunOnce (but does the same with RunOnce)
* KTD disabled
* QuickStream disabled

Thanks for all your absolutely great work !!

Go to forum: Feedback and Support - DriverPacks Base

24 Reply by Coccinelle

(7 replies, posted in Feedback and Support - DriverPacks Base)

Bâshrat the Sneaky wrote:

The problem with the double D cannot be reproduced. Did you repackage DriverPack MassStorage, Coccinelle?

No, I didn't change/pack/repack anything. I just used DP_MassStorage_wnt5_x86-32_608.7z as download from driverpack.net

Bâshrat the Sneaky wrote:

The 'length exceeded warning'-bug is now fixed.

Thanks you very much for your quick work big_smile !!!

Bâshrat the Sneaky wrote:

P.S.: your beautiful pictures of the environment you live in remember me each time why Belgium is such a miserable country... drooooooling for such a beach! tongue

It's another world, another time... If you plan to go here, let me know, I'll show you the best placeS wink ...

http://xpcoccinelle.fredisland.net/images/temp/coteazur3.jpg
http://xpcoccinelle.fredisland.net/images/temp/coteazur5.jpg
http://xpcoccinelle.fredisland.net/images/temp/coteazur4.jpg

Go to forum: Feedback and Support - DriverPacks Base

25 Topic by Coccinelle

(7 replies, posted in Feedback and Support - DriverPacks Base)

Hello the Team,

While integrating MassStorage 6.08 (just this package) + Base 6.08.5, I got this message :

http://img224.imageshack.us/img224/5486/dpackbase6085gl3.gif

I386/winnt.sif looks like this after closing message box :

;
; Generated by DriverPacks BASE 6.08.5
; http://www.driverpacks.net/
;


[Unattended]
	OemPnpDriversPath="D\D\M\3\1;D\D\M\3\1\O;D\D\M\3\2;D\D\M\3\3;D\D\M\A\1;D\D\M\A\2;D\D\M\A\3;D\D\M\A\4;D\D\M\A\5;D\D\M\A\6;D\D\M\A\7;D\D\M\A\8;D\D\M\AD\1;D\D\M\AD\2;D\D\M\AD\3;D\D\M\AD\4;D\D\M\AD\5;D\D\M\AD\6;D\D\M\AD\6\C;D\D\M\AD\7;D\D\M\AD\8;D\D\M\AD\9;D\D\M\AD\A;D\D\M\AM;D\D\M\AR;D\D\M\AT;D\D\M\AU\1;D\D\M\AU\2;D\D\M\AU\3;D\D\M\AU\4;D\D\M\AU\5;D\D\M\D;D\D\M\E;D\D\M\H\1;D\D\M\H\1\R;D\D\M\H\2;D\D\M\H\3;D\D\M\H\4;D\D\M\H\5;D\D\M\H\6;D\D\M\H\7;D\D\M\H\8;D\D\M\I\1;D\D\M\I\2;D\D\M\IN\1;D\D\M\IN\1\O;D\D\M\IN\2;;D\D\M\IT;D\D\M\J\1;D\D\M\J\2;D\D\M\L\1;D\D\M\L\2;D\D\M\L\3;D\D\M\L\4;D\D\M\M;D\D\M\N\123;D\D\M\N\4\I;D\D\M\N\4\R;D\D\M\N\4INTEL\I;D\D\M\N\4INTEL\R;D\D\M\N\590SLI\I;D\D\M\N\590SLI\R;D\D\M\N\TM;D\D\M\P\1;D\D\M\P\2;D\D\M\P\2\A;D\D\M\P\3;D\D\M\P\4;D\D\M\P\5;D\D\M\P\6;D\D\M\P\7;D\D\M\P\8;D\D\M\Q\1;D\D\M\Q\2;D\D\M\Q\3;D\D\M\Q\4;D\D\M\S\1;D\D\M\S\2;D\D\M\S\3;D\D\M\S\4;D\D\M\S\5;D\D\M\S\5\A;D\D\M\S\6;D\D\M\S\7;D\D\M\S\8;D\D\M\S\9;D\D\M\S\A;D\D\M\S\B;D\D\M\S\C;D\D\M\SI\1;D\D\M\SI\2;D\D\M\SI\3;D\D\M\V\1;D\D\M\V\2;D\D\M\VM"
	OemPreinstall=Yes
	DriverSigningPolicy=Ignore
	NonDriverSigningPolicy=Ignore
[Data]
	MsDosInitiated=No
[GUIRunOnce]
	command9="%SystemDrive%\DPsFnshr.exe"

I don't really understand: how 1008 bytes can exceed 4096 bytes limit ????


Thanks for your great help ! big_smile

Fred, from France, where I live (Côte d'Azur) :

http://xpcoccinelle.fredisland.net/images/temp/coteazur1.jpg
http://xpcoccinelle.fredisland.net/images/temp/coteazur2.jpg

Go to forum: Feedback and Support - DriverPacks Base