Page 1 of 1

Error run TBOSDT in XP/2003R2 x64

Posted: Thu May 14, 2020 11:38 am
by ostapvoip
Error Run in XP/2003R2 x64
- imagew64.exe, tbview64.exe, tbimount64.exe https://i.vgy.me/mPIma9.png
- tbosdtw64.exe https://i.vgy.me/RtfCV5.png
- tbosdtw.exe https://i.vgy.me/ji5hYL.png
ws2_32.dll file is in the system 32 and 64 bit https://i.vgy.me/JJuHcr.png

Re: Run in XP/2003R2 x64

Posted: Thu May 14, 2020 3:52 pm
by ostapvoip
Fix for XP/2003R2 x64 https://i.imgur.com/zyJ0oCa.png
run_tbosdtw.cmd script should be in the program folder

@echo off
setlocal enableextensions
set "xOS=x64"
if /i "%PROCESSOR_ARCHITECTURE%"=="x86" if not defined PROCESSOR_ARCHITEW6432 set "xOS=x86"
for /f "tokens=4 delims=[]." %%A in ('ver') do (set "Build=%%A")
If %Build% LSS 6000 if "%xOS%"=="x64" set "PATH=%windir%\SysWOW64"
"%~dp0tbosdtw.exe" %*
endlocal

It works without errors in XP x64 and 2003R2 x64.

Re: Error run TBOSDT in XP/2003R2 x64

Posted: Thu May 14, 2020 8:02 pm
by TeraByte Support
If I recall XP x64 doesn't like it due to the signing even though dual
signed. There was something unique about XP x64 but can use the x86 if
I recall.

On 5/14/2020 4:38 AM, ostapvoip wrote:
> Error Run in XP/2003R2 x64
> - imagew64.exe, tbview64.exe, tbimount64.exe
>
> [
> https://i.vgy.me/mPIma9.png
> ](https://i.vgy.me/mPIma9.png)
>
> - tbosdtw64.exe
>
> [
> https://i.vgy.me/RtfCV5.png
> ](https://i.vgy.me/RtfCV5.png)
>
> - tbosdtw.exe
>
> [
> https://i.vgy.me/ji5hYL.png
> ](https://i.vgy.me/ji5hYL.png)
>
> ws2_32.dll file is in the system 32 and 64 bit
>
> [
> https://i.vgy.me/JJuHcr.png
> ](https://i.vgy.me/JJuHcr.png)
>
>
>


Re: Error run TBOSDT in XP/2003R2 x64

Posted: Thu May 14, 2020 8:36 pm
by ostapvoip
Hmm, not funny ...
Digital signature is not important here.
Before starting tbosdtw.exe, it is important to have a 32-bit environment, because 64-bit does not work.
Is it not clear from the information above?
In my opinion, everything is transparent and simple.

It is depressing that the 32-bit version of tbosdtw.exe does not work without first profiling the environment.
It is of course an obvious error.

I apologize for the unpleasant opinion. But I got the impression that no one is testing the code on a real 32 and 64 bit OS from NT4 to 10.
https://i.imgur.com/mAy1p7E.png

I must note that your programs are very high quality and beautiful, but these simple mistakes are strange against this general background. They should not be.
I apologize for being perhaps too rude. But, in my opinion, otherwise it will be difficult to wake you up.

Update. Corrected the script above ..