Drive Window Abb

0 views

Skip to first unread message

Jude Petkus

unread,

Aug 3, 2024, 11:08:50 AM8/3/24

to zohillmyksua

I was wondering if there is a shortcut to getting to the main VeraCrypt drive window, where the drive letters are assigned. For example, Alt+X exits the program, Alt+M mounts a drive, etc. Is there a shortcut like that?

Don't think there's anything integrated into VeraCrypt, but if you have a shortcut to VeraCrypt on your Desktop, right click on it and left click 'Properties'. Put the cursor into the 'Shortcut key:' box, press Ctrl and Alt keys plus a number/letter key, left click 'OK', then that key combination will open the VeraCrypt main window. (This is a standard Windows procedure.)

This doesn't depend on any mouse movements or clicks, thus was easy to add to a macro. I added the macro to a hotkey (in the macro program, not VeraCrypt), and a simple keypress mounts the drive. Another macro simply sends Ctrl+Alt+v to unmount the drive. I mapped each of these macros to a button on my programmable remote and it works flawlessly.

The command.exe will auto-complete the line with the tab key, so it knows where I'm at. It just doesn't print to screen the result or actually get me there. This problem exists for the network drives as well.

Going back to the days of DOS, there's a separate "current directory" for each drive. cd D:\foldername changes D:'s current directory to the foldername specified, but does not change the fact that you're still working on the C: drive.

You're not using a Unix or Linux shell program. The cd command in Microsoft's command interpreter doesn't behave as the cd commands in such shells do. It behaves somewhat differently. In particular, it doesn't always change directory. In Unix and Linux shells, cd only ever sets the working directory. In Microsoft's command interpreter, cd sometimes queries it. There's no separate pwd command, so cd does two jobs.

If you give it no arguments, or an argument that is just a drive letter and a colon without a path, then it reports the current directory instead of changing it. If you give it no arguments, it reports the current directory of the current drive of the command interpreter process. If you give it only a drive letter and a colon as an argument, it reports the command interpreter process' current directory of that drive. Each drive has its own current directory in the command interpreter. (This is a fiction maintained by the run-time libraries for Microsoft's and several other vendors' implementations of various programming languages. Win32 itself doesn't work this way.)

So when you gave it d: as an argument, it reported the the command interpreter process' current directory on drive D to you, which happened to be D:\. If you'd given it no arguments at all, it would have reported C:\ to you.

If you want the cd command to always be in set mode and never be in query mode you need to add the /D option to it. This forces the command to always be in set mode, and also extends it so that it changes the current drive as well as changing a drive's current directory. (In other words, it works more like the underlying Win32 API actually does.)

Afraid this is incorrect. It's true from the days of DOS, but the command line in Windows NT and later is not DOS. In the command line that everyone uses today, you have the /D switch. The /d switch will change the current directory of the specified drive AND change to that directory. The /d switch must be specified before the path. For example:

I'm trying to establish a connection to my recently updated to Windows 11 PC, using a usb C to usb A connector from my Canon Eos R. It is failing to get a connection. I've used two separate usb leads with the same result. The camera has no problem appearing as a drive on a Windows 10 computer with the same leads, and its firmware version is up to date. This is really annoying, as it also makes it impossible to use the Canon utility software. Does anyone know a ready made solution, or whether there ever will be one?

Beyond that, here are some setup suggestions that might help:
* If it is not there already, make sure the camera is plugged into a USB on the back of your computer. (The front USB ports can be a little weaker sometimes.)
* Since you're having problems downloading, disconnect all other devices except the keyboard, mouse, and camera from the computer.
* Close any other programs you have open, and exit out of any image-related or printer-related programs in the system tray, found in the bottom right corner of your computer screen. If you don't see the program icons, look for a small triangle by the time display. Click that and you should see the icons. You should be able to close them by right clicking the icons and selecting the exit option.

If so, right click on the camera icon and select uninstall. When it finishes uninstalling, turn your camera off. Wait a few seconds then turn it on. A window should come up that says FOUND NEW HARDWARE DEVICE, keep clicking the NEXT button, until it finishes. Then see if you can connect to your camera once again.

If you see another camera, like a webcam, listed in the Device Manager, right click on it and select DISABLE. It is possible that you are getting interference from that device. When you are done with your tests, you can reactivate it by right clicking on it and selecting ENABLE.

No luck with any of these suggested tweaks. The only place where the camera shows up is in portable devices.. as an MTP USB device.. and as an eos digital device icon in printers and devices. It's barely there. And the troubleshooter can't help.

I think it's pretty obvious there is no Windows 11 driver for the Eos R yet. By comparison, I can see my old 6D as a separate drive, and open it like the others. I can get around all of this by putting the SD card in my computer's card reader. But I'm worried my canon xf300 will have the same issues, and I don't have a flash drive reader. But I do have an old Mac Pro running Catalina. So I'll see if Canon's XF utility software still reads the camcorder on that system. It should..

Nick2000 has covered many of the likely scenarios for an unrecognized USB device. If the Camera appears correctly in Device Manager, also look at Disk Management to see if windows has assigned a drive letter. If not, it will not display in Windows Explorer.

Thanks to all for the helpful suggestions. I gave up trying to get my new Windows 11 desktop to read the Eos R. But the latest Canon XF utility software reads my XF300 just fine, so I can download all my files without having to purchase a compatible flash drive adaptor. That's something of a relief, as the XF300 is now quite old, though still very useful.

Plugging the whole camera into your computer, means the card has an extra step to communicate with the camera, and the camera with the computer. Instead, simply turn off your camera, remove the card and plug it into a suitable card slot in the computer or get a USB card reader (lots available). The computer will recognize the card as a drive and you can then download your images.

Hi Tronhard, I've been using my USB cable since forever, and I've never had an issue until I moved to Windows 11. The issue here is strictly to do with Windows 11 and there is no hardware issue. That indicates to me that Canon have not produced a driver suitable for Windows 11, even though Windows 11 has been well signalled. Additionally, if you want to fry a memory card, handle it all the time. You will eventually succeed. The only time I ever remove a memory card from my camera (I now have 128MB card, so that very rarely happens) is when it gets full when I'm shooting. I haven't managed to succeed in that since I've had my EOS R, so there is no need. Handling cards almost guarantees that the card will fault. In all my time using digital cameras, over a decade, I've only ever had one fault, and that was on my first EOS camera, a 300D, when I tried to change the card while it was still writing. So, your suggestion is the worst possible suggestion. The best suggestion is that Canon gets its act together and fixes the issue, so that people don't have to remove the card from the camera. I will tell you this: I have done a test, by using the same cable that I previously used on my old computer, with the same brand motherboard, and also on my laptop before it was upgraded to Windows 11. When it was installed with Windows 10, there was no issue.

And I also don't agree with you about how fast it is to download images using a card reader. One, I have to take the card from camera, locate the card reader (I always have the USB cable attached to my computer for downloads, so I never have to locate that) and then I have to download all of the images, and then rename the folder to the date (done automatically by the software, according to camera and date) and then move the files from the various dates into the correct folder, a very time consuming an tedious task. I would also note that all of the later cameras, EOS R5 and forward, have a Windows 11 compatible firmware update. The EOS R does not, and yet it is still a currently for sale camera. Pretty slack, if you ask me.

Gavin, I sincerely and politely tried to help the OP (DROO) with their issue, but you have subsequently responded to this when you should have started your own thread to deal with your specific issues. Furthermore, your responses are full of angst that is not helping anyone.

To quote you: "Handling cards almost guarantees that the card will fault. In all my time using digital cameras, over a decade, I've only ever had one fault, and that was on my first EOS camera, a 300D, when I tried to change the card while it was still writing."

I have used cards in the way I have suggested for almost 20 years without any issue. The fact that you actually admit the one issue you had was your own action in pulling a card out while it was writing, is your issue as a user and there is no validity to extrapolate that to an essential inherent issue with cards themselves.

I worked on the design for Windows interface, and the intent was always that you should use the Eject feature (either in File Manager, or from the tool in the Windows tray) to ensure that the card does not have open file connections to the computer. Pulling the card prematurely creates a risk that the card will corrupt its FAT system and render it unusable. That is not an issue with Windows, or with cards per se, it is user error.