[Beta Release] RVM Integrator 1.5.4 beta 9

[5eraph]

It's been a couple months since the last release. The work isn't quite done, but more beta testing is needed. This is a major update: Read the Changelog.

Download: Link: RVM_Integrator_1.5.4_b09.7z (http://www.siginetsoftware.com/forum/attachment.php?attachmentid=658&d=1232813333)
Size: 853 KB
MD5: 23382A376A617555BD129E27D7770450
Current Localization Files:
Link: English_1.5.lng (http://www.siginetsoftware.com/forum/attachment.php?attachmentid=646&d=1232677195)
Size: 10.9 KB
MD5: C669F91EA7E248D8FD42C2F258B206EC


Link: Italiano_1.5.lng (http://www.siginetsoftware.com/forum/attachment.php?attachmentid=652&d=1232698293)
Size: 11.6 KB
MD5: 3E2B6BD98FC8A44373826E130DD9C54C


Link: Simplified_Chinese_1.5.lng (http://www.siginetsoftware.com/forum/attachment.php?attachmentid=655&d=1232727938)
Size: 8.1 KB
MD5: 6D6F4009872FAC260474A1F9791371A2
For next release: Driver32.cab issues in x64 sources: Properly update DrvIndex.inf with missing [driver32] section and file listing.
Possibly auto-update Driver32.cab without specialized code in entries.ini.
Changelog: b09 - Current release. (yumeyao)
[CreateCab] now cleans up after itself again.
Typographical error with $LNG_0803 corrected.


b08.5 - (5eraph) Localization files need updating. Updated $LNG_0800 and $LNG_0801 variables.
Added $LNG_0802, $LNG_0803 and $LNG_2350 variables.

Updated RyanVM Update Pack version checking code. File name checks updated for new names with SP numbers.
INF %NAME% string check updated for new names with SP numbers.

Service pack level check routine changes: Changed some language written to log for clarity.
Removed checks for which no actions were defined.
RVMi now terminates with exit code 1 when service pack slipstream attempt fails.
Added a check for when source service pack level was too high for chosen update pack.
RVMi terminates with exit code 1 when source service pack level is too high for chosen update pack.

Changed behavior of [obsolete] section to be more predictable. For example, suppose we specify "KB960000"... Old behavior: Removes "KB960000*", including KB960000-IE7.cat and KB960000-v2.cat.
New behavior: Removes only "KB960000.cat", "KB960000.ca_", "KB960000.exe" and "KB960000.ex_".

"Browse for Source" window is now resizable.

Source detection function Windows($RootDir) now looks in the proper place for x64 files SetupP.ini and PIDGen.dll.

Long file name warnings are no longer thrown in the log file for x64 sources.


b08.4 - (ENU_user) Issued fileflags fix (Support for HD base installs)


b08.3 Avoided UPX compression to reduce possible false positive reactions by AV software.
ReadDirectoryAsArray (b08.2: over-fix )
OSIdent on Log's Startup (b08.2: over-fix)


b08.1 - (code65536) Improved CabLite's logging
Replaced PEChecksum.exe with a direct call
Fixed two minor typos
Updated the El Torito boot sector with the one from the latest AIK
Fixed a few intermittent bugs caused by unreliable STDOUT scraping

[yumeyao]

I take the liberty to release 1.5.4 beta 9.
Changes:
1. [CreateCab] fix:
This issue is brought when the Integrator changes its way of handling cab compression. It would leave the directory for cabbing rather than remove the dir in latest betas.
Now it's fixed so the directory is deleted after cabbing.

2. language file fix:
$LNG_0803 is not handled correctly by the script.

----------edited----------
Simplified Chinese language file updated. sorry for the forgetting.
----------edited2----------
I forgot to change the titlebar to beta9. because old beta version won't indicate whether it's stable or beta on titlebar.... 5eraph changed this but i didn't noticed until some one pointed it out... oops.
http://www.ryanvm.net/forum/viewtopic.php?p=88874#88874
so i updated the attachment with a new one. if you have the old one, you don't need to update since there is no other change.

[mf3imp]

Hello to all,
I've just finished updating the Italian translation with the new strings.
It's attached to this post.

[ENU_user]

collectively to more modifications with this beta and especially for the Driver32.cab issuing I think it calls for a FINAL RVM Integrator 1.5.4

so use this thread for final test for the FINAL ... (no more beta's lol)

if any old bugs are showing up it will need to get into new beta's
if it ain't a special bug it shouldn't stop this final beta from going FINAL

if there are routines that need to be optimized in the script, that too, can wait and go into beta ...

the public RVM Integrator 1.5.3 is suffering from a few bugs with ryans updatepack as well ...which the latest beta takes care of among many other stuff like reliability, speed .etc thanks (again!) to code65536

keeping in mind that most novice users tend to use the public release regardless

Don't wait up for siginet to make the FINAL release as he is very busy ..

call it FINAL RVM Integrator 1.5.4 then later we can go into more beta ... ;)

[yumeyao]

I support you, ENU_user.
Let's wait for siginet's release of 1.5.4 FINAL and till then we mainly deal with errors & bugs, etc.

We'd better put our future planning for routine optimizings, new features, bugs investigating on the new 1.6.0 beta.
Our main current aim is to make it stable and not poping bugs that messes up the integration.

[5eraph]

Don't wait up for siginet to make the FINAL release as he is very busy ..

call it FINAL RVM Integrator 1.5.4 then later we can go into more beta ... ;)

Our main current aim is to make it stable and not poping bugs that messes up the integration.
I'm impatient as well, but let's not get ahead of ourselves. I gained access to the source code only two weeks ago. The current beta has only been available for 28 hours. And, we have no real feedback on the betas released this month, good or bad. There's a considerable number of fixes to test and I'm not done adding more as I find them.

The best time to release a final is just before Ryan releases his next update pack. That should give everybody plenty of time to find any remaining bugs we've missed. And it will give me a little more time to work out the issue with Driver32.cab and DrvIndex.inf (http://www.ryanvm.net/forum/viewtopic.php?p=87861#87861). For me, this issue is a showstopper. It must find its way into the next final.

[mr_smartepants]

Beta 09 is working fine for me. But I haven't been digging either.

[ENU_user]

once a temp or final routine for the Driver32.cab and DrvIndex.inf repacking under the 64 source is issued ..

and once all functions that use the path declairation as in AMD64\ or I386\ in in entries file's are found to be working on both types of a source with & without "UpdatePack"

which I haven't got around testing to the fullest, there aren't any special bugs I know of that can come in the way of the integration

this release should go public and replace the version which is buggy with the RyanVM_UpdatepPack

mostly to respect ryans work on top of all ... I know what it feels like to have an addon or an updatePack that doesn't run correctly with the current public

im sure ryan will be glad to update his pages with a working final that can fully supports hee's pack and work

I know you are on top of the 64updatepack and yumeyao's on top of his work

so please take your time but dont fallback with learning autoit lol, give the best of what you got now, leave the rest for the bested

meaning avoid pinning the work to dead lines on this ...

keep up the good work & thanks ;)

[Siginet]

Thanks Everybody! This helps me so much. You really have no idea. I feel like I have just had handcuffs taken off of me. ;) I have been trying to put together an integrator development team for quite a while And I think we have a great team now! :D

[ENU_user]

I must admit b08.5 is issuing some really annoying bugs :p

excellent catches 5eraph :)

I'll wait for the update on Driver32.cab issues in x64 sources before I'll start testing ...or digging into the code, again ;)

[elrico]

Hi,

I use this in entries.ini


[ExpandCab]
I386\ELEXTRA.CAB,@PLUGINS\elextra

[FileMove]
...
spupdsvc.exe,@PLUGINS\elextra\spupdsvc.exe
msimsg.dll.ar-sa.mui,@PLUGINS\elextra\msimsg.dll.ar-sa.mui
...

[CreateCab]
@PLUGINS\elextra,I386\ELEXTRA.CAB

In beta 9 elextra.cab is created but in plugin dir.

I386 don't work again. I must preserve compatibility a little with 1.5.3 for I386 because i can't review all addons. Can you make something for that?

Anyway you have done an impressive job. Thanks, i'll try some options and give you feedback.

[yumeyao]

I'll look into it when i get up in the morning.

Today is China's New Year's day(which is according to the Lunar (http://en.wikipedia.org/wiki/Lunar_calendar)). so happy new year to you all again.

[elrico]

Thanks for quick reply,

I compared two integrations between RVMi 153 and 154b9, only an updatepack, and no option used. With XP pro SP3 slimstreamed manually.

Some things seem fine (CMPNENTS folder is now concerved, sp2.cat is now deleted...) but for some other :
- i386\logowin.gif is deleted? why?
- and wbem fix for napclient* is only two files from [WBEM.CopyMOFs]
section of wbemoc.inf comented? And nothing more? (I ask this because with RVMi prior to 1.5.4b9 some lines aren't added into [Version] section of svcpack.inf on french Xp home).

I'll test more options and addons later, and XP home too.

[yumeyao]

Thanks for quick reply,

I compared two integrations between RVMi 153 and 154b9, only an updatepack, and no option used. With XP pro SP3 slimstreamed manually.

Some things seem fine (CMPNENTS folder is now concerved, sp2.cat is now deleted...) but for some other :
- i386\logowin.gif is deleted? why?
it's ok to delete it.
in fact the Integrator doesn't intend to "delete" it. It's done when the Integrator tries to repack MMSSETUP.CAB(which contains certain files for Windows Messenger 4.x), the Integrator detects there are logowin.gif in your i386\ directory so the Integrator regard this file as a updated one(in fact it is due to M$ hasn't cleaned it up) then compresses it into MMSSETUP.cab.
Since windows installation doesn't require logowin.gif in i386\, but only needs that in mmssetup.cab, so it's harmless.


- and wbem fix for napclient* is only two files from [WBEM.CopyMOFs]
section of wbemoc.inf comented? And nothing more? (I ask this because with RVMi prior to 1.5.4b9 some lines aren't added into [Version] section of svcpack.inf on french Xp home).

I'll test more options and addons later, and XP home too.
In fact the wbem fix only contains commenting 2 lines in wbemoc.inf(which i have discussed and pointed the reason in RyanVM's forum). the [Version] section of svcpack.inf is changed for other POSSIBLE issues(i can recall it's "battery" driver issue), i dunno why it's gone. i'll try to revert it.
Thanks for pointing this issue out.

BTW, 5eraph's saying he will release beta10 here (http://www.ryanvm.net/forum/viewtopic.php?p=88978#88978), so i will send codes to him if i can solve them.

[yumeyao]

@elrico:
would you help me confirm one thing:
look at your i386\layout.inf, locate at [Strings] section, look for string "cdname", does it have a localized name? no matter what it is, post it here.

well in the latest beta no code is actually changed about this.

[elrico]

Yumeyao, what did you here :o
Happy new Year :)

And voilà :
cdname = "CD-ROM Windows XP Professionnel"
productname = "Windows XP Professionnel"

They was several discutions on wbemoc.inf, i only remember that RVMi 1.5.4 fix the problem in a new way. With 1.5.3 I used the "clasic" with a ","

[yumeyao]

Sorry, but I meant... the xp french sp3 home(on which svcpack.inf fix didn't work for you), not pro.

yeah, after several discussions of wbemoc.inf fixes i looked up the windows installation source for some interesting finds, and then gave the reason out.

and FYI, the [CreateCab] issue is being discussed. since there is not a bug tracker for RVM Integrator, it's not convienent, though.

[elrico]

NP,


cdname = "CD-ROM Windows XP �dition familiale"
productname = "Windows XP dition familiale"

Oh! "CD-ROM Windows XP �����Édition familiale", dos encoding, bad copy/paste, i join the file.

[yumeyao]

Yeah!!! This is the answer i'm looking for.

the Integrator will distinguish different versions of windows(2k3, 2k, xp pro, xp home) by this string. for xp home, it will be happy to see "XP Home", this, in English laylou.inf, has a full string of "cdname = "Windows XP Home Editon CD-ROM"".

Then Integrator can't find "XP Home" in french localized string, resulting some features disabled.

[ilovepappa]

I got this error

[yumeyao]

this is not an Integrator issue.

In the log:
13:38:28 - ERROR: Service pack level of source is too high for chosen update pack.

this is because the addon(YZA_MultimediaV7BIT_AddOn_PureRunMod.rar) you're trying to integrate is for sp2. contact the addon author to ask for a sp3-compatible addon.

[ilovepappa]

this is not an Integrator issue.

In the log:
13:38:28 - ERROR: Service pack level of source is too high for chosen update pack.

this is because the addon(YZA_MultimediaV7BIT_AddOn_PureRunMod.rar) you're trying to integrate is for sp2. contact the addon author to ask for a sp3-compatible addon.

I assure you that this addon has always worked

[yumeyao]

then would you post any link to this addon?

[ilovepappa]

then would you post any link to this addon?

addon link (www.mediafire.com/?rmntc2jyw9n)
Thank You

[yumeyao]

oops... could you upload the entries*.ini here(unpacking the addon then you'll see)
i can't get access to mediafire due to GFW (http://en.wikipedia.org/wiki/Golden_Shield_Project) policy. though i tried using a proxy, yet downloading a file as large as 50M+ via a proxy is crazy.....

[ilovepappa]

oops... could you upload the entries*.ini here(unpacking the addon then you'll see)
i can't get access to mediafire due to GFW (http://en.wikipedia.org/wiki/Golden_Shield_Project) policy. though i tried using a proxy, yet downloading a file as large as 50M+ via a proxy is crazy.....

Here

[yumeyao]

I think this is the same cause as elrico's svcpack.inf not being modified.....
check your i386\layout.inf, find spcdname string and tell me the value....
ex.
spcdname = "Windows XP Professional Service Pack 3 CD"

BTW, did you ever encouter this error using RVM Integrator 1.5.3?

[Siginet]

that error:
13:38:28 - ERROR: Service pack level of source is too high for chosen update pack.

Will only represent itself if the UpdatePack is for an older ServicePack. Check your entries.ini file in your updatepack. See if it is for a SP2 or SP3 source. Remember Ryan now creates 2 different updatepacks. A Post-SP2 and a Post-SP3. ;)

[Siginet]

Yeah!!! This is the answer i'm looking for.

the Integrator will distinguish different versions of windows(2k3, 2k, xp pro, xp home) by this string. for xp home, it will be happy to see "XP Home", this, in English laylou.inf, has a full string of "cdname = "Windows XP Home Editon CD-ROM"".

Then Integrator can't find "XP Home" in french localized string, resulting some features disabled.

Yes we definatly need people to post any info if their local versions of windows are not being recognized properly. Because we have no way of knowing how to determin different languages unless they help. ;)

[yumeyao]

@Sigi:
not quitely.
the addon he is trying to integrate is a T-13 installer, and no sp info in [General] Section of entrie*.ini.

i think it's due to the similar reason as elrico's. RVM integrator checks service pack levels by reading some strings in layout.inf too. so RVM integrator can't get the exact service pack level, but get a error one..
$SPEntry's non-existance value is 'none', and $SP's non-existance value is ''(empty).
then autoit manage it some way that 'none' <(less than) ''(empty).

-----------------------------------
and for your second post.. can we find out a more efficient way by change how the Integrator gets OS type?

[elrico]

Can you externalise the $SPEntry string in an .ini? And eventually all other velue needed to know the service pack level etc...

Just an idea...

[Siginet]

Just to let everyone know... I took the time yesterday to notify any AV companies about false positives on the integrator file.

If anyone receives any more false positives please follow the instructions in this thread:
http://siginetsoftware.com/forum/showthread.php?t=550

[compstuff]

Sorry if this seems like a dumb question but I am about to try the 9 beta version and I'm wondering where the localization file goes... in my case the english version

[5eraph]

The localization file goes in the same directory as the Integrator... if you're not English. If you're English then you don't need a localization file. The English file exists to translate into other languages. :)

[compstuff]

Thanks :)

[chiman]

well guys I'm a newbie at all of this but I'm trying to intergrate various things into my winxp pro disc. I'll let you know how I do. cheers

[bhishmar]

1.5.4b9 versions both reported in this forum (siginetsoftware.com) & in ryanvms msfn page (http://www.ryanvm.net/msfn/) are different & has different md5 checksums. (7z file).
The contents of the files (.exe) after expansion is also different? :confused:

Can some expert here clarify the differences?
regards

[5eraph]

I slightly modified yumeyao's version here to report the proper information in the Version tab of the Properties window. That's the only change. Ryan has the unmodified version.

http://i272.photobucket.com/albums/jj164/5eraph/RVMi_Properties_VersionTab.png

[compstuff]

Just some feedback on the latest "beta": I have done just about a dozen integrations since yesterday and they have all gone without any noticable problems. I'm not as good as others at picking up on some of the more complex errors but as far as I can see I'm now ready to switch from 1.5.3
THANKS!!!!!

[ENU_user]

yes, ryan has updated his integrator links accordingly ...

the only link left is the public release of 1.5.3 @ http://integrator.siginetsoftware.com/index.php?download remains a problem, perhaps it can be replaced with this thread to buy some time till when the beta is finally ready for a public announcement

[rsadix]

Thanx Siginet,

I just used the b09 and had no issues. Thanx for all of your hard work!!

[Siginet]

I definatly can't take the credit for this one. This goes out to the entire team! Without them we would not be this far.

[BOTUS]

Hi Guys I seem to be the unlucky one.

note disc failed to install windows right at the start.... list of files it couldn't find of which first 3 were kodac_dc.icm, srgb.icm, streamci.dll


this is exact same issue I have had when using any version on RVMi 1.54

using 1.53 not had this problem.
first failure where didn't find files was with 1.54b8.4
this time was with 1.54b09

each time was using latest (at the time) version of boooggy's integrator to install MP11 and all patches


after RVMi, to add ryans pack and others see log
added MP11 using Mp11 slipstreamer 1.4.1
then nlite to remove / adjust (tiny tweaks)
then RVMi to make ISO...which has always taken ages when nlite I seem to remeber was just seconds?
23:41:09 - Windows XP Professional - Corporate SP3 Found
23:45:55 -
23:45:55 - Creating ISO
23:45:55 - Command Line = C:\WINDOWS.0\system32\cmd.exe /c C:\WINDOWS.0\System32\rvmisofs.exe -joliet-long -iso-level 2 -N -d -relaxed-filenames -duplicates-once -D -boot-load-seg 0x7C0 -boot-load-size 4 -o "C:\XP cds\XPSP3_ISO\Windows XP Professional Service Pack 3.iso" -b rvmintegrator.img -hide rvmintegrator.img -hide boot.catalog -J -hide-joliet xpboot.img -hide-joliet boot.catalog -no-emul-boot -volid "WXPVOL_EN" -sysid "Win32" "C:\XP cds\SP3 work"
23:45:55 - Using Internal mkisofs 2.01-bootcd.ru (i686-pc-mingw32)
23:52:02 - Total translation table size: 2048
23:52:02 - ISO Complete

Log Shutdown @ 23:54:32 On 06-02-2009

[Siginet]

One of te addons you are using must not be working correctly. I would try less addons and not use booogy's slipstreamer. Then test. Then add a few more addons and test and so on. Then use boogys slipstreamer and test again.

[BOTUS]

thanks for reply Siginet. Been playing every time same issue.

failed to install windows right at the start.... list of files it couldn't find of which first few were kodac_dc.icm, srgb.icm, streamci.dll, tosdvd.sys, tsbvcap.sys, tsbyuv.dll .........


USING 1.54 b09 started with fresh source added sp3 added rvm pack and less addons than earlier, failed issue listed above.

USING 1.53 same method success




ONLY other difference was used 1.53 to make ISO



2009-02-08_18.57.32
Log Startup @ 18:57:32 On February 08, 2009

Running OS: WIN_XP Service Pack 3 X86
RVMIntegrator v1.5.3

"C:\Updates\boot cd\Ryanvm\RVM_Integrator_1.5.3.exe"

18:57:32 - Windows XP Professional - Corporate SP3 Found
18:58:47 -
18:58:47 - Source Drive = C:\XP cds\XP Pro SP3
18:58:47 - Destination Drive = C:\XP cds\New Folder
18:58:47 - Destination Size = 21.91 GB
18:58:47 - Working Directory = C:\XP cds\New Folder\I386
18:58:47 - Temp Directory = C:\XP cds\New Folder\I386\rvmtemp
18:58:47 -
18:58:47 - Starting Integration
18:58:47 -
18:58:47 - Copying Files To The Destination Directory.
18:58:47 - Copying Working Directory...
19:02:40 - 6951 Files Copied in 232 Seconds
19:02:41 -
19:02:41 - Checking Destination For OS Type.
19:02:41 - Windows XP Professional - Corporate SP3 Found
19:02:41 -
19:02:41 - Extracting RVMUpdatePackSP3_1.0.3.7z
19:03:23 - MD5 Hash = 6B85B116AC1591F7EC2C7FFC4760E20D
19:03:23 - Extracting Reapers_CCleaner_2.16.830_AddOn.7z
19:03:26 - MD5 Hash = 56907B3DE2E65D3DAF402A0CC7B251B0
19:03:26 - Extracting RVMAddons_1.9.0.7z
19:03:27 - MD5 Hash = 888209EFCE3149127E778D3E513E517A
19:03:27 - Copying RedDXRuntimes_0.6.1_32bit.exe
19:03:27 - MD5 Hash = DDC6954149017F75F8303EA002B61286
19:03:27 - Extracting NR_IE7en_Addon_2.0.4a.7z
19:03:32 - MD5 Hash = 8929DDE401D80A573E952FADCA987CE0
19:03:32 - Extracting DotNetFx_All_In_1_Addon_v2.4.7z
19:03:55 - MD5 Hash = D521F5F64D36D5B68728D44C849815FD
19:03:55 - Extracting Foxy_DVDShrink_3.2.0.15_Addon_v1.1.cab
19:03:55 - MD5 Hash = 3FDAD767B296C1A2844850B293886619
19:03:55 - Extracting Kels_WinsockXPFix_v1.2_addon.CAB
19:03:55 - MD5 Hash = 25F3D7C4519A3922437CFD217C812191


etc........


19:30:06 - Optimizing System Files Finished.
19:30:06 -
19:30:06 - Cleaning Up.
19:30:06 - Integration Completed.
19:30:06 - Total Integration Time = 1645 Seconds
19:30:06 - ================================================== ================================
19:30:06 -

Log Shutdown @ 19:43:56 On 08-02-2009

[ENU_user]

ONLY other difference was used 1.53 to make ISO


so, using 1.54 b09 with makeiso from 1.53 fixes your problem ??

some info related to what else is is done on top of the source would help like:
is it possible you are using an nlited source when starting a new integration "to a new Root\Source" ? or any info as like ..

[BOTUS]

ENU_user, common thread for me seems to be failure when using RVMi 1.54,


more testing, odd results.....


xp source sp3 integrated with RVMi1.54

disable av and firewall, using RVMi 1.53 integrated only RVMUpdatePackSP3_1.0.3.7z, nothing else, no nlite, RVMi 1.53 to make iso

successful install of windows. but try to integrate mp11 to source now with RVM pack 1.4.1 fails every time


next test


xp source sp3 integrated with RVMi1.54

disable av and firewall, using RVMi 1.54 integrated only RVMUpdatePackSP3_1.0.3.7z nothing else no nlite, RVMi 1.54 to make iso

fails install of windows. but try to integrate mp11 using 1.4.1 success

[ronaldinho50]

merci bien l'ami

[BOTUS]

ENU_user, common thread for me seems to be failure when using RVMi 1.54,


more testing, odd results.....


xp source sp3 integrated with RVMi1.54 b09

disable av and firewall, using RVMi 1.53 integrated only RVMUpdatePackSP3_1.0.3.7z, nothing else, no nlite, RVMi 1.53 to make iso

successful install of windows. but try to integrate mp11 to source now with RVM pack 1.4.1 fails every time


next test


xp source sp3 integrated with RVMi1.54 b09

disable av and firewall, using RVMi 1.54 b09 integrated only RVMUpdatePackSP3_1.0.3.7z nothing else no nlite, RVMi 1.54 b09 to make iso

fails install of windows. but try to integrate mp11 using 1.4.1 success




further test

xp source sp3 integrated with RVMi 1.53

disable av and firewall, using RVMi 1.53 integrated only RVMUpdatePackSP3_1.0.3.7z, nothing else, no nlite, RVMi 1.53 to make iso

try to integrate mp11 to source now with RVM pack 1.4.1 success


so source broken during integration of SP3 when using RVMi 1.54bo9 ?

[Raoul90]

Beta 10 or final coming soon? :)

Dutch language file attached. :)
MD5: 0a84a4175ade8373c134e23f8c8a7169
Size: 12.0 KB


Greets,
Raoul

[5eraph]

I hope to have beta 10 up later today, Raoul90. Thank you for the Dutch translation. :)

[5eraph]

Thank you for your persistence, BOTUS. Looking through your logs, it seems that there is a problem with the new driver.cab compression method introduced in v1.5.4_b08.1. This is beyond my area of expertise; code65536 probably needs to have a look.

Here are the relevant bits of your logs:


2009-02-09_18.27.44
Log Startup @ 18:27:44 On February 09, 2009

Running OS: WIN_XP Service Pack 3 X86
RVMIntegrator v1.5.3

"C:\Updates\boot cd\Ryanvm\RVM_Integrator_1.5.3.exe"

18:27:45 - Windows XP Professional - Corporate SP3 Found
18:27:51 - Windows XP Professional - Corporate SP3 Found
18:28:36 -
18:28:36 - Source Drive = C:\XP cds\1.53 of XP Pro SP3
18:28:36 - Destination Drive = C:\XP cds\1.53 RVM
18:28:36 - Destination Size = 22.55 GB
18:28:36 - Working Directory = C:\XP cds\1.53 RVM\I386
18:28:36 - Temp Directory = C:\XP cds\1.53 RVM\I386\rvmtemp

[...]

18:32:59 - Expanding driver.cab
18:34:01 - Expanding SP3.cab

[...]

18:40:07 - Calculating the number of files to pack into driver.cab
18:40:52 - Rebuilding driver.cab
18:54:53 - Compressed 4784 Files Into driver.cab


2009-02-05_21.02.21
Log Startup @ 21:02:21 On February 05, 2009

Running OS: WIN_XP Service Pack 3 X86
RVMIntegrator v1.5.4 beta 9

"C:\Updates\boot cd\Ryanvm\RVM_Integrator_1.5.4_b09.exe"

21:02:25 - Windows XP Professional - Corporate SP3 Found
21:03:49 -
21:03:49 - Source Drive = C:\XP cds\xp SP3
21:03:49 - Destination Drive = C:\XP cds\SP3 work
21:03:49 - Destination Size = 26.20 GB
21:03:49 - Working Directory = C:\XP cds\SP3 work\I386
21:03:49 - Temp Directory = C:\XP cds\SP3 work\I386\rvmtemp

[...]

21:10:53 - Expanding driver.cab
21:12:03 - Expanding SP2.cab
21:12:21 - Expanding SP3.cab

[...]

21:18:54 - Rebuilding driver.cab
21:25:31 - Compressed 2047 files into driver.cab [code=07FF0001]


2009-02-09_18.57.59
Log Startup @ 18:57:59 On February 09, 2009

Running OS: WIN_XP Service Pack 3 X86
RVMIntegrator v1.5.4 beta 9

"C:\Updates\boot cd\Ryanvm\RVM_Integrator_1.5.4_b09.exe"

18:57:59 - Windows XP Professional - Corporate SP3 Found
18:58:10 - Windows XP Professional - Corporate SP3 Found
18:58:26 -
18:58:26 - Source Drive = C:\XP cds\1.54 of XP Pro SP3
18:58:26 - Destination Drive = C:\XP cds\1.54 RVM
18:58:26 - Destination Size = 22.02 GB
18:58:26 - Working Directory = C:\XP cds\1.54 RVM\I386
18:58:26 - Temp Directory = C:\XP cds\1.54 RVM\I386\rvmtemp

[...]

19:02:31 - Expanding driver.cab
19:03:11 - Expanding SP3.cab

[...]

19:07:43 - Rebuilding driver.cab
19:14:05 - Compressed 2047 files into driver.cab [code=07FF0001]

For the benefit of others, here's a summary of your previous posts with important segments highlighted in red.


Hi Guys, been reading about 1.5.4.B08.4s progress and with Rayn's pack out thought I'd give it a go. Failed miserably :eek: when trying to used finished disc to load windows on clean install.

Integration went without errors. I then added Boooggy's MP11 and all listed patches. Went to nlite 1.491 and added KB 952069

trying to load windows right at the start, making list of files it couldn't find many of which first 3 were kodac_dc.icm, srgb.icm, streamci.dll

binned that disc and this morning using RVM 1.5.3 did the same BUT did not yet add boooggy's MP11 now its working fine so will report back when I add MP11 is this any help ?

Update of my latest integration efforts (Using all the same files but integrator 1.5.3 with latest RVM pack, IE7, and other pack, it loaded windows OK) [...] complete success.

Hi Guys I seem to be the unlucky one.

note disc failed to install windows right at the start.... list of files it couldn't find of which first 3 were kodac_dc.icm, srgb.icm, streamci.dll


this is exact same issue I have had when using any version on RVMi 1.54

using 1.53 not had this problem.
first failure where didn't find files was with 1.54b8.4
this time was with 1.54b09

thanks for reply Siginet. Been playing every time same issue.

failed to install windows right at the start.... list of files it couldn't find of which first few were kodac_dc.icm, srgb.icm, streamci.dll, tosdvd.sys, tsbvcap.sys, tsbyuv.dll .........


USING 1.54 b09 started with fresh source added sp3 added rvm pack and less addons than earlier, failed issue listed above.

USING 1.53 same method success

ENU_user, common thread for me seems to be failure when using RVMi 1.54,


more testing

further test [...]

so source broken during integration of SP3 when using RVMi 1.54bo9 ?

[ENU_user]

the problem may have to do with how the permission assignments are set up on BOTUS's computer

sometimes when making a slight change in permissions even administrators runs with lower privileges

running the latest beta on a fresh OS or a OS where privileges where not tampered with. everything should run as expected

it isn't necessarily a cablite issue (the process that builds driver.cab .etc)

I guess some tests Under limited user privileges may help revile more about the nature of the problem but that helps with absolutely nothing if that is the true case of the problem.

BOTUS the only thing I can suggest you try is:

go to "Run" paste the following command, no quotation marks!!

"secedit.exe /configure /db C:\WINDOWS\sectest.db /cfg C:\WINDOWS\inf\defltwk.inf"

this should bring back the default behavior of how privileges should be set up on your machine by default

let the process complete and then try it all once again (after doing a Reboot of course ..)

Good luck

[BOTUS]

the problem may have to do with how the permission assignments are set up....

Hi ENU_user, thanks for following up, did as you suggest ran

"secedit.exe /configure /db C:\WINDOWS\sectest.db /cfg C:\WINDOWS\inf\defltwk.inf"


up popped a cmd window for a split second, waited a few mins nothing else seemed to be happening, rebooted.

then tried this

xp source sp3 integrated with RVMi1.54 b09

disable av and firewall, added mp11 using 1.4.1 went without hitch, made iso with 1.54 and loaded windows OK

then realised I hadn't integrated RVM pack....

with unmod xp sp3 source (sp3 integrated with RVMi1.54 b09) added RVMUpdatePackSP3_1.0.3.7z, nothing else, no nlite,

looking at log same as before ?

23:36:59 - Compressed 2047 files into driver.cab [code=07FF0001]

[ENU_user]

open a "cmd" window and run the command again to see that it completes successfully

it will take longer then any split second, thats for sure ..

[5eraph]

Beta 10 has been released (http://www.siginetsoftware.com/forum/showthread.php?t=561). Please continue bug reporting the current issue at the following thread, BOTUS.Driver cab failing with code 07FF0001 (http://www.siginetsoftware.com/forum/showthread.php?t=564)