system lock after Image ends

[tas3086]

I run image.exe through a tbos script that is initiated through BIBM scripting. Image runs correctly and ends, but never returns to tbos. I get the message:
"Remove disk or other media. Press any key to restart". Pressing a key causes the system to hang.

I just changed my bios options to ACHI instead of IDE (disk access).
Do you have any suggestions other than go back to IDE?
Thanks,

[Brian K]

tas3086 wrote:

> "Remove disk or other media. Press any key to restart". Pressing a key causes the
> system to hang.
>

tas3086,

Do you have /uy /um in the script?

[tas3086]

only /u is coded. Log file indicates successful completion. I see a very quick small blue box flash by .. I think it says that the image was successful, but it is very quickly gone ... and then a black screen with the messages stated previously.

[tas3086]

Further investigation shows that errors happen when the script is exited, and not after image.exe ends.
I put ext("reboot") just before the end sub, which works fine for me now. No more messages, and no prompt to continue and hang.

I just wonder why I never saw this set of error messages before.

[TeraByte Support]

is it a "restore" - it can be this issue as well:
http://www.terabyteunlimited.com/kb/article.php?id=465

or if it was USB target, perhaps the keyboard isn't working:
http://www.terabyteunlimited.com/kb/article.php?id=349


"tas3086" wrote in message news:8447@public.image...

I run image.exe through a tbos script that is initiated through BIBM
scripting. Image runs correctly and ends, but never returns to tbos. I get
the message:
"Remove disk or other media. Press any key to restart". Pressing a key
causes the system to hang.

I just changed my bios options to ACHI instead of IDE (disk access).
Do you have any suggestions other than go back to IDE?
Thanks,

[tas3086]

No usb devices other than KB and mouse.
Happens doing backup or restore
Discovered that ACHI or IDE bios settings make no difference to the error messages.
Unckecking the ACHI 2.1 setting option in BIBM settings seems to help a lot.
Further investigation shows that errors happen when the script is exited, and not after image.exe ends.
I put ext("reboot") just before the end sub, which works fine for me now. No more messages, and no prompt to continue and hang.

I just wonder why I never saw this set of error messages before.
I now run perfectly with achi set in bios, and ACHI 2.1 settings in BIBM, with the ext reboot addition to the script.

Thank you for all of your help and support.

[TeraByte Support]

Sounds like the direct access to the SATA devices is being used in IFD
(rather than BIOS devices) then on the attempt to read from disk again is
where the BIOS is used again.

"tas3086" wrote in message news:8488@public.image...

No usb devices other than KB and mouse.
Happens doing backup or restore
Discovered that ACHI or IDE bios settings make no difference to the error
messages.
Unckecking the ACHI 2.1 setting option in BIBM settings seems to help a lot.
Further investigation shows that errors happen when the script is exited,
and not after image.exe ends.
I put ext("reboot") just before the end sub, which works fine for me now. No
more messages, and no prompt to continue and hang.

I just wonder why I never saw this set of error messages before.
I now run perfectly with achi set in bios, and ACHI 2.1 settings in BIBM,
with the ext reboot addition to the script.

Thank you for all of your help and support.