Possible Outstanding Bug Reports For Siginet.

[Stimpy]

Hello Siginet, as per your request, I have compiled a very rough and ready list of reported bugs and problems from your forum regarding the RVMI.

I must stress that I have checked the forum threads for answers to these reported isses, and have made the list from unanswered bug reports. *I have not edited any of these quotes in any way.*

*** Keep in mind that you may have already fixed some/all of these issues, as well as the possiblility that some of these bugs may be caused by user error. So please dont think I'm telling you that this is a clear list of outstanding bugs ***


1.) Window Setup Error - entry "kbdhid.sys" in [SourceDisksFiles] section of the INF
http://www.siginetsoftware.com/forum...read.php?t=355


2.) if both SETUP.exe(the one launched to install xp) & SETUP.EX_(the one in control panel to add/remove xp components) exists in i386....... SETUP.exe will be compressed to setup.ex_ and ... the original setup.ex_ missing.
http://www.siginetsoftware.com/forum...read.php?t=369


3.) AutoIt Error -1
Variable Used Without being Declared
http://www.siginetsoftware.com/forum...read.php?t=371


4.) Nonno Fabio - When an addon needs to put the same file from txtsetup.sif in two different locations, Integrator chooses only one of them and discards the first one.
http://www.siginetsoftware.com/forum...p?t=299&page=8


5.) Nonno Fabio - suggestion:
we have noticed that Integrator is able to write no more than 640 lines in dosnet.inf and about 750 in txtsetup.sif: we have tested that this could cause problems with some big addons. It's possible to increase those limits?
http://www.siginetsoftware.com/forum...p?t=299&page=8


6.) Siginet - Yeah I plan on changing the drivercab cacheing to use md5 hashing of the original driver.cab file as well
http://www.siginetsoftware.com/forum...p?t=299&page=7


7.) ENU_USER - @sig I think i found something weird when using a command stream to append addons to replicate this use the command without the \intgrate switch
then look into integrator.ini - under [AddonPacks] listing. here im seeing the addon names show on both sides where its shouldn't. the parameter on the right side should only show the path to the addon without the addon itself pended...
http://www.siginetsoftware.com/forum...p?t=299&page=6


8.) Bhishmar - Two identical integrator runs WITHOUT & WITH driver-cab caching enabled, results in output files differences.

The run in which caching is enabled results in additional #19 files. Since these #19 files are already inside driver.cab in both cases, no functional problem, as noted earlier... Just do two successive integrations with RVMUpdatepack only. First one with driver.cab caching disabled, & second with caching enabled.

The second integrator run has more files (#19) left in the output. Other than this the two outputs are exactly identical.
But all these 19 files are anyway already included within the driver.cab, in both run outputs. So i think there is no functional problem.

Only see why this happened, to ensure no other side effects.
regards.
Note: The extra files in i386 are: aec.sy_, battc.sy_, kmixer.sy_, kswdmcap.ax_, msdv.sy_, ndisuio.sy_, ntkrnlpa.sy_, portcls.sy_, powerfil.sy_, ..........
allmost all files seems to be from sp2.cab
http://www.siginetsoftware.com/forum...p?t=299&page=5



9.) Will not slipstream if the service pack filename has a space in it.


10.) Stimpy - RVMI Cannot Slipstream SP1a on to an original XP SP0 Source - It just comes up with a box telling you what the command options for the Service Pack are, OK button at the bottom of the box, then it exits.
http://www.siginetsoftware.com/forum...read.php?t=364


11.) GC_917 - Error: No entries*.ini Found, Exiting
I keep receiving this message when I try to integrate. I have tried using the XP Pro cd as well as emptying the contents of the CD onto the hard drive but I still receive this message.
gets past
Gathering temp files
Expanding Drivers cab
Expanding SP3.cab
Copying files for drivers.cab repackaging

Originally Posted by TwoJ
12.) On integration of XP Home & Professional SP2 Upgrade versions, they are properly detected as Upgrade
After integration with SP3 they are detected as Retail versions and not upgrade versions

13.) Also do you know about slipstreaming SP3 in media center 2005, i saw a thread over in msfn that it actually downgrades certain components when you slipstream SP3.
http://siginetsoftware.com/forum/sho...84&postcount=5

14.) msdemich - When you integrate to the source, all extra folders are preserved. (cmpnents, DOCS, SUPPORT, VALUEADD) When you integrate to a destination folder other than the source, extra folders are NOT copied.

15.) Elrico - Optimize system Files/Driver cab caching
When one of this option is activated [I386_compress], [drivercab_copy] and [drivercab_move] are ignored. A good example is the file entries_ie7.ini, i must put twice the files in [file_move].
The second thing : files in habitually in [drivercab_move] are copied in I386 when i re-run an updatepack integration with driver cab caching checked. Even if my entries*.ini contain or not [drivercab_move] section.

16.) Elrico - Unicode file support...

All Unicode-Dos files are jumped to DOS (sysoc.ini etc)... when i edit hivesys.inf All text with non english character are transformed into strange things (not in the files, but after installation).


I think that covers user submitted bugs on your forum since the release of RVMI 1.5.1.

[msdemich]

Maybe this was intentional but I haven't found it in documentation anywhere. This threw me for a bit: I thought I was doing something wrong:

When you integrate to the source, all extra folders are preserved. (cmpnents, DOCS, SUPPORT, VALUEADD)
When you integrate to a destination folder other than the source, extra folders are NOT copied.


Thanks

[TwoJ]

Possible bug;

-On integration of XP Home & Professional SP2 Upgrade versions, they are properly detected as Upgrade
After integration with SP3 they are detected as Retail versions and not upgrade versions

-Also do you know about slipstreaming SP3 in media center 2005, i saw a thread over in msfn that it actually downgrades certain components when you slipstream SP3.

[Siginet]

Possible bug;

-On integration of XP Home & Professional SP2 Upgrade versions, they are properly detected as Upgrade
After integration with SP3 they are detected as Retail versions and not upgrade versions

-Also do you know about slipstreaming SP3 in media center 2005, i saw a thread over in msfn that it actually downgrades certain components when you slipstream SP3.

I wasn't aware of either of these issues. Thanks for posting.
The new Beta RVM Integrator will be online soon.

Any ideas on the best thing for the integrator to do reguarding slipstreaming MCE?

[TwoJ]

No problem - happy to help out a bit

the problem of SP3 integration in to Media Center Edition 2005 MCE2005 can been here;
http://www.msfn.org/board/Slipstream...5-t116371.html

According to nuhi he says that its not really possible but as usual people are finding little hacks around it, but obviously it is not an officially supported integration.

Apparently nlite does integrate it but apparently you get MCE v2.8 instead of v3 (whatever that means), also somethings might not work.

I'm not sure what to suggest - while i like the idea of having any OS completly up-to-date when you install it, i have never needed to install MCE yet, so i guess its not on my high priority list.
I think i would let others figure this one out in terms of what is possible. Maybe for the time being to not allow a sp3 integration on a MCE2005 until a tried&true method has establised itself?