84 replies to this topic

[Lancelot]

did you run
RegWrite('HKLM\SYSTEM\Setup', 'SystemSetupInProgress', 'Reg_Dword', '0x00000000')
before trying ghost ?

always and verify with each trial


joakim

Okey i followed the way of loader now
first installed:
vbrun60sp6.exe
vcredist_x86_2005.exe
vcredist_x86_2008.exe
msxml6_x86.msi
Than vss batch
than ghostloader.....


ghostloader tries to install wimfltr, but it is already installed

vss batch is okey but cant start swprv service (okey i add swprv which i forgot). I add a line to the top of new batch which didnt make service start. picture (path to executable taken from 2k3!)
( vss_ddu.dll vssui.dll are not in xp and obviously will not effect the batch, as you say it is a general batch )


2nd trial with 2k3sp2 source
first installed:
vbrun60sp6.exe --> cant so i manually add files -> cause lock down
vcredist_x86_2005.exe
vcredist_x86_2008.exe
msxml6_x86.msi
Than vss batch -->swpnp service works
than ghostloader..... ---> trying to install wimfltr cause collapse
it seems to me with 2k3 if it is already exists, 2k3 refuses and lock .

so i turn back to junction+ .reg+.ghost14.cmd --> get same result with xp32





other notes:

First of all xp is not verified to work. 2k3 and vista is currently verified to work here.

yep i know from begining, just giving a shot.

Only junction the dotnet2 package. Do NOT junction anything inside LODR\ghost14.

i dont junction dotnet2 at the moment, all in bootsdi.img. I decide to junction ghost14 because there is X:\LODR\ghost14 in .reg file.

The fixinstall.bat can be removed and is never used.

okey



Final notes:
maybe my dotnet is too old , also i have other trials in my mind but time ..... ,
I guess for these lodr packs to try with livexp, first we need a dotnet2 package preparation routine that can be applied by everyone. For now a quick way to prepare a \dotnet2_xp_sp2_enu\ and \dotnet2_2k3_sp2_enu\ is enough to me in which i will follow sanbarrow way (later a more livexp way to prepare these ).

but as joakim indicated value of lodr comes with big packages and livexp need a trustable .net2 first .

CU

[joakim]

When I start thinking about it, ghost 14 is actually an app that depends on a lot things.

I will look more specifically on the issue xp vs 2k3 and come up with some "easy" to understand guidelines.

I will also make different dotnet2 packages...with vc2005...

And also make a check for the presence of the wimfltr..

Sorry, I guess I just had too many of the dependacies present and didn't see all the possible errors and conflicts coming.

Joakim


Important:
Don't touch ghost14.reg (unless you're curious and want look). The values of X:\ inside it will be patched and modified and the loader handles this itself. That's why the loader deletes these files after they are executed. They are written to %temp%\ghost14 and make sure %temp% is defined (I thought most had it by default).

[Lancelot]

Sorry, I guess I just had too many of the dependacies present and didn't see all the possible errors and conflicts coming.

That is why galapo offered (and i %98 support) a common plugin/script for inter environment (+options) check dependacies.
%2 part was:
galapo support to write the result to registry at startup, so a lodr writer (joakim) can put checks to this specific registry (reg read wimfltrinstalled if no ... )... it is already in livexp, but topic ended later.
I was supporting to have an individual batch (maybe better au3 exe ) that makes the tests with writer's lodr application demands. (i wrote a .cmd that times too, but not easy to find now)

just reminding old days, lets not focus on this for now, for now better to see wheels turning first .

[joakim]

That discussion that went on some time was rather interesting and I learned a bit from. Don't know what happened, it just died out..

We can continue on that track, just not now. I haven't got time.

Joakim


Important:
This LODR pack is incompatible with what we discueed then, and is not the same as what sanbarrow has (slightly different). Mine is self contained and independant from projects.

[joakim]

Update:
ghost14_LODR_v1002
dotnet2_xp-installrite_61Mb
vc_patcher_v1002.rar

Made a check for the presence of wimfltr.
Removed Fixinstall.bat from file collection batch.
Does not delete the registry patches written to %temp%\ghost14 for those interested.
Custom vss batch for xp included.

About XP:
I received a ramloading xp of livexp to test on. Although very basic and limited in that many dependancies where missing, I managed to get passed the dotnet2 and vc checks. But ended with a crash and "an exception that could not be handled". Don't know what the problem is with xp at the moment. The image I tested did also not have wmi installed which may have contributed to the crash.

Be sure to have xcopy in path before launching vc_patcher.

Joakim

[sanbarrow]

Joakim - from my experience wmi-support is not required for dotnet2 - at least not in 2k3

[risolutore]

This is what changed in my activation procedure on BESR

; Report of the Regshot 2.0.1.63 unicode
;
; Shot A:
; Shot date: 06/05/2009 17.55.28, Computer: SOLVO, User: utente,
; Shot type: , Shot time: 10.63 s
; Keys: 94818, Values: 173874, Folders: 0, Files: 0
; Deleted keys: 0, Deleted values: 0, Changed values: 11, Total changes: 11
;
; Shot B:
; Shot date: 06/05/2009 17.56.49, Computer: SOLVO, User: utente,
; Shot type: , Shot time: 11.10 s
; Keys: 94823, Values: 173885, Folders: 0, Files: 0
; New keys: 5, New values: 12, Changed values: 11, Total changes: 28
;
; Comment: after the installation procedure completes
;

[Version]
Signature=$Windows NT$
Class=Base

[DefaultInstall.NT]
DelReg=ShotA.new
AddReg=ShotB.deleted,ShotB.changed

[ShotA.new]

[ShotB.deleted]
HKLM,"%Key1%","Backup Exec",1,d9,07,05,00,03,00,06,00,11,00,37,00,39,00,61,02
HKLM,"%Key2%","Trace Level",,""
HKLM,"%Key3%","Enable",0x10001,1
HKLM,"%Key3%","SwapSync",0x10001,1
HKLM,"%Key3%","Palettized Formats",0x10001,1
HKLM,"%Key3%","IO Priority",0x10001,0
HKLM,"%Key3%","Use Generic Stencil",0x10001,1
HKLM,"%Key3%","Enumerate as ICD",0x10001,0
HKLM,"%Key4%","O",1,00,00,00,00,00,00,00,00
HKLM,"%Key4%","AK",1,2a,7d,04,fb,00,00,80,d7
HKLM,"%Key4%","LO",1,48,00,00,00,00,00,00,00,30,00,37,00,34,00,31,00,38,00,37,\
00,37,00,34,00,35,00,37,00,38,00,36,00,33,00,30,00,36,00,38,00,d9,07,05,00,\
03,00,06,00,11,00,37,00,39,00,61,02,3c,00,00,00,7f,d7,10,0f,8b,26,e5,7d,b4,\
06,99,8f
HKLM,"%Key4%","MLO",1

[ShotB.changed]
HKLM,"%Key5%","bin",1,be,18,84,67,12,14,ad,ab,48,e2,49,e6,4f,ee,41,e7,41,e7,41,\
e7,41,e7,41,e7,05,ae,e5,10,fe,51,fa,51,25,ae,85,50,05,ae,05,fd,41,e7,c1,e7,\
40,e7,41,e7,2c,8a,38,82,33,94,1f,b7,02,b4,05,a8,6c,aa,0c,be,41,e7,41,e7,41,\
e7,41,e7,41,e7,41,e7,41,e7,41,e7,13,82,35,86,28,8b,41,e7,41,e7,41,e7,41,e7,\
41,e7,41,e7,41,e7,41,e7,41,e7,41,e7,41,e7,41,e7,41,e7,41,e7,41,e7,41,e7,41,\
e7,41,e7,41,e7,41,e7,41,e7,41,e7,41,e7,be,18,41,e7,74,c9,74,c9,71,c9,75,d3,\
71,d7,41,e7,39,e3,9f,93,1d,ed,41,e7,1d,ed,41,e7,1d,ed,41,e7,41,e7,41,e7,00,\
00,00,00,53,22,83,64
HKLM,"%Key6%","Seed",1,17,16,4f,e5,20,d9,a6,10,13,c3,00,b8,9a,26,35,79,1e,d5,\
6a,27,f8,1d,94,f5,88,68,19,a9,cf,d9,45,6e,94,4b,99,df,eb,f0,d2,b6,83,40,25,\
87,58,44,d0,c1,2e,d4,1e,cd,b6,64,3a,bb,8f,5c,af,48,22,4e,04,13,39,42,0e,2b,\
6f,ee,be,dc,b7,52,a6,a7,da,de,bc,52
HKLM,"%Key7%","TracesProcessed",0x10001,120
HKU,"%Key8%","Cookies",,"C:\Documents and Settings\LocalService\Cookies"
HKU,"%Key8%","Cache",,"C:\Documents and Settings\LocalService\Impostazioni locali\Temporary Internet Files"
HKU,"%Key8%","History",,"C:\Documents and Settings\LocalService\Impostazioni locali\Cronologia"
HKU,"%Key9%","SavedLegacySettings",1,46,00,00,00,03,00,00,00,09,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
HKU,"%Key10%","Cookies",,"C:\Documents and Settings\LocalService\Cookies"
HKU,"%Key10%","Cache",,"C:\Documents and Settings\LocalService\Impostazioni locali\Temporary Internet Files"
HKU,"%Key10%","History",,"C:\Documents and Settings\LocalService\Impostazioni locali\Cronologia"
HKU,"%Key11%","SavedLegacySettings",1,46,00,00,00,03,00,00,00,09,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

[strings]
Key1="SOFTWARE\Classes\SOFTWARE\Symantec\6.5"
Key2="SOFTWARE\Microsoft\ESENT\Process\VProSvc\DEBUG"
Key3="SOFTWARE\Microsoft\Windows\CurrentVersion\MCD"
Key4="SOFTWARE\Symantec\Backup Exec System Recovery\8.5"
Key5="SOFTWARE\Classes\.wid"
Key6="SOFTWARE\Microsoft\Cryptography\RNG"
Key7="SOFTWARE\Microsoft\Windows NT\CurrentVersion\Prefetcher"
Key8=".DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders"
Key9=".DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections"
Key10="S-1-5-18\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders"
Key11="S-1-5-18\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections"

[joakim]

Joakim - from my experience wmi-support is not required for dotnet2 - at least not in 2k3

What I meant about wmi was not related to dotnet. You see some of the install of drivers (like I do with this one and a couple of the driver on ws652, that means NOT using drv_ctl) will require wmi as it queries system information through that service. Can't remember which one it was though.

So with wmi missing, not all the drivers/services will install correctly.

One more note;
The package makes use of vss in its backup procedure. Without it the app will not even detect the local system. Actually it's not real vss running, because that would also require comsysapp installed and running (and getting that one running is even harder, that's why I thought it was almost impossible to get this kind of app running in PE). Therefore vss may seem to work, but it fails to do backups that require real vss. You will notice the difference when launching different backups. You will be able to create backups of local disks mounted if no programs are running from them/no files open or being used, but you will not be able to create a backup of your ramdisk (which in your case is R:\ and a local vmdk). That's the reason why I brought up and mentioned comsysapp/msdtc as being the root of the problem when this app was discussed earlier. I still have some untested theories, but time really prevents any actual work...

Joakim

[risolutore]

the Utility folder and the Packages folder can be deleted since contain the installation package and the recovery support tools. So can be minimized space on Hd.

[joakim]

This is what changed in my activation procedure on BESR....

The activation stuff is written into %allusersprofile% and is gone when rebooted (if it resides on a ramdisk that is reset).

Joakim

[Lancelot]

@sanbarrow
you are lucky peter psc dont create a topic "Fundemantals of moa" around .
yep since my last build your automatization improved
yep i understand what you do to gather dotnet pack
same method with full automatic feature available with livexp but never used for that purpose, can be implemented later for dotnet etc. (added todo list, I am not galapo)
nope i was not very successfull with moa, moa needs a lot of reading for me which means a lot time (i did once with very old moa ), well i love LiveXP

@joakim
guessing you are renaming inside .reg file to have independent source. I hope there are no entries around that cant work this way.!!!!
please check env_fix.reg, seems to me it add wrong registry with wrong drive letter for livexp
X:\documents and settings.... --> B:\documents and settings.....
probably with some other reg settings, this was the reason my junction test working better on my previous trials !


@all

after making many many many many test builds yesterday (bootsdi.img with 460MB ntfs compressed - ram 800MB virtualbox and not a super pc) i give up
wmi: we have fully operational wmi script for xp-2k3. I tested with source 2k3sp2 and works good. (ps: CrystalDiskInfo strickly requires wmi and working)

i test with
vcregpatch+vc2005sp1 redist (VCREDIST_X86.EXE)+NETFX20SP1_X86.EXE ---> registervss -- ghost14.exe
or
vcregpatch+vc_patcher_v1002.rar+dotnet2_xp-installrite_61Mb ---> registervss -- ghost14.exe

(all tests made without preregistered wmi..)

always same problem, norton ghost service (vprosvc) dont work.

besides i tested many things (ps: .net setup dont like assembly folder junctioned before installing )

okey here are something for others test trials:
in case of wmi doubts, here is CrystalDiskInfo script to test if wmi fully working
http://apps.winbuild..._Req_wmi.script

Here is a script i made to be sure all required files for ghost14 are in the build, use it in your builds (only required files from sourcecd, box/opendir used only for saving purposes and registry entries in script are not used by script.)
http://lancelot.winb...ODR_Ghost14.rar

Easyway to testers: enable LODR_Ghost14.script , make a big bootsdi build,
get your ghost14 lodr package from, dotnet2, vc2005 into a folder
copy that folder inside the iso, open your virtual machine, copy ghost14 lodr from iso to virtual harddrive .... rest is up to you Good luck.
(ps: yep, method can be enchanced by our advanced users, just wrote an easy understandable way)

I guess enough for me for a while , i will test later with next generation LiveXP, waiting good news from fxscprt .


AND
because i am not sure which entries to be used only for dotnet2sp1 by comparing reg inputs (too many to eliminate not good ones if exists)
if you have one , can someone send a reg file prepared for X:\i386\... (dotnet2sp1_2k3sp2_enu.reg or... !!)
so i can make a dotnetsp1 script for future trials to make faster tests.


cu

[joakim]

Ghost or Backup Exec System Recovery?

Is there any difference?

A loader for besr853 is finished and the funny thing is that ghost 14 runs with the loader and its configuration for besr853...

So basically same loader will do for both of them.

But the license may look a little bit weird...




Joakim

[risolutore]

great to see BESR 8.5x workingin e preinstallation environment, gotta have it
I still use the ghost32 :-(( and is not possible to do incremental backup..and I started to use the latest powerquest v2i, but sometimes fails to open the v2i created with ghost 14, probably the change from powerquesto to symanxxx introduce some bugs
sometimes I use to do a pqi file, than I convert with the recovery pojnt browser but it takes too long.
so actually we are ready for a script for vistaPe? I read all posts, and dowloaded the dotnet2.0 65Mb file and the ladr for ghost.. But I lack some other instruction to do my homework )
@joakim can you introduce me to the secret art of getting BESR or Ghost14 working in Vistape or in LiveXP??

[joakim]

@joakim can you introduce me to the secret art of getting BESR or Ghost14 working in Vistape or in LiveXP??

Sure, I'll put it all together in a document and do my best at explaining how it's done with different OS's.

The main problem is to have all the dependencies present and the requirements met.

I repeat myself when saying these two LODR packages may only serve as a proof it's possible, and nothing more. It's bigtime bloatware!

Joakim

[joakim]

besr853_LODR_v2.0.0.1.rar
ghost14_LODR_v2.0.0.1.rar
dotnet2_livexp_2k3.rar(28Mb)


Two almost identical packages finished, one for each app. It's still not gonna be easy to get it running correctly, but I've supplied some tools to assist:

- batch for vss
- batch for winmgmt (wmi)
- dotnet2 package (2 batches - 1 for use with ntfs and 1 for use with non-ntfs) 28 Mb.

It works like a charm on MOA, but something is missing on LiveXP that prevents it from detecting any local drives. May I suggest that LiveXP expand their core system a little bit, so that it becomes a little bit more flexible. Think of it like an investment that will pay off in the future. Just invest some Mb's, it wouldn't hurt todays powerful machines. VistaPE works but is tricky..

The most important change in this version was the addition of a 2 kb text file, Base.properties, that is very important to have present in the Shared folder. The loader takes care of it (it is not visible when extracting the main installer).

Backup Exec System Recovery can be downloaded from Symantec's site as a zip archive at a massive 272 Mb. Unzip the archive and place the get_files_besr853.cmd and exclude_besr853.txt inside the directory "BESR853_AllWin_Multilingual_Prod\Install"

Joakim

[Lancelot]

but something is missing on LiveXP that prevents it from detecting any local drives. May I suggest that LiveXP expand their core system a little bit, so that it becomes a little bit more flexible. Think of it like an investment that will pay off in the future. Just invest some Mb's, it wouldn't hurt todays powerful machines.

Not the core (@peter psc: No peter, it is not about core, joakim is new LiveXP user), Default LiveXP build may include your suggestions to support "general LODR". The unfinished topic of the lodr resulting with lodr script prepared for this reason

I will test on LiveXP with 2k3sp2 source + your suggestions when i come back.

CU

[joakim]

New improved dotnet2 package with 3 batches;

3 ways of adding (hotplugging) dotnet2 to a running windows livecd based on xp/2k3.

1. Execute for_ntfs.cmd. Will make junction points inside %SystemRoot% that points to externally located directories. Will only work on ramloading build with ntfs formatted ramdisks. Will copy only 2 Mb into %SystemRoot%.

2. Execute non_ntfs.cmd. Will be the same as an Installrite kit as it copies everything into %SystemRoot%. Will require about 92 Mb of free space on the systemdrive. To be used in companion with File Based Write Filter (FBWF) or Enhanced Write Filter (EWF).

3. Execute split_install.cmd. Copies only the assembly and winsxs directories into %SystemRoot%. Leaves the Microsoft.NET directory out of the systemdrive and therefore only requires 41 Mb of free space on the systemdrive (X:\). The path to the Microsoft.NET directory is currently hardcoded to "C:\LODR\dotnet2\Microsoft.NET" but can tweaked easily. If so, then open the file dotnet2_split.reg and replace the string C:\\LODR\\dotnet2\\Microsoft.NET with what is wanted.

The binaries have been upx'ed and tested, and it works. Confirmed working on LiveXP with 2k3 sources, BartPE with xpsp2 sources, and MOA with 2k3 sources.

Joakim


dotnet2.rar

[Lancelot]

Hi joakim

Thanks a lot for dotnet and all others, luckly today i was free to test, tested with 2k3sp1 source and some various combinations, I still fail with ghost14 with usual reasons !! sth missing !!
Maybe setting %programfiles% to programs needed ! or not ! (not tested) -> if yes than bad for lodr package !
at least this script would help others to make wmi and vss files (files only) ready on LiveXP so one can register with wmi and vss batches you put (well sorry if sth missing i am too scattered today)

[codebox] [main] Title=LODR_Ghost14 Beta Description= Selected=True Level=5 Version=2 Download_Level=1 Author= Credits= [process] // from joakim batch Require_File,xolehlp.dll // joakim lodr pack requires xcopy Require_File,xcopy.exe // // lodctr required by .net installation require_file,lodctr.exe // lodctr requires loadperf require_file,loadperf.dll // // VPROSVC dependencies Require_File,cdfview.dll require_file,inetcomm.dll require_file,LINKINFO.DLL require_file,MOBSYNC.DLL require_file,MSHTML.DLL require_file,MSRATING.DLL require_file,PRINTUI.DLL require_file,QUERY.DLL require_file,SCECLI.DLL require_file,W32TOPL.DLL require_file,WINSCARD.DLL require_file,MSGINA.DLL require_file,Hlink.DLL require_file,imgutil.DLL require_file,MSOERT2.DLL // VPROSVC dependencies end // require_file,grpconv.exe require_file,DBGHELP.DLL require_file,vss_ps.dll Require_File,OLE32.DLL Require_File,OLEAUT32.DLL Require_File,ATL.DLL Require_File,eventcls.dll Require_File,vss_ps.dll Require_File,es.dll Require_File,stdprov.dll // require_file,msxml.dll // extra require_file,msxmlr.dll require_file,msxml2.dll // extra require_file,msxml2r.dll require_file,msxml3.dll require_file,swprv.dll // extra require_file,msxml3r.dll require_file,vssvc.exe // // from copy_files_wmi_2k3.cmd list of joakim require_file,ncobjapi.dll require_file,faultrep.dll require_file,loadperf.dll require_file,WMISCMGR.DLL require_file,WMI.DLL require_file,WMIMGMT.MSC require_file,cmprops.dll require_file,licwmi.dll require_file,mmfutil.dll require_file,servdeps.dll require_file,ncobjapi.dll // CopyOrExpand,"%source_win%\swprv.dll","%target_sys%" CopyOrExpand,"%source_win%\vss_ps.dll","%target_sys%" CopyOrExpand,"%source_win%\vssapi.dll","%target_sys%" CopyOrExpand,"%source_win%\vssvc.exe","%target_sys%" CopyOrExpand,"%source_win%\vssadmin.exe","%target_sys%" CopyOrExpand,"%source_win%\eventcls.dll","%target_sys%" IniRead,"%ProjectInfo%","OS","ServicePack","%SP%" If,%OS%%SP%,Equal,XPSP3,Require_File,msxml6.dll If,%OS%%SP%,Equal,XPSP3,Require_File,msxml6r.dll If,%OS%,Equal,W2003,Begin CopyOrExpand,"%source_win%\vss_ddu.dll","%target_sys%" CopyOrExpand,"%source_win%\vssddups.dll","%target_sys%" CopyOrExpand,"%source_win%\vssui.dll","%target_sys%" CopyOrExpand,"%source_win%\vsswmi.dll","%target_sys%" Set,"%dir%","%target_sys%\wbem" DirMake,"%dir%" CopyOrExpand,"%source_win%\vss.mof","%dir%" CopyOrExpand,"%source_win%\vss.mfl","%dir%" End[/codebox] Maybe (not sure): after installing BESR to my hostos i get bootsdi fails similar to yours ! (maybe related to BESR maybe not, i need to restore os to be sure and some tests....). Now Bootsdi script not working at all . Well not sure about what is going on and too tired being bad guy on boot-land reporting/finding things. For Boot-sdi Maybe time come to change vdk to imdisk or filedisk , or maybe another wb math problem............ Well sorry, mostly being the bad guy around make me tired especially these days, Like once but opposite of jacklaz post, back to cave.

Thanks a lot on keeping "General LODR" idea alive.
CU

[dera]

after installing BESR to my hostos i get bootsdi fails

Yes,
I have the same experience after Ghost 14 installed on my host

[Lancelot]

dera

Thanks a lot for confirmation, this is really badddd news after many things done for vdk
Since using real hd image may advantages in future I believe vdk is used as an investment for requests and not mandatory for bootsdi.

Time to use imdisk !!

I would like to use vdk , for 2 reasons: 1) no installation required, 2) real hd image investment

I hope a workaround can be found for vdk ????

[joakim]

Hey, incase you did not notice, there is a batch included to ripp the main installer (so you do not have to do a real install on the host).

I can very the bootsdi issue too. Currently I'm working on some slightly different way of automating this step (autoit/vdk). That is for moa, but should not matter as it can be adapted elsewhere.

@LiveXP team;
What is the exact commands used during the image creation/mounting/formatting/filecopying/unmounting?

Joakim

[joakim]

The issue is not LiveXP specific as MOA users also face the same issue when creating ramloading images.

I believe it can be worked around by using a different set of commands. The reason why I believe this is because the procedure works fine multiple times in a row if done manually...

Joakim

[Lancelot]

@Joakim

yep, just for curiosity i installed to my hostos, than notice the vdk error with bootsdi and remember your report!

@LiveXP team;
What is the exact commands used during the image creation/mounting/formatting/filecopying/unmounting?

vdk usage is simple, you can get many examples around.

here is a nice tidy one

fsutil.exe file createnew test.img 32901120

vdk.exe open * test.img /rw /p:0

Echo format F: /FS:NTFS /V:Test /X /force

rem filecopy here

pause

VDK.EXE STOP

VDK.EXE REMOVE

VDK.EXE VIEW test.img

cmd

on bootsdi of livexp project as far as i notice these 3 used:

VDK.EXE START
VDK.EXE Open xxx.img /rw /p:0
VDK.EXE Remove

Last notice/reminder: vdk is not mandatory, imdisk can be used for same purposes, an example: bootsdi of nativeex uses imdisk (so far i read ).

Rest is a long way for you, you need .img size to create with fsutil, and if ntfs compress used you need other copy utilities..........And if you need to add some options you need to make a gui for it.... whyyyy If your intention is using LiveXP bootsdi script on other projects, instead of rewriting, you can use winbuilder for same task !. Winbuilder is "The Batcher" and scripts are ready. Flexxxxyyyyy :


@dera:
hoping you are using xp environment. Can you give a simple batch (.cmd) example to reproduce on basics. Maybe above batch or maybe other !


@all:
since post44 topic is about vdk.exe and some symantec guys making ugly things resulting vdk.exe not working.

ps: i will be away for some hours, cu soon.

[dera]

Hi Lancelot

my host is XP SP3 Hungarian
at me the 'VDK STOP' and 'VDK REMOVE' commands are problematic

c:\wb076\Projects\Tools\Vdk>vdk_WB.exe stop

Virtual Disk Driver for Windows version 3.1(WB)

http://chitchat.at.infoseek.co.jp/vmware/

Recompiled for WinBuilder by psc



Closing the image on the virtual disk 0...The drive is empty.

Closing the image on the virtual disk 1...The drive is empty.

Closing the image on the virtual disk 2...The drive is empty.

Closing the image on the virtual disk 3...The drive is empty.

Stop operation has succeeded, but something

is preventing the driver from actually stopping.

You may need to reboot the system before restarting the driver.





c:\wb076\Projects\Tools\Vdk>vdk_WB.exe remove

Virtual Disk Driver for Windows version 3.1(WB)

http://chitchat.at.infoseek.co.jp/vmware/

Recompiled for WinBuilder by psc



Failed to stop the Virtual Disk Driver.

Some programs may be using the virtual drive.

after uninstalled the 'Ghost 14' this vdk problem disappears

[Lancelot]

Thanks dera

here is result with 2k3x64 with using x64 version of vdk.exe after using once

D:\vdk64>vdk stop

Virtual Disk Driver for Windows version 3.1

http://chitchat.at.infoseek.co.jp/vmware/



Failed to stop the Virtual Disk Driver.

Some programs may be using the virtual drive.



D:\vdk64>vdk remove

Virtual Disk Driver for Windows version 3.1

http://chitchat.at.infoseek.co.jp/vmware/



Failed to stop the Virtual Disk Driver.

Some programs may be using the virtual drive.

totally: vdk from psc, vdk x64 from sherpya failsare prohibited by the OS to free a driver service which is in use anywhere..
(and i believe original vdk fails will be prohibited by the OS to free a driver service which is in use anywhere.. too)

Changing folder name dont help to solve !

Also i accidentally found another thing !
During test install of besr I had an (only) ufd connected to mob, i was playing with its chip these days , anyway after restart windows couldnt start. desktop came but executing explorer.exe dont give any gui, any application which likes to read drives (drive letters) didnt work. After unplugging ufd things back to normal.

maybe stop & remove vdk manually , or maybe stopping sth on besr for vdk operation etc etc.

ps: Imdisk not effected !

Maybe better to email symantec guys to fix their things, any volunteer .


My only concern is LiveXP using vdk with reasons written before , today symantec tomorrow tuctec can cause such an issue (or maybe Mista8 sp2). So far we have only 1 and 1 is good for exception, 2 is too much. I hope you agree with me (ps: i dont like to work on bootsdi script too :> and even we remove vdk i would like it optional on bootsdi for future references/requirements)



@joakim

For vdk please Check these
http://www.boot-land...?...=1662&st=59
http://www.boot-land...?...1580&st=216
http://www.911cd.net...o...21242&st=34