116 replies to this topic

[pscEx]

Is it using a virtual drive to create the RAMdisk file?

Yes, that is it

Peter

[pscEx]

I'm currently trying to find connections to this issue.

I'm going to continue there.

Peter

[nikzzzz]

Line in BootSdi
[codebox]ShellExecute,hide,"cmd.exe","/c #$q%VdkExe%#$q driver >> #$q%ProjectTemp%\vdk.ini#$q"[/codebox] does not work. It calls error of mount image. Replacement on [codebox]ShellExecute,hide,"cmd.exe","/c %VdkExe% driver >> #$q%ProjectTemp%\vdk.ini#$q"[/codebox] eliminates an error. But there is a problem with the path containing blank. The possible decision:[codebox]FileCreateBlank,"%ProjectTemp%\vdkstat.bat"TXTAddLine,"%ProjectTemp%\vdkstat.bat","cmd.exe/c #$q%VdkExe%#$q driver >> #$q%ProjectTemp%\vdk.ini#$q","Append"FileCreateBlank,"%ProjectTemp%\vdk.ini" TXTAddLine,"%ProjectTemp%\vdk.ini","[status]","Append" ShellExecute,hide,"%ProjectTemp%\vdkstat.bat"[/codebox]

[Galapo]

Hi nikzzzz,

You're picking up on exactly the same issue as I have: http://www.boot-land...?...ost&p=27946

This is where the logic of the script is failing if the line reads:

ShellExecute,hide,"cmd.exe","/c #$q%VdkExe%#$q driver >> #$q%ProjectTemp%\vdk.ini#$q"

Problem is, altering to this

ShellExecute,hide,"cmd.exe","/c #$q%VdkExe%#$q driver >> %ProjectTemp%\vdk.ini"

doesn't work if there's spaces in the path, so we need the work-around which both of us have suggested.

Still, I am at a loss to know why having quotes doesn't work in the script when in the batch file it is no problem.

Regards,
Galapo.

[pscEx]

Hi nikzzzz,

You're picking up on exactly the same issue as I have: http://www.boot-land...?...ost&p=27946

This is where the logic of the script is failing if the line reads:

ShellExecute,hide,"cmd.exe","/c #$q%VdkExe%#$q driver >> #$q%ProjectTemp%\vdk.ini#$q"

Problem is, altering to this

ShellExecute,hide,"cmd.exe","/c #$q%VdkExe%#$q driver >> %ProjectTemp%\vdk.ini"

doesn't work if there's spaces in the path, so we need the work-around which both of us have suggested.

Still, I am at a loss to know why having quotes doesn't work in the script when in the batch file it is no problem.

Regards,
Galapo.

Dis somebody try already

ShellExecute,hide,"cmd.exe","/c #$q#$q%VdkExe%#$q#$q driver >> %ProjectTemp%\vdk.ini"

?

Peter

[Galapo]

Dis somebody try already

Well, I didn't actually try it but made the assumption. I'm more than happy to be proven wrong here as it would make things much easier for us!

[allanf]

Hi Galapo,

My understanding is that cmd.exe reads quotation marks from the outside in, not linearly. For example, from one of my scripts:

ShellExecute,Hide,"cmd.exe","/c #$q%Tools%\7z.exe t #$q%ArchivesDir%\PortableApps\%ArchiveFile%#$q *portable.exe -r > %ArchivesDir%\PortableApps\Program%var%.ini#$q"

Regards

[nikzzzz]

Dis somebody try already

ShellExecute,hide,"cmd.exe","/c #$q#$q%VdkExe%#$q#$q driver >> %ProjectTemp%\vdk.ini"

?

Peter

Correctly working line:

ShellExecute,hide,"cmd.exe","/c (#$q%VdkExe%#$q driver >> #$q%ProjectTemp%\vdk.ini#$q)"

[Galapo]

But I don't think the backeting works with w2k3.

Regards,
Galapo.

[allanf]

Hi nikzzzz,

You're picking up on exactly the same issue as I have: http://www.boot-land...?...ost&p=27946

This is where the logic of the script is failing if the line reads:

ShellExecute,hide,"cmd.exe","/c #$q%VdkExe%#$q driver >> #$q%ProjectTemp%\vdk.ini#$q"

Problem is, altering to this

ShellExecute,hide,"cmd.exe","/c #$q%VdkExe%#$q driver >> %ProjectTemp%\vdk.ini"

doesn't work if there's spaces in the path, so we need the work-around which both of us have suggested.

Still, I am at a loss to know why having quotes doesn't work in the script when in the batch file it is no problem.

Regards,
Galapo.

From the outside in ... sorry, from the inside out:

cmd.exe reads:

1. " driver >> " ... wrong.

2. "%VdkExe%" driver >> "%ProjectTemp%\vdk.ini"


... should be:

1. "%VdkExe%"

2. ""%VdkExe%" driver >> %ProjectTemp%\vdk.ini"

It seems that only one set of quotes can be inside the outer set, unless the inner set is inside other inner set, etc.

Regards

[Galapo]

But then who does this work:

FileCreateBlank,"%ProjectTemp%\GetVdkStatus.cmd"

TXTAddLine,"%ProjectTemp%\GetVdkStatus.cmd","cmd.exe /c #$q%VdkExe%#$q driver >> #$q%ProjectTemp%\vdk.ini#$q","Append"

ShellExecute,hide,"%ProjectTemp%\GetVdkStatus.cmd",""

Thanks,
Galapo.

[amalux]

@Galapo, Peter

I'm a bit lost, did anyone confirm if this line from nikzzzz worked?

ShellExecute,hide,"cmd.exe","/c (#$q%VdkExe%#$q driver >> #$q%ProjectTemp%\vdk.ini#$q)"

I can't reproduce this issue so I can't test.

[allanf]

But then who does this work: ...

Sorry.

Do you mean "... how does this work?", or do you mean "... why does this work?"?

'cmd.exe /c #$q%VdkExe%#$q driver >> #$q%ProjectTemp%\vdk.ini#$q'

... does it work? I don't think so. It might work with:

'cmd.exe /c #$q#$q%VdkExe%#$q driver >> %ProjectTemp%\vdk.ini#$q'

or:

'cmd.exe /c #$q%VdkExe% driver >> #$q%ProjectTemp%\vdk.ini#$q#$q'

... only one of the paths can be enclosed. Which one?

Edit: Oops. Sorry again... not a good day! That's the code for the batch! I missed that bit ...


Also, I always Set the Path Variables with quotation marks... not certain that this makes a difference, but I do it anyway. eg In the first line under [Process] ... 'Set,%VdkExe%,"%pFileBox4%"'.

Regards

[allanf]

... BTW, I couldn't make a lot of sense out of XP's Help and Support Center. Out of interest...

cmd [[{/c|/k}] [/s] [/q] [/d] [{/a|/u}] [/t:fg] [/e:{on|off}] [/f:{on|off}] [/v:{on|off}] string]

...

Processing quotation marks

If you specify /c or /k, cmd processes the remainder of string and quotation marks are preserved only if all of the following conditions are met:

• You do not use /s.
  
• You use exactly one set of quotation marks.
  
• You do not use any special characters within the quotation marks (for example: &<>( ) @ ^ |).
  
• You use one or more white-space characters within the quotation marks.
  
• The string within quotation marks is the name of an executable file.

If the previous conditions are not met, string is processed by examining the first character to verify whether or not it is an opening quotation mark. If the first character is an opening quotation mark, it is stripped along with the closing quotation mark. Any text following the closing quotation marks is preserved.

... hmm. Does that mean anything relevent here?

Regards

[samneric]

I have tried all sorts to get this to work a second time.

I am running Vista so maybe that has something to do with it but something seems to lock the vdk.sys file even after unloading it.

The error message I get back from "vdk start" after the driver is loaded is "The system cannot find the file"

If I move the vdk.exe and vdk.sys to another folder on my HD and run it again, it works fine.

Like I say, it seems that something is holding on to the vdk.sys file so vdk.exe get an error when starting second time.

I hope this helps point someone in the right direction.

Steve

[pscEx]

I think I fixed it finally.

BaseDir

• with spaces in the name
  
• without spaces in the name

And I tested all entry conditions:

• vdk not installed
  
• vdk stopped
  
• vdk running

In every case on exit the entry condition has been rebuilt, as wanted.

Starting with version 44 I removed all spaces in vdk.ini (from key names AND values)
And I put the cmd in parentheses, like nikzzzzz suggested.

FileCreateBlank,"%ProjectTemp%\vdk.ini"
TXTAddLine,"%ProjectTemp%\vdk.ini","[status]","Append"
ShellExecute,hide,"cmd.exe","/c #$q%VdkExe%#$q driver >> #$q%ProjectTemp%\vdk.ini#$q"
TXTReplace,"%ProjectTemp%\vdk.ini"," : ","="
IniRead,"%ProjectTemp%\vdk.ini","status","driver#$sstatus","%VdkStatus%"
...
If,%VdkStatus%,Equal,"NOTINSTALLED",...

became to

FileCreateBlank,"%ProjectTemp%\vdk.ini"
TXTAddLine,"%ProjectTemp%\vdk.ini","[status]","Append"
ShellExecute,hide,"cmd.exe","/c (#$q%VdkExe%#$q driver >> #$q%ProjectTemp%\vdk.ini#$q)"
TXTReplace,"%ProjectTemp%\vdk.ini","#$s",""
TXTReplace,"%ProjectTemp%\vdk.ini",":","="
IniRead,"%ProjectTemp%\vdk.ini","status","driverstatus","%VdkStatus%"
...
If,%VdkStatus%,Equal,"NOTINSTALLED",...

The issue has been:

• If,%VdkStatus%,Equal,"NOTINSTALLED" >> %VdkStatus% was previously "NOT INSTALLED"

New version 45 on the nativeEx server

Peter

[robinj]

I had a similar problem today when I renamed the directory that WinBuilder resides in. Applying this fix still did not fix it. I found by going to the VDK directory and performing a VDK remove cured it prior to running Winbuilder. Obviously VDK was setup as being installed in a directory that no longer existed.

To create a permanent cure for this I added a VDK remove command before the VDK status command so that the VDK driver is removed prior to every build. This is a bit over the top for most systems, but works reliably.

[amalux]

I had a similar problem today when I renamed the directory that WinBuilder resides in. Applying this fix still did not fix it. I found by going to the VDK directory and performing a VDK remove cured it prior to running Winbuilder. Obviously VDK was setup as being installed in a directory that no longer existed.

To create a permanent cure for this I added a VDK remove command before the VDK status command so that the VDK driver is removed prior to every build. This is a bit over the top for most systems, but works reliably.

Hi robinj,

This is similar to what worked for me, adding

ShellExecute,Hide,"%VdkExe%","remove"

to the end of the [Process] section (snippit of earlier, unreleased 'fix' by Peter). The most recent version of the BootSDI script, I have not tested as it addressed a different issue which I had not experienced. Perhaps this VDK remove bit needs to be included in the script if others experience this same issue. Glad you got it working!

[by_rom]

Confirm that have problems with bootsdi in wb074
When trying to create ramboot.iso
message: zcopy error target path z:\not found ,process (script) stopped and only one option - button OK
in message. And this is occurred twice.
project: live_xp source files xp sp2 eng corporate + w2k3 files
Added for Line 177 in the end [Process] :
ShellExecute,Hide,"%VdkExe%","remove"
not help me
Created ISO file not work at all- damaged/corrupted
in log file (attached) only one error.

[pscEx]

Confirm that have problems with bootsdi in wb074
When trying to create ramboot.iso
message: zcopy error target path z:\not found ,process (script) stopped and only one option - button OK
in message. And this is occurred twice.
project: live_xp source files xp sp2 eng corporate + w2k3 files
Added for Line 177 in the end [Process] :
ShellExecute,Hide,"%VdkExe%","remove"
not help me
Created ISO file not work at all- damaged/corrupted
in log file (attached) only one error.

The file %BaseDir%\Temp\livexp\vdk.ini seems to be missing or wrong.

Please do a new build and post this file.

Peter

[by_rom]

bootsdi settings

Full rebuild attacment here

[pscEx]

bootsdi settings

Full rebuild attacment here

This information may look nice, but it is fully senceless for me

I asked for one file:

%BaseDir%\Temp\livexp\vdk.ini

Peter

[by_rom]

c:\WinBuilder074\Temp\livexp\vdk.ini
Hehe -)))
Message: Upload failed. You are not permitted to upload this type of file
but nothing inside vdk.ini openend with notepad only one line: [status]

[pscEx]

c:\WinBuilder074\Temp\livexp\vdk.ini
Hehe -)))
Message: Upload failed. You are not permitted to upload this type of file
but nothing inside vdk.ini openend with notepad only one line: [status]

Text files are not allowed. You must zip before upload.

There should be something inside like "status: rot running" or similar.

Maybe vdk is corrupted.

Try to download vdk and replace the files in %Tools%

Peter

For compare, here my vdk.ini
 vdk.zip   227bytes   90 downloads

[by_rom]

First of all many thanks to you.
I'll try to download vdk and replace it in %tools%
Compared my and your vdk.ini difference
Resultin:in my vdk.ini I have only one line [status] and nothing more.
Assume that problem in vdk, if you know direct link to downloading vdk I'll be happy to know it too.