• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

RFA - OS - Windows 8 - Command Processor - Test context of -

BASys

BASys

Messages
1,361
Country
scotland
RFA - OS - Windows 8 - Command Processor - Test context of -

Hi Folks

Do you have Windows 8 ?
If so I'd appreciate your assistance.



Background -
Whilst attempting to upgrade a set of batch files to 'Windows 10' compatibility
I came across a change in the Command Processor's behaviour
from at least 'Windows 7', and all prior OS versions.

Previously, any batch file ran in the context of it's containing folder.

'Windows 10' runs any batch file in the context of C:\Windows\System32\.



Request -
I need to know how Windows 8 behaves.

Would some kind 'Windows 8' users, (both 8.0 and 8.1),
please -
- Download the attached ZIP.
- Extract to the root of their C drive.
- Run the batch file, TestBatchContext.bat, (N.B. right-click 'Run as admin')
- Upload the resulting log file in your reply.

N.B.
You might have to 'unblock' the downloaded zip.

TestBatchContext doesn't do anything nasty,
just reads the current folder path, its context, and your OS version number. :)

Many thanks
Paul Donnelly
 

Attachments

  • TestBatCalls.zip
    2.4 KB · Views: 248
Last edited:
This what you need?

Doug
 

Attachments

  • LOG_Test_CALL.txt
    680 bytes · Views: 323
Hi Doug

Many thanks for taking the time to test & reply
against your Windows 8.1 version.



Your TestBatchContext's overall success, was as expected.
i.e.
Confirming our 'Windows 8' ODG Configurator's beta-testers - 'no issues' against tool.


However,
your returned results, only further discomfitted me, :(
in that -
behaviours across various OS versions,
were more diverse than expected.



Doug -
Just for information,
as I don't have a W8.1 machine,
would you be kind enough to repeat the test,
this time by just DOUBLE-CLICKING the bat file ?
Then re-posting the resulting log file ?



Much appreciated.
ATB
Paul
 
Last edited:
I don't have Win8 either. This is my mother's computer....
Here is the result if I double-click on the batch file, on the same machine.
 

Attachments

  • LOG_Test_CALL.txt
    702 bytes · Views: 412
Cheers Doug.
Thanks for your assistance.



RESULTS -
For the CALLED batch file -

For 'Run as admin' -
W7 SP1 == C:\TestBatCalls\ChildFolder\CalledTarget.bat
W8.0 == TBD
W8.1 == C:\TestBatCalls\ChildFolder\CalledTarget.bat
W10 == C:\WINDOWS\system32\ChildFolder\CalledTarget.bat

For 'Double-Click' -
W7 SP1 == C:\TestBatCalls\ChildFolder\CalledTarget.bat
W8.0 == TBD
W8.1 == C:\TestBatCalls\ChildFolder\CalledTarget.bat
W10 == C:\TestBatCalls\ChildFolder\CalledTarget.bat



Much appreciated
ATB
Paul
 
You must log in or register to reply here.
Back
Top