search for: drive_e

https://bugs.freedesktop.org/show_bug.cgi?id=95251 Bug ID: 95251 Summary: vdpau decoder capabilities: not supported Product: Mesa Version: 11.2 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

I am attempting to install a windows base business management program on Wine 0.9.60 I tried to install using the wines windows XP, but ran into shell32.dll problems. Iread Sticky's notations, and switched to wines windows 98. This allowed the setup.exe to move ahead, but when it looked at the S drive location it wanted to install to, it found no allocated space. It needs 483803. I do not

Attached file I use to test GPT code. I used qemu 1.2 with seabios with LSI enabled and a patch diff --git a/src/blockcmd.c b/src/blockcmd.c index 77c690f..df4fb1e 100644 --- a/src/blockcmd.c +++ b/src/blockcmd.c @@ -146,7 +146,7 @@ scsi_init_drive(struct drive_s *drive, const char *s, int prio) // We do not bother with READ CAPACITY(16) because BIOS does not support // 64-bit LBA

I keep reading on this list where drive C: is referred to as "~/.wine/drive_c" but on my system (due to no special smarts on my part that would be "~/.wine/dosdevices/c:" instead. Why this difference? Are the ones who post basing their operation on an older way of doing things? The ability to use "c:" rather than "drive_c" seems nicer IMNSHO. FWIW,

On 12/16/2013 05:18 AM, Frediano Ziglio wrote: > > Surely should apply to 4.xx where they was developed but I think I send > them for 5.xx. mbr part of patches was merged time ago. > Unfortunately I had no time to update other patches. If I remember there > was a problem on the way ADV was implemented (using the same sector). > > Unfortunately my company business required to