MantisBT - DriverPacks BASE
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000320DriverPacks BASEslipstreamerpublic2007-01-16 06:192008-05-09 02:26
ReporterMeeuws 
Assigned ToOverFlow 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version7.01.2 rc1 
Target VersionFixed in Version 
Destination OS Platformwnt5_x86-32 (Windows XP)
Installation Platformnot applicable
DriverPacksall
DriverPacks Method2
DriverPacks Finisher MethodGUIRunOnce
Summary0000320: Failed to CAB compress adpu160m .sys
DescriptionFailed to CAB compress F:\RIS_Build\RIS_Target\I386\adpu160m .sys to F:\RIS_Build\RIS_Target\I386\adpu160m .sy_.

The error seams the space between adpu160m and .sys

Steps To Reproduce
Additional InformationI'm prepearing a RIS image.
I have this error if I'm running base form a is WinXP Dutch with location Netherlands(Belgium) and Belgium keyboard pc AND if I run it form a win2003 server English with the same keyboard & location as the pc.
TagsNo tags attached.
Relationships
parent of 0000335closed BashratTheSneaky QuickStream Cache for DriverPack MassStorage text mode is empty 
Attached Fileslog RVM_Integrator_1.4.2.log (3,576) 2007-01-16 06:19
http://bugtracker.driverpacks.net/file_download.php?file_id=232&type=bug
log DPs_BASE.log (101,649) 2007-01-16 09:40
http://bugtracker.driverpacks.net/file_download.php?file_id=233&type=bug
Issue History
Date ModifiedUsernameFieldChange
2007-01-16 06:19MeeuwsNew Issue
2007-01-16 06:19MeeuwsStatusnew => assigned
2007-01-16 06:19MeeuwsAssigned To => BashratTheSneaky
2007-01-16 06:19MeeuwsFile Added: RVM_Integrator_1.4.2.log
2007-01-16 06:19MeeuwsDestination OS Platform => wnt5_x86-32 (Windows XP)
2007-01-16 06:19MeeuwsInstallation Platform => not applicable
2007-01-16 06:19MeeuwsDriverPacks => all
2007-01-16 06:19MeeuwsDriverPacks Method => 2
2007-01-16 06:19MeeuwsDriverPacks Finisher Method => GUIRunOnce
2007-01-16 07:45BashratTheSneakyNote Added: 0000611
2007-01-16 07:45BashratTheSneakyStatusassigned => feedback
2007-01-16 09:40MeeuwsFile Added: DPs_BASE.log
2007-01-16 09:41MeeuwsNote Added: 0000612
2007-01-22 13:29BashratTheSneakyNote Added: 0000616
2007-01-25 09:41MeeuwsNote Added: 0000618
2007-01-31 15:42BashratTheSneakyNote Added: 0000622
2007-01-31 16:26BashratTheSneakyNote Added: 0000623
2007-02-01 03:59MeeuwsNote Added: 0000624
2007-02-20 17:26BashratTheSneakyRelationship addedparent of 0000335
2007-10-15 19:08continkNote Added: 0000703
2007-10-15 20:04continkNote Added: 0000704
2008-05-04 19:09OverFlowStatusfeedback => assigned
2008-05-04 19:09OverFlowAssigned ToBashratTheSneaky => OverFlow
2008-05-04 19:09OverFlowNote Added: 0000739
2008-05-04 19:09OverFlowStatusassigned => feedback
2008-05-09 02:26OverFlowStatusfeedback => closed
2008-05-09 02:26OverFlowResolutionopen => fixed

Notes
(0000611)
BashratTheSneaky   
2007-01-16 07:45   
So you are using the RyanVM integrator, which in turn calls the DriverPacks BASE.
Not a problem, but you should post the DPs_BASE.log file, NOT the RyanVM integrator log file. There's nothing useful to find in that log file!

This line in the RyanVM integrator log file

Executing External Program: F:\RIS_Build\DP\DPs_BASE.exe /API:"RVMIntegrator 1.4.2" /SETTINGS:"F:\RIS_Build\DP\settings.ini"

marks that you're using the settings file "F:\RIS_Build\DP\settings.ini". So you will have to open up THAT file (the settings.ini) and add the entry

debug = "yes"

to the [General] section.


Then run the RyanVM integrator again, get the log file and attach it to this issue.

Thanks.
(0000612)
Meeuws   
2007-01-16 09:41   
I've attached indeed the wrong file.
(0000616)
BashratTheSneaky   
2007-01-22 13:29   
Could you please download DP MassStorage again and retry? I really think it's due to a bad entry there... Though that sounds impossible.

But this is an error that should occur on EVERY system, which is why it must be something special on your system... So please retry.
(0000618)
Meeuws   
2007-01-25 09:41   
Some try & error remarks :
With the new Masstorage pack (7011) I get an other error :
Failed to CAB compress F:\RIS_build\RIS_Target\I386\dpti2o .sys to F:\RIS_build\RIS_Target\I386\dpti2o .sy_.

Ever if I don't use RVM before BTS I get this error.
I'm using the lateste base (7.01.5) at the moment

Side notes:
- If I don't manuely empty the QSC it get this error:
<CRIT> QuickStream Cache for DriverPack MassStorage text mode is empty!
- If I don't select textmode integration I getting :
<CRIT> Failed to CAB compress \D\M\.sys to \.SY_.
- If I don't select Massstorage pack at all I'm also getting
<CRIT> Failed to CAB compress \D\M\.sys to \.SY_.
(0000622)
BashratTheSneaky   
2007-01-31 15:42   
Those last two errors are fixed in issue 0000334. That first one, I'm not able to reproduce, please post a DPs_BASE.log of an instance where you are able to generate such an error.
(0000623)
BashratTheSneaky   
2007-01-31 16:26   
Please also update to the latest BASE (just updated to 7.01.6), it has that 0000334 bug fixed.
(0000624)
Meeuws   
2007-02-01 03:59   
I've updated to 7.01.6 and still getting the failed \dpti2o .sy_.
error.

I've summited an other bug report for the "QSCache is empty" error.
(0000703)
contink   
2007-10-15 19:08   
I just wanted to note that this issue is VERY much alive and "well"...

Using the latest drivers (ie: 7092 - 710) and the \dpti2o .sy_ is very much alive and kicking off.

FYI: The \dpti2o.sys file does exist in the I386 folder as do many others when you start on a deleting mission! so it's entirely possible that there's a list of files that the text mode or something similar try to overwrite and fail.

What may be a root cause is the actual XP CD source being used which is Corporate XP-SP2... UK based and used for educational establishments.
(0000704)
contink   
2007-10-15 20:04   
On further investigation it seems this may be a permissions issue:

When I deleted the files listed here:
[code]2007-04-22 08:44:53 : <DBG> $dpm_tm_drv_replace_wxp_x86_32 = array(
2007-04-22 08:44:53 : <DBG> [0] => 8
2007-04-22 08:44:53 : <DBG> [1] => dpti2o
2007-04-22 08:44:53 : <DBG> [2] => adpu160m
2007-04-22 08:44:53 : <DBG> [3] => ALIIDE
2007-04-22 08:44:53 : <DBG> [4] => mraid35x
2007-04-22 08:44:53 : <DBG> [5] => dac2w2k
2007-04-22 08:44:53 : <DBG> [6] => dac960nt
2007-04-22 08:44:53 : <DBG> [7] => ultra
2007-04-22 08:44:53 : <DBG> [8] => ql12160[/code]

It allowed the new files to be written and solved the error message.

If nothing else some error checking for permission issues might resolve this being such a PITA..
(0000739)
OverFlow   
2008-05-04 19:09   
Can you confirm this issue is resolved?