Access a mobile device using the command prompt
brucine Posted messages 24411 Registration date Status Membre Last intervention -
Hello,
I have a mobile device (PSION) that I connect to my PC. I would like to create a .bat file to create a folder "IA_DONNEES" on the SD card of the PSION.
3 réponses
Hello,
Psion can define several types of devices none of which, to my knowledge, run Windows (at best Windows CE).
I am not familiar with how they work, particularly regarding the identifier rights that may be required to connect to them, nor whether it is generally possible from a Windows system.
Assuming we have the above, you need to write the command with the network path:
MD \\(IP or network name of the Psion)\path
Or access it beforehand with a NET USE command:
NET USE Z: \\(IP or network name) then:
MD Z:\path
NET USE Z: /DELETE
Or finally do the same thing via PUSHD POPD
PUSHD \\(IP or network name)
MD Path
POPD
Hello,
Thank you for your reply.
My problem is mainly that I don't know how to write this path.
I don't know how to access the folder "This PC\PSION\SD-MMC Card\IA_DONNEES" using the command prompt.
The PSION is running Windows Mobile 6.1
Formally, I don't know, it depends on how the access is made; if it's a network access, the device is generally identified (see in Explorer) not by the name of its "drive" but by a letter, C: when it's considered as a fixed unit, possibly another letter otherwise, and has a network name (for example "Psion") and an IP address (for example 192.168.1.10, knowing that access is only possible within the same workgroup).
We then have something like: MD \\Psion (or 192.168.1.10)\C$\IA_DONNEES
where the quotes are not needed (no special characters) and where C$ designates the name of the share for the destination folder (in this example, we have used the default administrative share under Windows C$).
If the device is connected via USB, the question obviously does not exist: it is identified by a drive letter, for example E:, and we simply use MD E:\IA_DONNEES.
If it is not recognized via USB with a drive letter, it means that the PC does not have the appropriate drivers to recognize it (a counter-example: my GPS is recognized by Windows under 2 letters, that of its system and that of the optional SD card, because the hardware drivers are installed under Windows and/or they are recognized upon connection).
If that’s not the case, either we find such drivers under Windows if they exist (I don’t know), or the USB connection is useless, then we return to the previous hypothesis (which is also not guaranteed): we would need to set up a real network share from a Wifi or Ethernet connection if feasible, and then gain sharing rights on this device, in short, it’s not a sure thing...
By the way, there is probably a mistake in the MD command if we let it take time to display by pausing after the command, as the syntax is incorrect not only in the non-recognition of the network path but also because "This PC" is just a symbolic link and does not exist: in the best-case scenario (to be verified), the command would foolishly create a sub-folder named "This PC" (and the rest) locally in the top-level sub-folder from where it is executed.

