http://bugs.winehq.org/show_bug.cgi?id=26704
Summary: SIV can no longer access it's driver - IoCreateSymbolicLink() broken? Product: Wine Version: 1.3.17 Platform: x86 URL: http://rh-software.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: ray@pobox.co.uk
SIV (http://rh-software.com/) can no longer access it's driver, the driver seems to start, but there is no SIVDRIVER to \Device\SIVDRIVER mapping. I have checked and both the IoCreateDevice() and IoCreateSymbolicLink() calls worked, but the link is missing. This used to work with Wine 1.3.5.
Using the SIV 4.17 release you can check the MS-DOS names using Menu->System->DOS Devices which uses QueryDosDevice( NULL, buf, 65535 ).
I have also tried to create the mapping using DefineDosDevice( DDD_RAW_TARGET_PATH, ... ).
http://bugs.winehq.org/show_bug.cgi?id=26704
Andrew Nguyen arethusa26@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, regression
--- Comment #1 from Andrew Nguyen arethusa26@gmail.com 2011-04-09 15:15:00 CDT --- Please perform a regression test:
http://wiki.winehq.org/RegressionTesting
(In reply to comment #0)
SIV (http://rh-software.com/) can no longer access it's driver, the driver seems to start, but there is no SIVDRIVER to \Device\SIVDRIVER mapping. I have checked and both the IoCreateDevice() and IoCreateSymbolicLink() calls worked, but the link is missing. This used to work with Wine 1.3.5.
Using the SIV 4.17 release you can check the MS-DOS names using Menu->System->DOS Devices which uses QueryDosDevice( NULL, buf, 65535 ).
Is this the method of determining whether the symbolic link exists? I don't see a SIVDRIVER listed in the SIV's DOS Devices listing in wine-1.3.5.
http://bugs.winehq.org/show_bug.cgi?id=26704
--- Comment #2 from ray@pobox.co.uk 2011-04-09 17:40:46 CDT --- Created an attachment (id=34015) --> (http://bugs.winehq.org/attachment.cgi?id=34015) Extract from SIV save file generated with Wine 1.3.5
Extract from SIV save file generated with Wine 1.3.5
http://bugs.winehq.org/show_bug.cgi?id=26704
--- Comment #3 from ray@pobox.co.uk 2011-04-09 17:42:33 CDT --- (In reply to comment #1) Is this the method of determining whether the symbolic link exists? I don't see a SIVDRIVER listed in the SIV's DOS Devices listing in wine-1.3.5.
I can't really tell. I have attached an extract of what I got when I tested with 1.3.5
http://bugs.winehq.org/show_bug.cgi?id=26704
--- Comment #4 from ray@pobox.co.uk 2011-04-10 09:00:47 CDT --- I have figured out what is going on. The issue was by driver getting confused by invalid information being passed in by Wine. The real problem is the same as in http://bugs.winehq.org/show_bug.cgi?id=20083. I will code around this again.
http://bugs.winehq.org/show_bug.cgi?id=26704
ray@pobox.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Component|-unknown |ntoskrnl See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=20083 Resolution| |DUPLICATE
--- Comment #5 from ray@pobox.co.uk 2011-04-10 16:34:29 CDT --- Same issue, PIO_STACK_LOCATION->FileObject being 0x66666666 again.
*** This bug has been marked as a duplicate of bug 20083 ***
http://bugs.winehq.org/show_bug.cgi?id=26704
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Jeff Zaroyko jeffz@jeffz.name 2011-04-10 18:43:12 CDT --- Closing duplicate.