595 replies to this topic

[pscEx]

@nikzzzz

Why do you offer the unUPX option?

I know that (especially DisplayProperties) some apps do their own UPX, and so 'bypass' the autoUPX script.

Do UPXed files disturb your cfompress algorithm?

If yes, we should find a solution which is more economic.

It wastes a lot of time first to UPX and then to unUPX.

@Holger:
Maybe you take part in this discussion?

Peter

BTW: I could include in the verify that in case of BootSDI autoUPX is forbidden.
What about autoCompress?

[Nuno Brito]

Some times ago I tried successless similar with ProjectInfo.

The issue:

If WinBuilder could catch the console output of a ShellExecute process into a variable, things would become much more easier!
(Maybe and / or ExitCode)

@Nuno ???

Peter

Maybe it would be easier to code a small binary to launch vdk and properly interpret these messages - catching output is possible but how far would it really be needed just for one case?

btw: the ExitCode output var is a good tip..

[pscEx]

Maybe it would be easier to code a small binary to launch vdk and properly interpret these messages - catching output is possible but how far would it really be needed just for one case?

I think you are right.
That was only one special issue where only needed a string as result.
I'm rather sure that happens not so often ...

But if you implement the ExitCode,

Peter

[was_jaclaz]

The line 3 will always yield result RUNNING and will be execute vdk.exe REMOVE.
It will not solve a problem described Galapo.

Yes, they were just examples, I don't even know if invoking cmd.exe /c under Winbuilder behaves the same as from RUN.

IF it does, one can write whatever in that line, no need for temporary files, NO NEED to :

code a small binary to launch vdk and properly interpret these messages

@Nuno, you joking, right?
the point was to make things SIMPLER....
we can always write a tiny .NET app for this....

jaclaz

[nikzzzz]

@nikzzzz
Why do you offer the unUPX option?

UPX does not create problems. UPX the application demands more approximately twice memory. NTFS the compression does not pack UPX. UPX it is unprofitable.
I checked this statement experimentally.

[Galapo]

I had to modify the new version to get around the vdk service issue I raised.

See the script here and see what you think. This might give a bit more of an idea of what I required, perhaps I wasn't clear enough at the beginning. Anyway, problem now solved.

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

Regards,
Galapo.

[Galapo]

I get an error with the FileByteExtract line under the [Check-Version] section. An error message box appears reporting "Error -" and the FileByteExtract line.

Any idea of what the problem is. I had to uncomment the lines and add Set,%OK%,1 to get the script to run.

Thanks,
Galapo.

[nikzzzz]

I had to modify the new version to get around the vdk service issue I raised.
See the script here and see what you think. This might give a bit more of an idea of what I required, perhaps I wasn't clear enough at the beginning. Anyway, problem now solved.

I have understood the error.

VDK.EXE OPEN DiskNumber image /l:DriveLetter.......VDK.EXE CLOSE DiskNumber

It is corrected:

VDK.EXE OPEN * image /l:DriveLetter.......VDK.EXE CLOSE DriveLetter

Regards !

New version

[pscEx]

I get an error with the FileByteExtract line under the [Check-Version] section. An error message box appears reporting "Error -" and the FileByteExtract line.

Any idea of what the problem is. I had to uncomment the lines and add Set,%OK%,1 to get the script to run.

Thanks,
Galapo.

That is a bug. I already reported here.

In your case you do not have the correct version of setupldr.bin.
You should not set %OK% to 1 in order to neglect that.

Peter

[pscEx]

I have understood the error.

Regards !

New version

As version 034 on the nativeEx server.

Peter

[pscEx]

I sent a new version 035 to the nativeEx server.

Change: In [UnUpx] I added a backslash to %targetdir%

Without the backslash all projects instead ot the actual one are unUPXed.

Peter

[yahoouk]

I sent a new version 035 to the nativeEx server.

Change: In [UnUpx] I added a backslash to %targetdir%

Without the backslash all projects instead ot the actual one are unUPXed.

Peter

I've tested, failed with follow 3 errors.




And then closed.

For me, v22 is working, although size is doubled, I can makecab to be shrink.

Regards

yahooUK

[pscEx]

I've tested, failed with follow 3 errors.
...
For me, v22 is working, although size is doubled, I can makecab to be shrink.

Thanks for the report

For me there seem to be some reasons possible, which really do not depend on the new version 035.
(I'm sure that you get the same issues with version 034)

Your pictures tell me that you probably do not use the latest WinBuilder (pict #3 -but perhaps this can also be a hint for an old nativeEx_core-) version and also not the latest nativeEx_core (picts #1 and #2).

You know that WinBuilder and it's projects are 'alive' and may -and really do so- change from day to day.

If you use something 'brand new' you have to check that the environment is up to date, too.

Search for 'updateCore' and install + process it.

If you have issues after that, please post the log. Remember: There are never 'stupid questions' there can be only 'stupid answers'

Peter

[nikzzzz]

Update BootSdi.script
The script is copied to use Calculate.exe.
Little changes in the interface.
Small bugs.

[Galapo]

Hi nikzzzz,

Thanks for the new version! Quite a few changes.

I'm still having problems with having vdk service already on my system. I made some modifications to your script which can be seen here:

http://galapo.boot-land.net/temp/BootSDI[c..._marked].script

The changed/added lines are marked with an initial ---> If you accept my changes, then just remove this. I just added the indication so you could see what I had done. Basically, if the vdk service is detected as either running or stopped, then the script makes use of vdk already on system. Otherwise, if no service is detected, the script makes use of vdk located in %tools%\vdk.

Hopefully this makes sense now.

Thanks,
Galapo.

[nikzzzz]

The changed/added lines are marked with an initial ---> If you accept my changes, then just remove this. I just added the indication so you could see what I had done. Basically, if the vdk service is detected as either running or stopped, then the script makes use of vdk already on system. Otherwise, if no service is detected, the script makes use of vdk located in %tools%\vdk.
Galapo.

[variables]

[b]%VdkExe%=%Tools%\vdk\vdk.exe[/b]

[Process]

..........

IniRead,"%ProjectTemp%\vdk.ini","status","driverstatus","%VdkStatus%"

[b]If,%VdkStatus%,NotEqual,"NOTINSTALLED",Set,%VdkExe%,"Vdk.exe"[/b]

Run,%ScriptFile%,FreeLetter

If,%VdkStatus%,Equal,"NOTINSTALLED",ShellExecute,Hide,"%VdkExe%","install"If,%VdkStatus%,NotEqual,"RUNNING",ShellExecute,Hide,"%VdkExe%","start"Run,%ScriptFile%,CreateRAMIsoIf,%VdkStatus%,NotEqual,"RUNNING",ShellExecute,Hide,"%VdkExe%","stop"If,%VdkStatus%,Equal,"NOTINSTALLED",ShellExecute,Hide,"%VdkExe%","remove"

[yahoouk]

,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Hi nikzzzz,

Nice script, no error, but no iso file created.

Regards

yahooUK

[nikzzzz]

Hi nikzzzz,

Nice script, no error, but no iso file created.

Regards

yahooUK

Thanks for testing.

[pscEx]

After now having a new API containing 'Calculate':
Do we get a new BootSDI using this API-Function?

BTW: I have problems with the current Calculate:
BootSDI brings an error message.

Trying (from the log) the command line BooSDI executes, I get the same error mesage

Every variation in the command brings the correct sysntax error message.

Peter

[yahoouk]

I removed RAMPE script message today, because it is out of this topic.
Sorry for any annoyance!

yahooUK

Regards

[nikzzzz]

BTW: I have problems with the current Calculate:
BootSDI brings an error message.
Trying (from the log) the command line BooSDI executes, I get the same error mesage
Every variation in the command brings the correct sysntax error message.
Peter

I seem have found out an error in Calculate.exe and sCalculate.exe.

[nikzzzz]

I removed RAMPE script message today, because it is out of this topic.
Sorry for any annoyance!
yahooUK
Regards

Not clearly, why you have made it. IMGinRAM i wrote together with HighwayStar, and it helped me with a writing of this script. BootSdi this continuation of this script.
Regards !

[pscEx]

I seem have found out an error in Calculate.exe and sCalculate.exe.

Now it works!

@Nikzzzz, Pedrole15, Galapo:

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

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

@TheHive:
What about a nice icon for BootSDI?

Peter

[Galapo]

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.

[Galapo]

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

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.