0000320: Failed to CAB compress adpu160m .sys

(0000611)
BashratTheSneaky (administrator)
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 (reporter)
2007-01-16 09:41

I've attached indeed the wrong file.

(0000616)
BashratTheSneaky (administrator)
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 (reporter)
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 (administrator)
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 (administrator)
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 (reporter)
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 (reporter)
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 (reporter)
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 (administrator)
2008-05-04 19:09

Can you confirm this issue is resolved?

Issue History
Date Modified	Username	Field	Change
2007-01-16 06:19	Meeuws	New Issue
2007-01-16 06:19	Meeuws	Status	new => assigned
2007-01-16 06:19	Meeuws	Assigned To	=> BashratTheSneaky
2007-01-16 06:19	Meeuws	File Added: RVM_Integrator_1.4.2.log
2007-01-16 06:19	Meeuws	Destination OS Platform	=> wnt5_x86-32 (Windows XP)
2007-01-16 06:19	Meeuws	Installation Platform	=> not applicable
2007-01-16 06:19	Meeuws	DriverPacks	=> all
2007-01-16 06:19	Meeuws	DriverPacks Method	=> 2
2007-01-16 06:19	Meeuws	DriverPacks Finisher Method	=> GUIRunOnce
2007-01-16 07:45	BashratTheSneaky	Note Added: 0000611
2007-01-16 07:45	BashratTheSneaky	Status	assigned => feedback
2007-01-16 09:40	Meeuws	File Added: DPs_BASE.log
2007-01-16 09:41	Meeuws	Note Added: 0000612
2007-01-22 13:29	BashratTheSneaky	Note Added: 0000616
2007-01-25 09:41	Meeuws	Note Added: 0000618
2007-01-31 15:42	BashratTheSneaky	Note Added: 0000622
2007-01-31 16:26	BashratTheSneaky	Note Added: 0000623
2007-02-01 03:59	Meeuws	Note Added: 0000624
2007-02-20 17:26	BashratTheSneaky	Relationship added	parent of 0000335
2007-10-15 19:08	contink	Note Added: 0000703
2007-10-15 20:04	contink	Note Added: 0000704
2008-05-04 19:09	OverFlow	Status	feedback => assigned
2008-05-04 19:09	OverFlow	Assigned To	BashratTheSneaky => OverFlow
2008-05-04 19:09	OverFlow	Note Added: 0000739
2008-05-04 19:09	OverFlow	Status	assigned => feedback
2008-05-09 02:26	OverFlow	Status	feedback => closed
2008-05-09 02:26	OverFlow	Resolution	open => fixed

Notes
(0000611) BashratTheSneaky (administrator) 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 (reporter) 2007-01-16 09:41	I've attached indeed the wrong file.

(0000616) BashratTheSneaky (administrator) 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 (reporter) 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 (administrator) 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 (administrator) 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 (reporter) 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 (reporter) 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 (reporter) 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 (administrator) 2008-05-04 19:09	Can you confirm this issue is resolved?