Hi, I am currently using a Windows program, that is trying to read a raw-format drive through USB. I've tried making a symbolic link to the device from my dosdevices directory ln -s /dev/disk3 x: but the program still doesn't recognise it. This program currently works on winxp. Is there any way to read such a drive through wine? Thanks, Anna.
On 2/19/11 6:42 AM, annacegu wrote:> Hi, > > I am currently using a Windows program, that is trying to read a raw-format drive through USB. > > I've tried making a symbolic link to the device from my dosdevices directory > ln -s /dev/disk3 x: > but the program still doesn't recognise it. > > This program currently works on winxp. > > Is there any way to read such a drive through wine? >If the program uses a Windows system driver (.sys), no. Linux does not allow users to run this type of driver. If the program accesses the drive, maybe. Run the lsusb program when you insert the drive and see what Linux is reporting as the drive. Since the drive is 'raw' it should not have a drive letter. This is why I wrote the first part of my comment. James McKenzie
annacegu wrote:> I am currently using a Windows program, that is trying to read a raw-format drive through USB.No, for several reasons: 1. Wine does not talk directly to USB devices 2. Wine does not support any low level file-system operations 3. Even if your program can do the file-system part itself, Wine still doesn't have all low-level storage operations (ioctls). 4. Wine does not fill all registry places where programs like yours looking for the disk. The last reason is why your program doesn't see the disk. But even if it would, it won't work.
On 2/19/11 6:42 AM, annacegu wrote:> Hi, > > I am currently using a Windows program, that is trying to read a raw-format drive through USB. > > I've tried making a symbolic link to the device from my dosdevices directory > ln -s /dev/disk3 x: > but the program still doesn't recognise it.Looks like you're on Mac (and not quite clueless, unlike most Mac users :). In that case, you want the device file that has an 'r' tacked on the beginning: ln -s /dev/rdisk3 x:: and when you link it, you want to tack an extra colon onto the DOS name (like above). The link with only one colon is to the volume's root directory; two colons is for the device file.> Is there any way to read such a drive through wine?If you have the links set up properly, it should work. If it doesn't, post back with the stuff that Wine prints to Terminal (if it's really long, post to pastebin or some such, then post the link here). Vitaliy ("vitamin") might be right, though, about the program not being able to find the disk because it's looking in a place that Wine doesn't expect it to yet. Filing a bug in that case might be useful. He's definitely right about Wine not being able to directly talk to USB devices. Don't bother filing a bug for that: it's a well-known problem that isn't likely to get fixed anytime soon, sadly. Chip
Hi, Thank you all for your replies. I made the link in the dosdevices directory. dmesg gives me the following: disk1: ioctl(_IOR,'t',19,44) is unsupported. disk1: ioctl(_IOWR,'d',100,16) is unsupported. disk1: ioctl(_IOR,'t',19,44) is unsupported. disk1: ioctl(_IOWR,'d',100,16) is unsupported. And this is the message I get when I start the program in wine (the program doesn't show up the raw disk): err:listview:LISTVIEW_WindowProc unknown msg 109d wp=00000000 lp=00000000 err:listview:LISTVIEW_WindowProc unknown msg 109d wp=00000000 lp=00000000 I don't know if that's related. Regards, Anna.
James McKenzie wrote:> Ah, a fellow Mac user. I'll look at how this happens and Charles Davis > had a suggestion for you earlier in this forum/mail list thread. > > James McKenzieHi James, Thanks for that. Yes I did try Charles' suggestion (the symlink), but it's not showing up in the program's drive list still.. (see post @2:28pm for further details) Regards, Anna.
James McKenzie wrote:> Also, I just plugged in my USB 'stick' and it showed up as four devices > under the /dev directory (you have to be a system administrator AND > access this through Terminal.) > > The following is the result of using the ls (list) with the -l (long > format) command for these devices: > > brw-r----- 1 <user> operator 14, 10 Feb 19 18:39 disk4 > brw-r----- 1 <user> operator 14, 11 Feb 19 18:39 disk4s1 > > This is the block access (b) and the device is only read/write for me. > > crw-r----- 1 <user> operator 14, 10 Feb 19 18:39 rdisk4 > crw-r----- 1 <user> operator 14, 11 Feb 19 18:39 rdisk4s1 > > This is the character level access (c) and the same 'rights' are > bestowed upon the device. You might want to try this with the device > not plugged in and when it is plugged in. > > You want to map the 'raw' level (in my case rdisk4) to a drive letter, > if that is what the program requires. Otherwise, and if the program > requires the use of a hardware Windows driver, you are out of luck > trying to get this to work with Wine as it is now. > > James McKenzieMine is showing up as only 1 USB, probably because it's not formatted as any filesystem: crw-r----- 1 <user> operator 14, 4 20 Feb 14:06 rdisk1 brw-r----- 1 <user> operator 14, 4 20 Feb 14:06 disk1 When the device is not plugged in, it's not showing up on the ls. What do you mean by a hardware Windows driver? Does this include drivers that come default with windows? Anna.
Charles Davis wrote:> Actually, these are from another program (winemenubuilder). > > Which version of Wine are you running? This shouldn't happen with recent > Wine 1.3. It's usually a good idea to be running the latest Wine from > the development branch anyway. The "stable" versions were designed to > run particular apps (read: Microsoft Office, Adobe Creative Suite--not > that the Windows versions of either of those matter to us Mac users :) > well, but don't get all the fixes that the development version gets. > > > err:listview:LISTVIEW_WindowProc unknown msg 109d wp=00000000 lp=00000000 > > err:listview:LISTVIEW_WindowProc unknown msg 109d wp=00000000 lp=00000000 > > > So that really is all, huh? > > > Let me know if you stil need the long version.. > > > Then we definitely need more info. > > Like I said, if the log is really long, don't post the whole thing here. > Instead, post it on a site like pastebin, then post a link to it here. > > ChipHi Chip, I'm running v 1.3.7. Here's the full trace: http://pastebin.com/5AUS7iSF Thanks, Anna.