6 replies to this topic

[pscEx]

First: This is not a bug report about BootSDI.Script or Vdk!

This is just to give you a hint if you have the same strange events.

Let me tell you what happened:

Since some days I'v had some troubles on my PC. Sometimes during boot or even during work the system hang.
Some Google results pointed to disk failure.

Therefore I activated S.M.A.R.T in my BIOS and installed a nice program 'ActiveSmart26' which in intervals gave me some info about my hdd-s.

When after that I started WinBuilder with BootSDI (the tests I promised MedEvil in his 'boot order optimization' topic), at the end of the BootSDI script the progress tab remained active, with full blue progress bars. And WinBuilder hang. And Vdk still showed a drive Z:

I killed WinBuilder and tried 'Vdk stop' 'Vdk remove' and whatever seemed to be reasonable.
In all cases no success and the message that drive 0 is busy.

Only a reboot could solve this.

After a long time of investigation I found that ActiveSmart26 also tries to check the Vdk drive. And appearently the Vdk drive does not like that.

After deinstalling ActiveSmart26, everything went well again.

Peter


BTW: I posted here, because I thougt, it is a bit 'How To'

If it is misplaced here, @Jaclaz, please, move.

[Galapo]

Hi Peter,

Sometimes I have something of the same issue you descibe: "at the end of the BootSDI script the progress tab remained active, with full blue progress bars. And WinBuilder hang. And Vdk still showed a drive Z".

I don't think drive Z was still present to the system itself, though still loaded by vdk.

Regards,
Galapo.

[pscEx]

I don't think drive Z was still present to the system itself, though still loaded by vdk.

You are right, there was no Z: visible in the explorer!
But at least in my case Vdk was irritated.

Peter

[Galapo]

Yes, me too. Only a reboot will get vdk functioning properly again.

My feeling is that once you forcefully have to remove a drive with vdk, you are quite close to having to reboot.

Regards,
Galapo.

[Galapo]

Hi Peter,

Here's what I have to do now with the BootSDI script so that the above issues do not happen to me:

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

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",""

What happens is that if we use this line

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

the file '%ProjectTemp%\vdk.ini' is not written to. But if that is changed to

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

then the file is written to, but won't be if there are spaces in the path.

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",""

functions, though.

I cannot understand why

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

is problematic.

Regards,
Galapo.

[pscEx]

There seems to be a connection to a different topic.

I'm going to combine both 'bad boys' and find a final solution.

Peter

[amalux]

First: This is not a bug report about BootSDI.Script or Vdk!

This is just to give you a hint if you have the same strange events.

Let me tell you what happened:

Since some days I'v had some troubles on my PC. Sometimes during boot or even during work the system hang.
Some Google results pointed to disk failure.

Therefore I activated S.M.A.R.T in my BIOS and installed a nice program 'ActiveSmart26' which in intervals gave me some info about my hdd-s.

When after that I started WinBuilder with BootSDI (the tests I promised MedEvil in his 'boot order optimization' topic), at the end of the BootSDI script the progress tab remained active, with full blue progress bars. And WinBuilder hang. And Vdk still showed a drive Z:

I killed WinBuilder and tried 'Vdk stop' 'Vdk remove' and whatever seemed to be reasonable.
In all cases no success and the message that drive 0 is busy.

Only a reboot could solve this.

After a long time of investigation I found that ActiveSmart26 also tries to check the Vdk drive. And appearently the Vdk drive does not like that.

After deinstalling ActiveSmart26, everything went well again.

Peter


BTW: I posted here, because I thougt, it is a bit 'How To'

If it is misplaced here, @Jaclaz, please, move.

Hi Peter,

I have not experienced this 'system hang' issue you describe having used BootSDI in almost every project for months, also,

at the end of the BootSDI script the progress tab remained active, with full blue progress bars. And WinBuilder hang. And Vdk still showed a drive Z:

seems to be a differant issue than the 'zCopy' error, as I've not experienced this issue either. Maybe your 'bad boy' is unrelated to mine which you fixed, thank you very much.

Try SpeedFan (nice, free program) and do the free online analysis to see if anything is revealed about your drive.