LiveXP with 2k3-sp2 possible ?
#1
Posted 04 September 2008 - 09:10 PM
I used 2k3-sp2 as source and got critical errors during boot: can't load browseui.dll and shdocvw.dll.
After errors system reboots.
IS this normal ? - as far as I know I only added VMplayer and Converter
Ulli
#2
Posted 04 September 2008 - 11:04 PM
Regards,
Galapo.
#3
Posted 04 September 2008 - 11:30 PM
I've tested with Windows 2003 some time ago and it is working good on the standard configuration (nothing fancy added or modified)
Try to create a project that doesn't using so much ramdisk (*think* that minimal RAM disk size to start the explorer shell on this case is barely above 3Mb) or increase the available RAM on your virtual machine.
Look on the qemu script to find the fail safe emulated RAM values for LiveXP.
Good luck.
#4
Posted 04 September 2008 - 11:54 PM
The qemu VM was only configured with 384 RAM - but shouldn't that be enough ?
I also tried in VMware with 1200 MB RAM - same problem.
To me this problem with browseui.dll and shdocvw.dll looks like an error with creating the profile in ramdisk.
@Galapo - do you know if OffLine Sysprep can be installed on the fly - or does it need registry entries available at boot time ?
Ulli
Hmm - I just loaded the setupreg.hiv and looked up values for
HKEY_LOCAL_MACHINE\system\ControlSet001\Control\Session Manager\Environment\Temp = %TD%\%TempDir%
Is that correct ? - what is %TD% ?
#5
Posted 05 September 2008 - 12:22 AM
No traditional installing is necessary: just copy the 'OfflineSysPrep' folder under '%targetdir%\Program Files' (or whatever localised name you have for "program files"). Depending on your exac setup, you may need to copy paragliders runscanner to the 'tools' folder.@Galapo - do you know if OffLine Sysprep can be installed on the fly - or does it need registry entries available at boot time ?
Regards,
Galapo.
#6
Posted 05 September 2008 - 12:30 AM
Yes, that would be my guess too. This is confirmed by the following:To me this problem with browseui.dll and shdocvw.dll looks like an error with creating the profile in ramdisk.
It looks to me like the TempPE script has not filled the variables correctly and then wriiten them into the registry (that is, %TD%\%TempDir% should be filled and written as something like 'b:\Documents and Settings...'.Hmm - I just loaded the setupreg.hiv and looked up values for
HKEY_LOCAL_MACHINE\system\ControlSet001\Control\Session Manager\Environment\Temp = %TD%\%TempDir%
Is that correct ? - what is %TD% ?
Can you confirm what version of WB you are using. If not 075b4, then please test again with that version. I'd have to double-check, but there could well be some code in this newer script by Peter that requires 075 rather than, say, 074.
Thanks,
Galapo.
#7
Posted 05 September 2008 - 04:56 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users