Jump to content











Photo
- - - - -

[Solved!] zCopy error - Target path Z:\ not found. (Thanks Peter!)


  • Please log in to reply
116 replies to this topic

#76 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 05 March 2008 - 04:54 PM

Many thanks to all for you hard work.
What I must to do now ?
Has already test wb072 and wb073 with zCopy error stable.


Let me first clarify two things:
  • The issue is not caused by zCopy; vdk under certain circumstances cannot work correctly
  • This issue does not depend on WB 074 directly. Maybe there is a bug inside WB074 which also causes other anomalities.
To use the new BootSDI version:
  • If you work with nativeEx_barebone:
    • Click the Download tab
    • In the right, check nativeEx.boot-land.net
    • In the left, check nativeEx_barebone > Finish > Create Image > BootSDI.Script
    • If you do not want them do download, uncheck all other scripts in the left.
    • Download
  • If you work with LiveXP
    • Do the nativeEx_barebone steps above
    • Copy %BaseDir%\Projects\nativeEx_barebone\Finish\2 Create Image\BootSDI.Script %BaseDir%\Projects\LiveXP\Finish\2 Create Image
(I think, that Galapo will copy the new version to the LiveXP server soon)

Peter

#77 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 05 March 2008 - 05:43 PM

Many thanks to all for you hard work.
What I must to do now ?
Has already test wb072 and wb073 with zCopy error stable.

Yes, many thanks Peter :)

@by_rom Glad 072 (073) worked for you; you can download the new BootSDI script here and just copy it into your current build (in this case to: \\Projects\LiveXP\Finish\2 Create Image, where BootSDI resides).

To re-run an existing build with new script(s); delete everything in the build folder except:
Image1.JPG

Add/replace new script(s) and re-run. Everything else stays the same except for the new changes. This works well for adding/changing scripts in an otherwise stable build (not necessarily for troubleshooting deeper issues); hope this helps.

#78 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 05 March 2008 - 06:00 PM

@by_rom Glad 072 (073) worked for you; you can download the new BootSDI script here and just copy it into your current build (in this case to: \\Projects\LiveXP\Finish\2 Create Image, where BootSDI resides).

To re-run an existing build with new script(s); delete everything in the build folder except:
Image1.JPG

Add/replace new script(s) and re-run. Everything else stays the same except for the new changes. This works well for adding/changing scripts in an otherwise stable build (not necessarily for troubleshooting deeper issues); hope this helps.


:(
@Amalux: you successfully continue the way you started in the 'Should we have a "Newbie's" section?' topic.

Peter :)


#79 by_rom

by_rom

    Member

  • Members
  • 88 posts
  •  
    Israel

Posted 05 March 2008 - 06:47 PM

amalux ,psc ,thanks will be tested -)))

#80 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 06 March 2008 - 12:35 AM

A new version of BootSDI.Script is available on the nativeEx server.

Hi Peter,

Thanks for the new version -- works well!

The first line
ShellExecute,Hide,"%VdkExe%","remove"
needs to be changed to
If,ExistFile,"%VdkExe%",CommandShellExecute,Hide,"%VdkExe%","remove"
else the script will have an error the first time it runs.

Regards,
Galapo.

#81 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 06 March 2008 - 01:01 AM

Hi Peter,

Perhaps I was a little premature: subsequent runs are failing. From the commandline, this is what is happening:
C:\_WB\winbuilder\Projects\Tools\Vdk>vdk_wb remove

Virtual Disk Driver for Windows version 3.1(WB)

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

Recompiled for WinBuilder by psc



Uninstalled the Virtual Disk Driver.



C:\_WB\winbuilder\Projects\Tools\Vdk>vdk_wb install

Virtual Disk Driver for Windows version 3.1(WB)

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

Recompiled for WinBuilder by psc



Installed the Virtual Disk Driver.



C:\_WB\winbuilder\Projects\Tools\Vdk>vdk_wb start

Virtual Disk Driver for Windows version 3.1(WB)

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

Recompiled for WinBuilder by psc



Failed to start the Virtual Disk Driver.

The system cannot find the file specified.

Any idea why the driver file isn't being found?

The path in the registry points correctly for me: '\??\C:\_WB\winbuilder\Projects\Tools\Vdk\vdk_WB.sys'.

Thanks,
Galapo.

#82 nikzzzz

nikzzzz

    Frequent Member

  • .script developer
  • 263 posts

Posted 06 March 2008 - 02:36 AM

A new version of BootSDI.Script is available on the nativeEx server.

It contains the recompiled vdk.exe / vdk.sys as vdk_WB.exe / vdk_WB.sys.

Peter

Beautiful work! :)
The small not basic remark:
Run, %ScriptFile %, FreeLetter
It is carried out in sections [Process] and [CreateRAMIso] - one of them superfluous.
Regards !

#83 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 06 March 2008 - 03:52 AM

Perhaps I was a little premature: subsequent runs are failing.

Strange. I rebooted the machine and now repeated runs of the script are successful.

Galapo.

#84 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 06 March 2008 - 07:33 AM

Run, %ScriptFile %, FreeLetter
It is carried out in sections [Process] and [CreateRAMIso] - one of them superfluous.

Thanks :)
Version 048

Peter

#85 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 06 March 2008 - 07:36 AM

Strange. I rebooted the machine and now repeated runs of the script are successful.

Galapo.

I had the same behaviour.
No idea about the reason.

Your suggestion of 'If,ExistFile ... is on the server as version 048

Thanks :)

Peter

#86 by_rom

by_rom

    Member

  • Members
  • 88 posts
  •  
    Israel

Posted 06 March 2008 - 08:17 AM

This screenshots and logo file from bootsdi.script with latest vdk.exe running only.
I think no needs to run all build to see an error.
Also may be I miss something on my settings in bootsdi.script.

#87 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 06 March 2008 - 08:24 AM

This screenshots and logo file from bootsdi.script with latest vdk.exe running only.
I think no needs to run all build to see an error.
Also may be I miss something on my settings in bootsdi.script.


You are still running BootSDI version 044!

Peter

#88 by_rom

by_rom

    Member

  • Members
  • 88 posts
  •  
    Israel

Posted 06 March 2008 - 08:48 AM

Opps.

I'll fix it.

Now I need according log: You need SETUPLDR.BIN of W2003 SP1!
I need some times to get it.

#89 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 06 March 2008 - 06:09 PM

Now I need according log: You need SETUPLDR.BIN of W2003 SP1!
I need some times to get it.


Didn't you have it before?
If yes, maybe there is an issue in my 'detect setupldr.bin' section.

Peter

#90 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 06 March 2008 - 10:03 PM

This screenshots and logo file from bootsdi.script with latest vdk.exe running only.
I think no needs to run all build to see an error.
Also may be I miss something on my settings in bootsdi.script.

by_rom,

I've been running some tests and have not been able to reproduce your error again even with wb074 but as the BootSDI script seems to be undergoing further development, I'm waiting to see what the 'final' outcome is to test the newest version. I do have some observations, though, I'd like to bring to your attention; not saying they're problems necessarily, just things to look at.

1) In the BootSDI script options, you have pointed to a static location for the 'Path to installed vdk.exe'; this will cause problems if your base dir is renamed (shown here as 'wb074') - there is no need to define a path, the script will find vdk.exe in its default location (%basedir%\Projects\Tools\VDK) even if this dialog is left blank and will allow for renaming your base folder.

2) Make sure your W2003 source files are in a folder that never changes or gets renamed, you show this folder as "C:\WinBuilder071_Beta2\server20..." as long as this folder name/location is constant, you're OK but if it changes, make sure you set the new directory in the dialog box. Also, confirm that your source files are the correct versions as stated in the dialog or they won't work.

3) You seem to have an awful lot going on in your system tray! It's best to avoid any unnecessary processes or background programs running while building your project (my system tray is empty while running WinBuilder) even legitimate programs like firewalls and anti-virus can cause issues. It's best to download everything upfront and disconnect from the internet before running WB if your that concerned about mal-ware sneaking in.

BTW, I recommend checking 'Compress RAM drive' option in BootSDI; there's no downside and it cuts about 20-25% off the size of your image. :)

EDIT: just tested new version 48 in wb074 and works great, even re-run in renamed folder. Great work guys! :(

#91 by_rom

by_rom

    Member

  • Members
  • 88 posts
  •  
    Israel

Posted 07 March 2008 - 05:20 AM

Didn't you have it before

certainly I have it before,but has thought that they not compatible with latest Bootsdi.script.
Now I have 100% working set of w2003 files.

If yes, maybe there is an issue in my 'detect setupldr.bin' section.

I think that is.

You seem to have an awful lot going on in your system tray!

Fixed

just tested new version 48 in wb074 and works great

I want too!!!!!!!
But my result here:

#92 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 07 March 2008 - 08:11 AM

I want too!!!!!!!
But my result here:

You must not run BootSDI stand alone.
Necessary files and directiries are missing.

BootSDI is the last task of a complete build process.

There is a way to RE - start BootSDI, but as first rule assume that this is not recommended

Peter

#93 by_rom

by_rom

    Member

  • Members
  • 88 posts
  •  
    Israel

Posted 07 March 2008 - 09:04 AM

running all project with create iso and qemu emulation=OK
running all project with create bootsdi and qemu emulation=fail

#94 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 07 March 2008 - 09:10 AM

running all project with create iso and qemu emulation=OK
running all project with create bootsdi and qemu emulation=fail

Reboot your system.
Galapo and me have had strange behaviour after replacing the old BootSDI with the new one.
After reboot everything was ok.

Please use the complete build! No ReOpen!

Peter

#95 by_rom

by_rom

    Member

  • Members
  • 88 posts
  •  
    Israel

Posted 07 March 2008 - 10:07 AM

system rebooted, used fixed option,complete build=fail

#96 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 07 March 2008 - 02:14 PM

system rebooted, used fixed option,complete build=fail


Download and try version 049.

It generates the file vdk_WB.log in the %Tools%\VDK directory.

Maybe the logt can tell us, what's going on in your project.

BTW: The log is the only difference in the new version.

Peter

#97 by_rom

by_rom

    Member

  • Members
  • 88 posts
  •  
    Israel

Posted 07 March 2008 - 03:28 PM

wb074+bootsdi_049

#98 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 07 March 2008 - 03:38 PM

wb074+bootsdi_049

I made the change to generate the vdk log, because I wanted to see it :)

I need the file %Tools%\VDK\vdk_WB.log = %BaseDir%\Projects\Tools\vdk_WB.log.

You must zip it, because the forum does not accept text files.

Before telling you the opposite, I do not need the WB log any more. It does not show any trouble.

Peter

#99 by_rom

by_rom

    Member

  • Members
  • 88 posts
  •  
    Israel

Posted 07 March 2008 - 04:13 PM

:)

#100 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 07 March 2008 - 04:36 PM

:)

Attached File(s) Posted Image vdk_WB.7z ( 771bytes ) Number of downloads: 2

Part of the vdk log:

*** open * "c:\074\ISO\Ram\i386\bootsdi.img" /rw /p:0 /l:Z:
Virtual Disk Driver for Windows version 3.1(WB)
http://chitchat.at.i...k.co.jp/vmware/
Recompiled for WinBuilder by psc

some unimportant lines ...

------- ------- ----
FLAT 143360 c:\074\ISO\Ram\i386\bootsdi.img

Partitions :

# Start Sector Length in sectors Type

-- ------------ --------------------- ----

Failed to assign the drive letter 'Z' to disk 0 partition 0.

The local device name is already in use.

0 0 143360 ( 70 MB) <disk>


Here we are.

Do you have a drive Z: visible in explorer?
  • If yes
    • what type?
    • formatted?
  • If no, check registry:
    HKLM\\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\Z
    • If this entry is there:
      on my system I would delete the key
    • If this entry is not there:
      Buy a hammer, stand in front of your PC and :(
      (Maybe we find some other solution)
My assumption is that you have an unformatted drive Z:
And this is not recognized by the BootSDI's FreeDrive function

Peter




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users