83 replies to this topic

[JonF]

[quote name='Lancelot' post='52146' date='Dec 17 2008, 02:09 PM']here is a batch file example for you to try

test.cmd

Microsoft Windows [Version 6.0.6001]Copyright © 2006 Microsoft Corporation.  All rights reserved.E:\Temporary>testE:\Temporary>VDK.EXE STOPVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]The Virtual Disk Driver is not installed.E:\Temporary>VDK.EXE REMOVEVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]The Virtual Disk Driver is not installed.E:\Temporary>del /q /f /a "test.img"E:\Temporary>fsutil.exe file createnew test.img 32901120File E:\Temporary\test.img is createdE:\Temporary>pausePress any key to continue . . .E:\Temporary>vdk.exe open * test.img /rw /p:0Virtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Installed the Virtual Disk Driver.Started the Virtual Disk Driver.Failed to decide type of &#39;test.img&#39;.Open as a simple sector image file.Virtual Disk 0Access Type     : WritableDisk Capacity   : 64260 sectors (31 MB)Geometry        : © 31 * (H) 64 * (S) 32Number Of Files : 1  Type     Size    Path -------  -------  ----  FLAT      64260  E:\Temporary\test.imgPartitions      :      #   Start Sector    Length in sectors    Type     --   ------------  ---------------------  ---- M:   0              0      64260 (    31 MB)  <disk>E:\Temporary>pausePress any key to continue . . .E:\Temporary>VDK.EXE STOPVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Closing the image on the virtual disk 0...The image is closed.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.Failed to stop the Virtual Disk Driver.Some programs may be using the virtual drive.E:\Temporary>VDK.EXE REMOVEVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]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.Failed to stop the Virtual Disk Driver.Some programs may be using the virtual drive.E:\Temporary>testE:\Temporary>VDK.EXE STOPVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]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.Failed to stop the Virtual Disk Driver.Some programs may be using the virtual drive.E:\Temporary>VDK.EXE REMOVEVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]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.Stopped the Virtual Disk Driver.Uninstalled the Virtual Disk Driver.E:\Temporary>del /q /f /a "test.img"E:\Temporary>fsutil.exe file createnew test.img 32901120File E:\Temporary\test.img is createdE:\Temporary>pausePress any key to continue . . .E:\Temporary>vdk.exe open * test.img /rw /p:0Virtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Installed the Virtual Disk Driver.Started the Virtual Disk Driver.Failed to decide type of &#39;test.img&#39;.Open as a simple sector image file.Virtual Disk 0Access Type     : WritableDisk Capacity   : 64260 sectors (31 MB)Geometry        : © 31 * (H) 64 * (S) 32Number Of Files : 1  Type     Size    Path -------  -------  ----  FLAT      64260  E:\Temporary\test.imgPartitions      :      #   Start Sector    Length in sectors    Type     --   ------------  ---------------------  ---- M:   0              0      64260 (    31 MB)  <disk>E:\Temporary>pausePress any key to continue . . .E:\Temporary>VDK.EXE STOPVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Closing the image on the virtual disk 0...The image is closed.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.Stopped the Virtual Disk Driver.E:\Temporary>VDK.EXE REMOVEVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Uninstalled the Virtual Disk Driver.E:\Temporary>testE:\Temporary>VDK.EXE STOPVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]The Virtual Disk Driver is not installed.E:\Temporary>VDK.EXE REMOVEVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]The Virtual Disk Driver is not installed.E:\Temporary>del /q /f /a "test.img"E:\Temporary>fsutil.exe file createnew test.img 32901120File E:\Temporary\test.img is createdE:\Temporary>pausePress any key to continue . . .E:\Temporary>vdk.exe open * test.img /rw /p:0Virtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Installed the Virtual Disk Driver.Started the Virtual Disk Driver.Failed to decide type of &#39;test.img&#39;.Open as a simple sector image file.Virtual Disk 0Access Type     : WritableDisk Capacity   : 64260 sectors (31 MB)Geometry        : © 31 * (H) 64 * (S) 32Number Of Files : 1  Type     Size    Path -------  -------  ----  FLAT      64260  E:\Temporary\test.imgPartitions      :      #   Start Sector    Length in sectors    Type     --   ------------  ---------------------  ---- M:   0              0      64260 (    31 MB)  <disk>E:\Temporary>pausePress any key to continue . . .E:\Temporary>VDK.EXE STOPVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Closing the image on the virtual disk 0...The image is closed.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.Failed to stop the Virtual Disk Driver.Some programs may be using the virtual drive.E:\Temporary>VDK.EXE REMOVEVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]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.Failed to stop the Virtual Disk Driver.Some programs may be using the virtual drive.E:\Temporary>

[Lancelot]

JonF

sorry for typo, and sorry i sent before testing, but still my finding is true with 1 adding, format line.

i put XX: for drive letter, change as you wish, be verry carelful
you will see it works only 1 time and changing folder name makes it work again as i wrote before


re-written in further post

[was_jaclaz]

Also, if you add to it a line like:
VDK.EXE DRIVER

you will see something like:

Virtual Disk Driver for Windows version 3.1
http://chitchat.at.i...k.co.jp/vmware/

Driver File : C:\Downloaded\VDK\vdk.sys

Driver Version : 3.1

Start Type : DEMAND

Driver Status : STOP_PENDING

Number of Disks : 4

Virtual Disk Driver for Windows version 3.1
http://chitchat.at.i...k.co.jp/vmware/

The Virtual Disk Driver is not running.

jaclaz

[Lancelot]

Jaclaz

no, i change batch like this:

VDK.EXE STOPVDK.EXE REMOVEdel /q /f /a "test.img"fsutil.exe file createnew test.img 32901120pausevdk.exe open * test.img /rw /p:0format XX: /Q /FS:NTFS /V:Test /X /forcepauseVDK.EXE STOPVDK.EXE REMOVEECHO repeatVDK.EXE STOPVDK.EXE REMOVEVdk.exe driverdel /q /f /a "test.img"fsutil.exe file createnew test.img 32901120pausevdk.exe open * test.img /rw /p:0format XX: /Q /FS:NTFS /V:Test /X /forcepauseVDK.EXE STOPVDK.EXE REMOVEECHO repeatVDK.EXE STOPVDK.EXE REMOVEVdk.exe driverdel /q /f /a "test.img"fsutil.exe file createnew test.img 32901120pausevdk.exe open * test.img /rw /p:0format XX: /Q /FS:NTFS /V:Test /X /forcepauseVDK.EXE STOPVDK.EXE REMOVEECHO repeatVDK.EXE STOPVDK.EXE REMOVEVdk.exe driverdel /q /f /a "test.img"fsutil.exe file createnew test.img 32901120pausevdk.exe open * test.img /rw /p:0format XX: /Q /FS:NTFS /V:Test /X /forcepauseVDK.EXE STOPVDK.EXE REMOVEECHO repeatVDK.EXE STOPVDK.EXE REMOVEVdk.exe driverdel /q /f /a "test.img"fsutil.exe file createnew test.img 32901120pausevdk.exe open * test.img /rw /p:0format XX: /Q /FS:NTFS /V:Test /X /forcepauseVDK.EXE STOPVDK.EXE REMOVEexit

and after 1st format success, others act like this:Problem is, when format ntfs used, i cant use format ntfs again.with format fat/fat32 no such problem, if above code /FS:NTFS changed to /FS:FAT , it works without problem.That is why wimpack+bootsdi works with 1st boot now, because wimpack uses /FS:FAT (or /FS:FAT32) and at bootsdi step /FS:NTFS used for the 1st and last time on this boot.Also if test.img on above code changed to test1.img , test2.img ..... , it still dont workBetter to change folder name of vdk.exe which makes it again work one time

[was_jaclaz]

What happens with FULL paths to BOTH vdk.exe and test.img?

I seem to remember a similar problem having two instances of VDK.SYS on different (arbitrary) directories.

Maybe it's a PATH problem.

What if instead of the asterisk you use "full" syntax, something like:
X:\whatever\vdk.exe OPEN 0 "X:\whatever\test.img" /RW /p:0 /l:K

I.e. what is the "item" that creates the error:
"The system cannot find the file specified"

• vdk.exe
• vdk.sys
• *
• test.img
• the automatic drive letter assignment

jaclaz

[Lancelot]

Jaclaz

using FULL paths dont solve, look:

C:\test7>C:\test7\VDK.EXE STOPVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]The Virtual Disk Driver is not installed.C:\test7>C:\test7\VDK.EXE REMOVEVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]The Virtual Disk Driver is not installed.C:\test7>del /q /f /a C:\test7\test1.imgC:\test7>fsutil.exe file createnew test1.img 32901120File C:\test7\test1.img is createdC:\test7>pausePress any key to continue . . .C:\test7>C:\test7\VDK.EXE open * C:\test7\test1.img /rw /p:0Virtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Installed the Virtual Disk Driver.Started the Virtual Disk Driver.Failed to decide type of &#39;C:\test7\test1.img&#39;.Open as a simple sector image file.Virtual Disk 0Access Type     : WritableDisk Capacity   : 64260 sectors (31 MB)Geometry        : © 31 * (H) 64 * (S) 32Number Of Files : 1  Type     Size    Path -------  -------  ----  FLAT      64260  C:\test7\test1.imgPartitions      :      #   Start Sector    Length in sectors    Type     --   ------------  ---------------------  ---- F:   0              0      64260 (    31 MB)  <disk>C:\test7>format F: /FS:NTFS /V:Test /X /forceThe type of the file system is RAW.The new file system is NTFS.Formatting 31MCreating file system structures.Format complete.     32128 KB total disk space.     29876 KB are available.C:\test7>pausePress any key to continue . . .C:\test7>C:\test7\VDK.EXE STOPVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Closing the image on the virtual disk 0...The image is closed.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.Stopped the Virtual Disk Driver.C:\test7>C:\test7\VDK.EXE REMOVEVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Uninstalled the Virtual Disk Driver.C:\test7>ECHO repeatrepeatC:\test7>C:\test7\VDK.EXE STOPVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]The Virtual Disk Driver is not installed.C:\test7>C:\test7\VDK.EXE REMOVEVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]The Virtual Disk Driver is not installed.C:\test7>C:\test7\VDK.EXE driverVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Driver Status   : NOT INSTALLEDC:\test7>del /q /f /a C:\test7\test2.imgCould Not Find C:\test7\test2.imgC:\test7>fsutil.exe file createnew C:\test7\test2.img 32901120File C:\test7\test2.img is createdC:\test7>pausePress any key to continue . . .C:\test7>C:\test7\VDK.EXE open * C:\test7\test2.img /rw /p:0Virtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Installed the Virtual Disk Driver.Failed to start the Virtual Disk Driver.The system cannot find the file specified.C:\test7>format F: /FS:NTFS /V:Test /X /forceSpecified drive does not exist.C:\test7>pausePress any key to continue . . .

using quote for vdk.exe open line dont work:

C:\test8>C:\test8\VDK.EXE STOPVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]The Virtual Disk Driver is not installed.C:\test8>C:\test8\VDK.EXE REMOVEVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]The Virtual Disk Driver is not installed.C:\test8>del /q /f /a C:\test8\test1.imgC:\test8>fsutil.exe file createnew test1.img 32901120File C:\test8\test1.img is createdC:\test8>pausePress any key to continue . . .C:\test8>C:\test8\VDK.EXE open * "C:\test8\test1.img" /rw /p:0Virtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Installed the Virtual Disk Driver.Started the Virtual Disk Driver.Failed to decide type of &#39;C:\test8\test1.img&#39;.Open as a simple sector image file.Virtual Disk 0Access Type     : WritableDisk Capacity   : 64260 sectors (31 MB)Geometry        : © 31 * (H) 64 * (S) 32Number Of Files : 1  Type     Size    Path -------  -------  ----  FLAT      64260  C:\test8\test1.imgPartitions      :      #   Start Sector    Length in sectors    Type     --   ------------  ---------------------  ---- F:   0              0      64260 (    31 MB)  <disk>C:\test8>format F: /FS:NTFS /V:Test /X /forceThe type of the file system is RAW.The new file system is NTFS.Formatting 31MCreating file system structures.Format complete.     32128 KB total disk space.     29876 KB are available.C:\test8>pausePress any key to continue . . .C:\test8>C:\test8\VDK.EXE STOPVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Closing the image on the virtual disk 0...The image is closed.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.Stopped the Virtual Disk Driver.C:\test8>C:\test8\VDK.EXE REMOVEVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Uninstalled the Virtual Disk Driver.C:\test8>ECHO repeatrepeatC:\test8>C:\test8\VDK.EXE STOPVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]The Virtual Disk Driver is not installed.C:\test8>C:\test8\VDK.EXE REMOVEVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]The Virtual Disk Driver is not installed.C:\test8>C:\test8\VDK.EXE driverVirtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Driver Status   : NOT INSTALLEDC:\test8>del /q /f /a C:\test8\test2.imgC:\test8>fsutil.exe file createnew C:\test8\test2.img 32901120File C:\test8\test2.img is createdC:\test8>pausePress any key to continue . . .C:\test8>C:\test8\VDK.EXE open * "C:\test8\test2.img" /rw /p:0Virtual Disk Driver for Windows version 3.1[url="http://chitchat.at.infoseek.co.jp/vmware/"]http://chitchat.at.infoseek.co.jp/vmware/[/url]Installed the Virtual Disk Driver.Failed to start the Virtual Disk Driver.The system cannot find the file specified.C:\test8>format F: /FS:NTFS /V:Test /X /forceSpecified drive does not exist.C:\test8>pausePress any key to continue . . .

I.e. what is the "item" that creates the error:

As shown in picture and from codebox, VDK.EXE opencreates this error when 2nd timeIt is a vista32sp1 thing, this error dont happens with vista32sp0,xp32, xp64 .....

[was_jaclaz]

As shown in picture and from codebox,
VDK.EXE open
creates this error when 2nd time

It is a vista32sp1 thing, this error dont happens with vista32sp0,xp32, xp64 .....

Yep, I have understood that it is VDK OPEN that creates the error, but we are exactly where we were before.


Let's try again:

C:\test8\VDK.EXE REMOVE

C:\test8\VDK.EXE DRIVER

del /q /f /a C:\test8\test2.img

fsutil.exe file createnew C:\test8\test2.img 32901120

PAUSE

DIR C:\test8\test*.*

C:\test8\VDK.EXE INSTALL

C:\test8\VDK.EXE DISK 1

C:\test8\VDK.EXE START

PAUSE

C:\test8\VDK.EXE open 0 "C:\test8\test2.img" /rw /p:0 /l:Z

PAUSE

DIR Z:

PAUSE

Make sure there is a free drive letter Z:\ or change accordingly last line.

What happens?

jaclaz

[Lancelot]

jaclaz

it fails at VDK.EXE START step

C:\test8>C:\test8\VDK.EXE INSTALL
Virtual Disk Driver for Windows version 3.1
http://chitchat.at.i...k.co.jp/vmware/

Installed the Virtual Disk Driver.

C:\test8>C:\test8\VDK.EXE DISK 1
Virtual Disk Driver for Windows version 3.1
http://chitchat.at.i...k.co.jp/vmware/

The number of virtual disk device is set to 1.
It will take effect the next time the driver is started.

C:\test8>C:\test8\VDK.EXE START
Virtual Disk Driver for Windows version 3.1
http://chitchat.at.i...k.co.jp/vmware/

Failed to start the Virtual Disk Driver.
The system cannot find the file specified.

C:\test8>PAUSE

[was_jaclaz]

I seem to remember a similar problem having two instances of VDK.SYS on different (arbitrary) directories.

Maybe it's a PATH problem.

it fails at VDK.EXE START step

Which should mean that somehow the VDK.EXE gets "confused" about location of VDK.SYS, or that something prevents re-accessing the same VDK.SYS instance....

Can you check before and after each step the contents of:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VirtualDK

Another test could be to add in the batch:

md newvdk

cd newvdk

copy ..\VDK.EXE

copy ..\VDK.SYS

in second instance, as to install a new copy of VDK.SYS and see what happens....

jaclaz

[JonF]

no, i change batch like this:

OK, now I can reproduce your results. FWIW.

It sure seems that there must be a cleaner way to do this ... your workaround works, but we still don't know what the core issue is.

[pscEx]

Maybe I'm totally wrong, but I do not understand at all.

Everybody here is speaking about vdk.*

If you look ito the forum's topics, long time ago I made (after changing some mails with the vdk autor) a vdk_wb.* which could be used in our forum.

Some highlights:

• vdk_wb does not disturbe and is not disturbed by any possibly running 'normal' vdk driver
• vdk_wb avoids 'hanging' of WinBuilder when waiting for a user's input because there are some troubles/questions
• ...

In the scripts with vdk issues I never see vdk_wb, only the original vdk

And additional:

Exploring the rules of '64 bit Windows', IMHO: In Billy the Door's 64 bit OSs, as long as there is no 'files system redirection' switched off, WinBuilder will never succeed in using vdk(_WB) to mount something.

Maybe with a supercallifragilisticexpiallgotic batch this can be done.
But is that in the sence of WinBuilder (easy, suited for 'expert-dummies')

Peter

[Lancelot]

psc

again obvious you dont read carelfully

vdk.exe and vdk_wb.exe cause same trouble,

Exploring the rules of '64 bit Windows', IMHO: in 64 bit OSs, as long as there is no 'files system redirection' switched off, WinBuilder will never succeed in using vdk(_WB) to mount something.

no need 'files system redirection' for vdk x64, As you dont need carelfully lets repeat again, i use vdk x64 successfully for a looooooong time in my x64 hostos, and still it is not the subject here.

Maybe with a supercallifragilisticexpiallgotic batch this can be done.
But is that in the sence of WinBuilder (easy, suited for 'expert-dummies')

Better idea is: experts reads more carelfully.



Jaclaz:

you catch sth , shortly:
VDK.EXE REMOVE
dont delete registry key
after changing directory
VDK.EXE REMOVE
successfully deletes registry key

Maybe deleting registry with wb may work

I need some time, vmware collapsed during trials

[pscEx]

Better idea is: experts reads more carelfully.

And 'reporters report more carefully'
If they write about 'vdk_wb.*', they should not write 'vdk.*'
And if they did a test with 'vdk.*' or 'vdk_wb.*' only they should mention in their reports.

As long as 'some 64 bit issues' work at one place, and nobody knows why they are working here, there is no reason to be proud: 'They work everywhere'

OK. I understood that my post has been very misplaced here and I'm not really welcome with my opinion.
I'm trying forget this issue and do nao disturbe your development work any more.

Peter

EDIT: @Nuno: nice (unwanted brazilian) typo with just missing accent

[Lancelot]

Jaclaz

my last post was wrong, it should be reverse, sorry vmware collapsed that time.
Here is the right and detailed one:
In 1st run everthing works nicely and this registry created:





on 2nd run which doesnt work, only this registry created, no enum subkey



i hope this helps?????



Peter,

And 'reporters report more carefully'

Done many times (since 911 topic)

If they write about 'vdk_wb.*', they should not write 'vdk.*'
And if they did a test with 'vdk.*' or 'vdk_wb.*' only they should mention in their reports.

answered in previous post which you dont read carelfully

vdk.exe and vdk_wb.exe cause same trouble

As long as 'some 64 bit issues' work at one place, and nobody knows why they are working here, there is no reason to be proud: 'They work everywhere'

it is totally a different subject out of this topic.

OK. I understood that my post has been very misplaced here and I'm not really welcome with my opinion.

You are always welcome when you read carelfully

I'm trying forget this issue and do nao disturbe your development work any more.

Your choice, i respect that.

[pscEx]

Peter,

Done many times (since 911 topic)

answered in previous post which you dont read carelfully

it is totally a different subject out of this topic.

You are always welcome when you read carelfully

Your choice, i respect that.

I respect that, too.

But allow me one question:

How do you come to a conclusion about vdk_WB.* while NEVER in the post appears:

Virtual Disk Driver for Windows version 3.1(WB)
http://chitchat.at.i...k.co.jp/vmware/
Recompiled for WinBuilder by psc

Peter

[Lancelot]

How do you come to a conclusion about vdk_WB.* while NEVER in the post appears:

answer is simple, AS you DO NOT READ, here is answer: JonF and Dera found out this error when building with winbuilder.exe, which uses vdk_wb.exe which causes same error.

[JonF]

I'm messing with vdk.exe to see if I can figure out why it has difficulty with Vista SP1, but no progres yet. I'll be out of town for the rest of the week and not doing any more on this problem.

I ran built LiveXP on an XP machine, with WIMPack and BootSDI. I ran the BootSDI HDD and USB disk section to set up my flash drive. What do I do with WIMs.vmdk? Copy it to the root of the flash disk?

[Lancelot]

JonF,

copy WIMSs.vmdk to usb:\WIMS\ folder, (as written in "Container name" of wimpack script gui, or you may change "WIMs\WIMs.vmdk" to "BootSDIwims.vmdk" and put BootSDIwims.vmdk to the root of usb)


and here is a temporary solution for vista32sp1: close winbuilder.exe change basedirectory name after each build with bootsdi

[Lancelot]

Hi JonF, dera

I guess i solved the vista32sp1 vdk problem with changing where vdk starts as described before. Made couple of tests with vista32sp1 and my hostos, everthing works fine.

New bootsdi and wimpack scripts are on LiveXP server.

ps: thanks a lot for Peter's patience and tutorial about StrFormat,Date


Merry Christmas

[xylosxot]

I hope that I won't get torched for asking this question...
I've been looking all over the forum and perhaps I've missed what I'm looking for.

I've been endeavoring to edit an existing SDI image. I want to get inside of the image itself.

Is there a tool that I can use to edit the contents of an existing SDI image? If so where can I download it?

Here's my problem and why I'm asking this question.
1. Looking around I've found this discussion area to be the best fitting place to ask such a question.
2. I keep having problems with all of the images generated from Winbuilder freezing in virtual box.
3. I've found one image thus far that does not freeze but there are several annoying things about the image that I don't like and want to change.

Being just a bit more specific about the issue:
I am wanting to know if there's a program that will let me edit an SDI image like UltraISO is able to edit an ISO image. Even if this is not an option what would my options be?

Please be specific and don't be afraid to be technical in your response.

I truly hope someone can be of assistance even if it's just to redirect me if I'm in the wrong spot.

[Lancelot]

Hi xylosxot

Welcome to boot-land

hope that I won't get torched for asking this question..

Nope,

for bootsdi img files, you can use various utilities, a well known example, WinImage. But trying to fix img file would probably fail.

Your report:

2. I keep having problems with all of the images generated from Winbuilder freezing in virtual box.

concerns me, i would like to try to help you, can you answer this questions:

Where/How you get a copy of winbuilder ???
Can you send a log file of a build when error occurs ??
Any problem with creating iso images??

[xylosxot]

I'm not saying no to your help. I definitely appreciate the help and want it. My understanding of things technical runs in a backwards motion. My weird retarded brain picks up things by seeing how they're put together and then I run backwards to the beginning and the understanding of how to do such things becomes clearer. I will later get back with you when I run Winbuilder again.

So that you'll know I've been trying to build images based upon prebuilt projects off of Winbuilder.net. I keep getting the problem with the network install freezing the virtual computer and device detection freezing the virtual computer. Most recently I actually got a BSOD from the virtual computer. So I opt for other alternatives. My understanding of running winbuilder is still basic but I do understand enough to compile the image. So you'll know I do have my personal Xp Pro img copied to my system for faster compilation. Thought, recommendations, counsel, wisdom? Anything you have currently would be helpful.

Thanks so much for the info on WinImage. Shame there's not a freeware version to help. Or is there?

[Lancelot]

xylosxot

i dont know other utilities for .img files than WinImage that has a simple gui, try imdisk http://www.ltr-data..../imdiskinst.exe , imdisk is free. (you will see icon on control panel after installing, for imdisk related questions look here ) , also for other utilities try searching internet

freezing the virtual computer.

issue fixed recently for LiveXP project, update your LiveXP project.


Question4: are you using LiveXP ??

[pscEx]

@xylotxot!

Maybe it depends on my insufficient knowledge of English language, but I do not understand the issue you present here.

Do yo have some troubles with 'WinBuilder does not understand my project' or are you trying to get WinBuilder (forum's) help in a topic where you do not get help anywhere else.

Please try to explain exactly (and in simple words for fools like me as German) what you are looking for.

Peter

[xylosxot]

actually lancelot fixed the problem with my original concern. I wanted to be able to edit an SDI image file. WinImage did the trick. I might buy it since I will have an honest need for it now. Lancelot raised questions about my other problems though.

Freezing of virtualbox computer.
I didn't want to worry about that problem at the moment as winimage will serve as a quick fix for my problem right now.