595 replies to this topic

[pscEx]

Hi Peter,

Nice changes to the script!

I made a few more additions so that there should now -- finally! -- be no problems for the service to be running outside %Tools%\vdk\, whether in \system32\ or elsewhere.

http://galapo.boot-l.../BootSDI.script

See what you think.

Regards,
Galapo.

Very good solution!


Peter

[pscEx]

Maybe the complexity of the script doesn't really lend itself to making it an api script. That is, there is a lot of IniRead,"%ProjectInfo%" etc that may not really be suitable for some projects. I'd like to hear Pedro's opinion before a "port" is done.

Regards,
Galapo.

I meant mainly the 'calculate' part.

Peter

[nikzzzz]

Now it works!

>@Nikzzzz, Pedrole15, Galapo:

>Can we now bring BootSDI to a.script using API?

It is correct. It is very bad, when projects are incompatible.

>Please use my version 038 form nativeEx server?
>I did some debug work inside.

I have not had time while to look, have been occupied. I will necessarily look.

>@TheHive:
>What about a nice icon for BootSDI?
It was ideal!!

>Galapo:
History039=Galapo improved support for already installed vdk servive

Regards !!!

[pscEx]

Caused by Nuno's LiveXP folder and level changes, I adapted nativeEx.

When I tested everything there appeared an issue with BootSDI:

Due to the last changes Galapo made, the vdk.ini lines
[codebox]... ShellExecute,hide,"cmd.exe","/c (#$q%VdkExe%#$q driver) >> #$q%ProjectTemp%\vdk.ini#$q" // psc + //TXTReplace,"%ProjectTemp%\vdk.ini"," ","" //TXTReplace,"%ProjectTemp%\vdk.ini",":","=" ////IniRead,"%ProjectTemp%\vdk.ini","status","driverstatus","%VdkStatus%" //Echo," Vdk satus - %VdkStatus%" ////Galapo + //If,%VdkStatus%,NotEqual,"NOTINSTALLED",TXTReplace,"%ProjectTemp%\vdk.ini","=\",":\" //If,%VdkStatus%,NotEqual,"NOTINSTALLED",IniRead,"%ProjectTemp%\vdk.ini","status","DriverFile","%VdkDriverSysFile%" //If,%VdkStatus%,NotEqual,"NOTINSTALLED",StrFormat,path,"%VdkDriverSysFile%",%VdkDriverLoc% //If,%VdkStatus%,NotEqual,"NOTINSTALLED",If,%VdkDriverLoc%,Equal,"system32\",Set,%VdkExe%,vdk.exe //If,%VdkStatus%,NotEqual,"NOTINSTALLED",If,%VdkDriverLoc%,NotEqual,"system32\",Set,%VdkExe%,%VdkDriverLoc%vdk.exe ////Galapo - TXTReplace,"%ProjectTemp%\vdk.ini"," : ","=" IniRead,"%ProjectTemp%\vdk.ini","status","driver#$sstatus","%VdkStatus%" Echo," Vdk status - %VdkStatus%" If,%VdkStatus%,NotEqual,"NOTINSTALLED",IniRead,"%ProjectTemp%\vdk.ini","status","Driver#$sFile","%VdkDriverSysFile%"
If,%VdkStatus%,NotEqual,"NOTINSTALLED",StrFormat,path,"%VdkDriverSysFile%",%VdkDriverLoc%
Set,%VdkExe%,%VdkDriverLoc%vdk.exe
// psc -
Run,%ScriptFile%,FreeLetter
...[/codebox]

Peter

[Galapo]

Gday Peter,

Well, the vdk issues seems to continue. I see now that I hadn't tested with a path with spaces.

The new version unfortunately doesn't work if vdk is located in the system32 folder. I had to alter to:

...

TXTReplace,"%ProjectTemp%\vdk.ini"," : ","="

IniRead,"%ProjectTemp%\vdk.ini","status","driver#$sstatus","%VdkStatus%"

Echo," Vdk status  - %VdkStatus%"

If,%VdkStatus%,NotEqual,"NOTINSTALLED",IniRead,"%ProjectTemp%\vdk.ini","status","Driver#$sFile","%VdkDriverSysFile%"

If,%VdkStatus%,NotEqual,"NOTINSTALLED",StrFormat,path,"%VdkDriverSysFile%",%VdkDriverLoc%

// Note by Galapo: next three lines must be such for vdk service in system32 folder to function

If,%VdkStatus%,NotEqual,"NOTINSTALLED",If,%VdkDriverLoc%,Equal,"system32\",Set,%VdkExe%,vdk.exe

If,%VdkStatus%,NotEqual,"NOTINSTALLED",If,%VdkDriverLoc%,NotEqual,"system32\",Set,%VdkExe%,%VdkDriverLoc%vdk.exe

//Set,%VdkExe%,%VdkDriverLoc%vdk.exe

// psc -

...

The issue now seems to be whether the variable %VdkDriverLoc% is a full path or not. %VdkDriverSysFile% can be system32\vdk.sys and so when this enters to be %VdkDriverLoc%vdk.exe it doesn't work since the path is system32\vdk.exe. I don't know how to tell through WB whether a path is a full path or not, so just had to alter the script as above.

Regards,
Galapo.

[pscEx]

// Note by Galapo: next three lines must be such for vdk service in system32 folder to function
If,%VdkStatus%,NotEqual,"NOTINSTALLED",If,%VdkDriverLoc%,Equal,"system32\",Set,%VdkExe%,vdk.exe
If,%VdkStatus%,NotEqual,"NOTINSTALLED",If,%VdkDriverLoc%,NotEqual,"system32\",Set,%VdkExe%,%VdkDriverLoc%vdk.exe
//Set,%VdkExe%,%VdkDriverLoc%vdk.exe
// psc -
...[/code]

The issue now seems to be whether the variable %VdkDriverLoc% is a full path or not. %VdkDriverSysFile% can be system32\vdk.sys and so when this enters to be %VdkDriverLoc%vdk.exe it doesn't work since the path is system32\vdk.exe. I don't know how to tell through WB whether a path is a full path or not, so just had to alter the script as above.

The issue I wanted to solve:

• vdk not installed
  
• script is interrupted out of any reason (between install and remove)

Next run the script sees vdk running or stopped and sets path to system32 ???

Why not solve it practically and provide a textbox 'path to installed vdk.exe'
If it is empty, %Tools%\vdk is assumed.

Peter

[niche99]

Hi All,

Here we go again.
After a break of a couple months, I have downloaded a complete fresh nativeEx_barebone and core. When I build I get the following errors.

1. regRedirect.exe not found when Explorer script runs.
2. vdk.exe not found when BootSDI script runs. This IS in Tools\vdk\vdk.exe.

I would attach a log but notice that no log is generated in the WinBuilder folder! Note I haven't changed any WinBuilder settings that I'm aware off. I am using the same version of WinBuilder as previously 072.

niche99
PS why does the BootSDI script continually download the HPUSBF.exe file each time it is run!

[pscEx]

Hi All,

Here we go again.
After a break of a couple months, I have downloaded a complete fresh nativeEx_barebone and core. When I build I get the following errors.

1. regRedirect.exe not found when Explorer script runs.
2. vdk.exe not found when BootSDI script runs. This IS in Tools\vdk\vdk.exe.

I would attach a log but notice that no log is generated in the WinBuilder folder! Note I haven't changed any WinBuilder settings that I'm aware off. I am using the same version of WinBuilder as previously 072.

niche99

Hi niche99!
Strange results!

Sorry, I just decided to finish for today. Inspite your issue seems to be interesting (and solvable!) I 'm coming back tomorrow.

I hope you can live some hours w/o a working WinBuilder PE

Peter

[Galapo]

The issue I wanted to solve:

• vdk not installed
  
• script is interrupted out of any reason (between install and remove)

Next run the script sees vdk running or stopped and sets path to system32 ???

Why not solve it practically and provide a textbox 'path to installed vdk.exe'
If it is empty, %Tools%\vdk is assumed.

Peter

Gday Peter,
If the script is interrupted, then next time it runs then the script locates where the service is running from. If it is from %Tools%\vdk then it will run from there. If it is from system32, then it will run from there. That, really, is the point of the lines

If,%VdkStatus%,NotEqual,"NOTINSTALLED",If,%VdkDriverLoc%,Equal,"system32\",Set,%VdkExe%,vdk.exe

If,%VdkStatus%,NotEqual,"NOTINSTALLED",If,%VdkDriverLoc%,NotEqual,"system32\",Set,%VdkExe%,%VdkDriverLoc%vdk.exe

But I guess a textbox to optionally specify a path would accomplish much the same thing...

Regards,
Galapo.

[niche99]

Hi All,

Here we go again.
After a break of a couple months, I have downloaded a complete fresh nativeEx_barebone and core. When I build I get the following errors.

1. regRedirect.exe not found when Explorer script runs.
2. vdk.exe not found when BootSDI script runs. This IS in Tools\vdk\vdk.exe.

I would attach a log but notice that no log is generated in the WinBuilder folder! Note I haven't changed any WinBuilder settings that I'm aware off. I am using the same version of WinBuilder as previously 072.

niche99
PS why does the BootSDI script continually download the HPUSBF.exe file each time it is run!

OK, I found regRedirect.exe in the archive I made before doing a clean nativeEx download. I think that the tools check script is missing a check for regRedirect.exe which is needed by the Explorer script?
And
vdk error disappears if vdk is installed, if it's not then I get the error vdk.exe not found.

niche99

[pscEx]

OK, I found regRedirect.exe in the archive I made before doing a clean nativeEx download. I think that the tools check script is missing a check for regRedirect.exe which is needed by the Explorer script?
And
vdk error disappears if vdk is installed, if it's not error vdk.exe not found.

niche99

regRedirect is used by and contained in OLESupport.Script.

If in Explorer.Script one uses OLESupport ('Init DLLs at build time' is checked). OLESupport.Script must be checked, too. This will extract regRedirect.exe

I'm working on a new BootSDI.Script version which will work with vdk installed and not installed.

Before I publish, I want to test carefully.

But as a preview, here the current version:
 BootSDI.script   739.66K   217 downloads

Peter

[fly]

I just don't understand this script. How can I get it to boot my USB drive? In the little GUI screen, my USB drive doesn't show up in the dropdown list. I'm also assuming that the instructions in the first post are a little outdated, do I really need grub?

Thanks for any help.

[Oleg_II]

You don't need grub for booting from USB:

Running from a USB stick or a flash card (your movable Windows in a pocket
(USB stick of flash card should be bootable on your computer - miracles are not possible yet
1. Copy file WINNT.SIF created in previous step 3 to your prepared USB stick.
2. Copy the folder i386 with all files inside created in previous step 7 to the USB stick.
3. Rename setupldr.bin (Win2003 file) to ntldr (file has no extention!) and place this file (ntldr) to USB stick.
Thats all! If your USB stick or flesh card is capable to boot at all, your motherboard supports booting from USB (make needed settings in BIOS setup) and your image is bootable it should work!

That is on the first page. It's working now.

You may use grub for booting from HDD. It's easy. But you can use other options too (you need to find them first).

If something doesn't work automatic, just create the project, format you USB drive and move needed files to it manualy (according to the instructions on the first page

[niche99]

regRedirect is used by and contained in OLESupport.Script.

If in Explorer.Script one uses OLESupport ('Init DLLs at build time' is checked). OLESupport.Script must be checked, too. This will extract regRedirect.exe

I'm working on a new BootSDI.Script version which will work with vdk installed and not installed.

Before I publish, I want to test carefully.

But as a preview, here the current version:
 BootSDI.script   739.66K   217 downloads

Peter

Hi Peter,

Ah, when I ran the build process, I'm pretty sure I didn't have OLE support checked. I don't remember getting a warning or message saying that OLE support must be checked. Maybe just me getting cross eyed again, I think Verify Project script was checked.
I can get a build running now.

As an aside I notice that there is a pause during desktop appearance when driver signing script is checked, no where near as bad as before, when I brought the driver signing issue to your attention, but I seem to remember it being quicker from blue background to desktop in previous versions/incarnations of the driver signing fix.

Just done a test. I check 'Init DLLs at build time' in Explorer.script. I check OLESupport.script. During build process I get an error during Explorer.script processing:

regRedirect.exe. This file does not have a program associated with it for performing this action.

Build continues on clicking OK, but RAM ISO reboots over and over in VirtualBox, after getting to blue backgound.

Regards,
niche99

[pscEx]

Ah, when I ran the build process, I'm pretty sure I didn't have OLE support checked. I don't remember getting a warning or message saying that OLE support must be checked. Maybe just me getting cross eyed again, I think Verify Project script was checked.

That is the discrepancy between fast, actual development and the rat's tail off adding something somewhere ...
I'll check and propably add to Verify.
Thanks

As an aside I notice that there is a pause during desktop appearance when driver signing script is checked, no where near as bad as before, when I brought the driver signing issue to your attention, but I seem to remember it being quicker from blue background to desktop in previous versions/incarnations of the driver signing fix.

I remember a Scottish collegue in the 80th. I worked with him a long time.
To understand his English has been as difficult for me as to understand your English.

After several reflections I hope to have understood completely.
I do not have any idea why the -in registry predefined- situation can cause time delay.
For me, only if an unsigned driver anywhen is detected, the install proc should look at the reg entry and say 'ok'.

But nobody knows what Bill G. offers as additional features ...

Peter

[niche99]

Hi Peter,

I think I was editing my post when you were replying to it.
I added a regRedirect error message I encountered.

Regards,
niche99

[pscEx]

Just done a test. I check 'Init DLLs at build time' in Explorer.script. I check OLESupport.script. During build process I get an error during Explorer.script processing:

regRedirect.exe. This file does not have a program associated with it for performing this action.

Build continues on clicking OK, but RAM ISO reboots over and over in VirtualBox, after getting to blue backgound.

That i cannot explain for myself. I never saw that clicking an *.exe wants to start a program associated with the extention .exe

Perhaps try this first:
Maybe by some failed or interrupted builds before, some cached data are corrupted.

• %BaseDir%\Temp\<your project>
  
• %BaseDir%\Workbench\<your project>

Store them anywhere. Maybe we need it for later debug.
Then delete them and rebuild.

If the issue still exists: post the log
If the issue has disappeared, please post the stored data and the log.

Thanks

Peter

[pscEx]

Hi Peter,

I think I was editing my post when you were replying to it.
I added a regRedirect error message I encountered.

Regards,
niche99

Today I got the same error.

It happens when you run a single script which uses OLESupport.Script.

Changed OLESupport.Script > Version 7

Peter

[edborg]

I'm trying BootSDI as an alternative to my CreateISO with RAM option.
Though I apply it to a build surely working and use the same W2K3 files that create a RAM booting ISO with my script, I get the enclosed error.
Can anybody explain how to correctly use the script?
edborg

Attached Thumbnails

• 

[pscEx]

I'm trying BootSDI as an alternative to my CreateISO with RAM option.
Though I apply it to a build surely working and use the same W2K3 files that create a RAM booting ISO with my script, I get the enclosed error.
Can anybody explain how to correctly use the script?
edborg

Please post the log.

Peter

[edborg]

Please post the log.

Peter

Here it is, thanks.
edborg

Attached Files

•  log.html   35.44K   79 downloads

[pscEx]

Here it is, thanks.
edborg

It seems to depend on your special project copy flow.

BootSDI can handle 2 situations:

• Source is XP and special W2003 ntdetect.com, ramdisk.sys, setupldr.bin are copied from 'anywhere'
  
• Source is W2003 and these files are already on target.

In your special case, with XP source, the W2003 setupldr.bin seems to be already on target. That brings troubles, because the script does not handle this situation.

Delete this setupldr.bin before running BootSDI (Or do not copy at all)

Peter

[edborg]

It seems to depend on your special project copy flow.

BootSDI can handle 2 situations:

• Source is XP and special W2003 ntdetect.com, ramdisk.sys, setupldr.bin are copied from 'anywhere'
  
• Source is W2003 and these files are already on target.

In your special case the W2003 setupldr.bin seems to be already on target. That brings troubles, because the script does not handle this situation.

Delete this setupldr.bin before running BootSDI (Or do not copy at all)

Peter

Congratulations, Peter!
You've immediately spotted the solution.
Setupldr.bin had already been copied by CreateISO to %target_win%. If deleted, BootSDI works.

However, also BootSDI copies Setupldr.bin to &target_win% and does not work if run a second time.
Perhaps this should be corrected.
edborg

[pscEx]

Congratulations, Peter!
You've immediately spotted the solution.
Setupldr.bin had already been copied by CreateISO to %target_win%. If deleted, BootSDI works.

However, also BootSDI copies Setupldr.bin to &target_win% and does not work if run a second time.
Perhaps this should be corrected.
edborg

In Standard nativeEx_barebone CreateISO and BootSDI exclude each other by definition in Edit > Options.
Why do you have to use both of them?

I do not understand the second part of your post.
How run BootSDI a second time?

Peter

[edborg]

In Standard nativeEx_barebone CreateISO and BootSDI exclude each other by definition in Edit > Options.
Why do you have to use both of them?

I do not understand the second part of your post.
How run BootSDI a second time?

Peter

I do not want to use them both at the same time; I know, they're mutually exclusive.
But if the script is re-run to recreate an image (e.g. after doing some changes to the project), the error occurs. Perhaps I should run ReOpen first in this case?
With my CreateISO I can do that without problems.
edborg