MantisBT - DriverPacks BASE
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000029DriverPacks BASEslipstreamerpublic2006-05-27 06:312006-05-27 11:41
Reporterrazormoon 
Assigned ToBashratTheSneaky 
PrioritynormalSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version6.05 CP 
Target VersionFixed in Version6.05 
Destination OS Platform
Installation Platformdisc (CD/DVD)
DriverPacksall
DriverPacks Method2
DriverPacks Finisher MethodRunOnceEx
Summary0000029: M2+RunOnceEx: if no $OEM$ dir exists, then it won't be created and as a result RunOnceEx won't work
DescriptionTried slipstreaming using method 2, all packs, RunOnceEx with Default ID...

I've used this setup with both my own preexisting $OEM$ folder and one without.
The slipstreamer DOES NOT create $OEM$ folder!

I do see the messages of $OEM$ creation during the slipstream process, but nothing to show for it.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
has duplicate 0000026resolved BashratTheSneaky M1+RunOnceEx: if no $OEM$ dir exists, then it won't be created and as a result RunOnceEx won't work 
Attached Fileslog M1_DPs_BASE.log (8,096) 2006-05-27 09:09
http://bugtracker.driverpacks.net/file_download.php?file_id=15&type=bug
? DPs_fnsh.cmd (12,187) 2006-05-27 09:09
http://bugtracker.driverpacks.net/file_download.php?file_id=16&type=bug
log M2_DPs_BASE.log (3,474) 2006-05-27 09:25
http://bugtracker.driverpacks.net/file_download.php?file_id=17&type=bug
Issue History
Date ModifiedUsernameFieldChange
2006-05-27 06:31razormoonNew Issue
2006-05-27 06:31razormoonDriverPacks => all
2006-05-27 06:31razormoonDriverPacks Method => 2
2006-05-27 06:31razormoonFinishing Method => RunOnceEx
2006-05-27 06:31razormoonInstallation Platform => disc (CD/DVD)
2006-05-27 07:12BashratTheSneakyNote Added: 0000098
2006-05-27 07:50Nakatomi2010Note Added: 0000099
2006-05-27 08:27razormoonNote Added: 0000102
2006-05-27 09:09razormoonFile Added: M1_DPs_BASE.log
2006-05-27 09:09razormoonFile Added: DPs_fnsh.cmd
2006-05-27 09:13razormoonNote Added: 0000103
2006-05-27 09:25razormoonFile Added: M2_DPs_BASE.log
2006-05-27 09:28razormoonNote Added: 0000104
2006-05-27 09:31razormoonNote Edited: 0000103
2006-05-27 09:31razormoonNote Edited: 0000104
2006-05-27 09:44razormoonNote Edited: 0000103
2006-05-27 10:07razormoonNote Added: 0000105
2006-05-27 10:20razormoonNote Added: 0000106
2006-05-27 11:31BashratTheSneakyStatusnew => assigned
2006-05-27 11:31BashratTheSneakyAssigned To => BashratTheSneaky
2006-05-27 11:31BashratTheSneakyNote Added: 0000111
2006-05-27 11:31BashratTheSneakyStatusassigned => acknowledged
2006-05-27 11:40BashratTheSneakyStatusacknowledged => resolved
2006-05-27 11:40BashratTheSneakyFixed in Version => 6.05
2006-05-27 11:40BashratTheSneakyResolutionopen => fixed
2006-05-27 11:40BashratTheSneakyNote Added: 0000112
2006-05-27 11:40BashratTheSneakyProjectionnone => tweak
2006-05-27 11:40BashratTheSneakyETAnone => < 1 day
2006-05-27 11:41BashratTheSneakySummary$OEM$ Folder => M2+RunOnceEx: if no $OEM$ dir exists, then it won't be created and as a result RunOnceEx won't work
2006-05-27 11:55BashratTheSneakyRelationship addedrelated to 0000026
2006-05-27 11:56BashratTheSneakyRelationship deletedrelated to 0000026
2006-05-27 11:56BashratTheSneakyRelationship addedhas duplicate 0000026

Notes
(0000098)
BashratTheSneaky   
2006-05-27 07:12   
Method 2 does not require the $OEM$ folder, but the OEM folder.

Please post your slipstream log.
(0000099)
Nakatomi2010   
2006-05-27 07:50   
Could be these are related to the error I posted earlier....
(0000102)
razormoon   
2006-05-27 08:27   
I'm currently going through an M1 slipstream, so I'll post log in a little while. I wanted to ask though...if $OEM$ is only used by M1, why does dpbase edit my cmdlines.txt and adds *roe*.cmd to $OEM$? (Provided $OEM$ is there of course)
(0000103)
razormoon   
2006-05-27 09:13   
(edited on: 2006-05-27 09:44)
Attached is the M1 BASE LOG. If you have a look you'll notice some discrepancies at the end of the log, specifically with how $OEM\DPs_ROE.cmd is missing a $.
Take a look at the cmd file...do a find... \\ and you'll notice entries with double backslashes! Will post M2 in a few minutes.
(0000104)
razormoon   
2006-05-27 09:28   
(edited on: 2006-05-27 09:31)
OK, M2 is up.

2006-05-27 08:24:00 : <SLIP> Created \I386\presetup.cmd file.
2006-05-27 08:24:00 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2006-05-27 08:24:01 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2006-05-27 08:24:01 : <SLIP> Updated \I386\winnt.sif to support method 2.
2006-05-27 08:24:01 : <SLIP> Updated \$OEM$\cmdlines.txt to execute DPs_ROE.cmd.
2006-05-27 08:24:01 : <SLIP> Created \$OEM\DPs_ROE.cmd batch file.
2006-05-27 08:24:01 : <SLIP> Slipstream finished in 2 minutes and 7 seconds.
2006-05-27 08:24:04 : <CLNP> Temporary working directory successfully deleted.
2006-05-27 08:24:04 : Program terminated.


So...It says its updating and creating stuff in $OEM$ (and $OEM :P), but the directory just doesn't exist. The above excerpt is from M2 with no preexisting $OEM$. However it does do what it says when there's already an $OEM$ folder in place.
(0000105)
razormoon   
2006-05-27 10:07   
Uh, more stuff...

I do have my own $OEM$ folder w/ bells, whistles, whathaveyou. I just tried to slipstream to an empty $OEM$ folder and basepack deleted it! lol
(0000106)
razormoon   
2006-05-27 10:20   
So, in summary, you mentioned M2 does not require $OEM$. I was just curious as to what type of cleanup happens, even with M2.

M2 still gives me the option to use RunOnceEx, yet does not implement anything unless 1) You have an existing $OEM$ folder and 2) $OEM$ is populated with files (otherwise, the directory gets deleted).

I'm just trying to get some clarification as to whether or not to run dps_fnsh.cmd, using M2, at first login.

Another thing is the various occurences of double backslashes in dps_fnsh.cmd itself. It was a cool find.

Thanks for everything bashrat.
(0000111)
BashratTheSneaky   
2006-05-27 11:31   
Able to reproduce the issue.
(0000112)
BashratTheSneaky   
2006-05-27 11:40   
Fixed.