QUESTION: Where is my wine’s C: drive? SHORT ANSWER: /home/$USER/.wine/drive_c As you probably know Linux and Windows have quite a different approach to maintaining and presenting files-systems, files and folders. Linux is using the “virtual tree” approach whereby the system has knowledge of all of its paths, arranged in one global tree hierarchy, with the the various storage devices (hard disk, tape drives, flash drives, CD-ROMs, network drives) attached or as the linux jargon has it “mounted”, to this virtual tree. Windows has used the “hardware-based” approach, where each physical drive (or logical drive, a.k.a. “partition”) is assigned a drive letter followed by a colon (A:, B:, C: etc). Under each drive there is a hierarchical tree system very much like in linux but there is no one global absolute hierarchical tree of paths and files – you have as many trees as there are drives (drive letters) known to your system.

Create And Mount ISO Files For Free With These Tools. 7 and most recently, Mac OS. But my new laptop doesn't have a disc drive. How do I make an.

Historically, the first two drive letters A and B were reserved for floppy drives. Thus, the first hard drive was, designated as C.

Not that you could not re-arrange your drives and have A: as your hard-drive, Q: as your CD-ROM and Z: as your floppy but 99% of programs (and humans!) would base a lot of their assumptions on C: being the first hard drive in the system and so most developers would design their applications with that in mind. On the C: drive, it is common to have such well-known paths as “C: Windows”, “C: Documents and Settings” and “C: Program Files”. Note that “C: Documents and Settings” is now renamed to “C: Users” in Windows 7. Most program installers would typically offer the user to install themselves somewhere underneath “C: Program Files” and store program config settings in the user’s folder under “C: Documents and Settings”. Since most Windows applications will rely on the system having at least one drive (which is typically named C:, as explained above), wine also needs to mimic this behaviour and maintain at least one virtual hard-disk (C:) so that the windows programs you want to use could run normally. The question is – where is it? Where is wine’s C drive?

You can’t have /C: as the colon character “:” is not a legal path character in Linux. Perhaps if could be named /C, then?

Yes that could be a possible solution (in theory), however there’s some problems with that as well. Most users would not have permissions to create folders under the root directory.

And, yet another problem with this setup would be that different users could overwrite their apps and data if all of their wine instances all wrote and read from one global location. So, how can we find out where is our wine’s C: drive? Well we could run the winecfg utility and see what it has to say about this? Looking in the Drives tab of winecfg, however, we can see that the C: drive is mapped to./drive_c, which is obviously not very useful (as this is a relative path and could be anywhere). Well, at least we know that it is called drive_c How can we use this information to find the C: drive used by wine? Well for one thing we could run “locate drive_c” and see if it finds any folders named drive_c in our system!

Start task manager for mac. Apple Footer • This site contains user submitted content, comments and opinions and is for informational purposes only.

Type “locate drive_c” in your terminal program. Also, a HUGE reason to know where “virtual c” is located, is what I am running into.

I have a 2nd ‘phyisical drive’ that has Windoze on it, and so now I need to make Wine know that my ‘c’ needs to be on that 2nd drive – so, how do i do that? I did not want to do a ‘side-by-side,’ so I dedicated a ‘main hd’ to Wine, and left Windoze on the 2nd HD – it sees it just fine, like 250GB whatever, but how do it get the info in Wine, in order to tell Wine, “Hey, look on this other HD for any Windoze programs?” Thanks in advance! This answers most basic questions and a very detailed troubleshooting lesson as well, however I need to get access to the C: drive without having to use Wine executing a file because I need to move a set of files into the C: drive, not the Program Files in the C: drive, let alone the files not being executable in the first place. The reason for this is I will be executing a file that will need those files in the appropriate file location (Windows wise), to function. The setup I am trying to achieve is Jeutie’s Blizzlike Repack 3.3.5.