Hi.
>From which configuration does the "ERROR_INVALID_NAME" came from,
when calling GetDefaultPrinter(NULL, &size) and no Printer is installed?
This Test is Present in the current "dlls/winspool/tests/info.c".
MSDN told us, that we receive an "ERROR_FILE_NOT_FOUND", if no Printer
is installed:
http://msdn.microsoft.com/library/en-us/gdi/prntspol_0hma.asp
I get the "ERROR_FILE_NOT_FOUND" on win98se, winme, w2k and win2003 in
this Situation.
--
By By ...
... Detlef
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I think after the 10 or more patches to the Wintab dll that I submitted
last month, I should say something about it's status...
And of course thank Alexandre for applying those patches.
P.S. I won't be available from the 15th for about a week or so.
So, if you have any questions, I'm afraid you might have to be patient.
Hope this is of interest to someone
-Rob.
******Applications: Current status***********
***In Painter 5
*Cursor pressure works. (Therefore is usable by most)
*Cursor orientation is a little odd: The orientation maths needs to be
re-done.
*No eraser. Haven't yet cracked what enables the eraser.
*Doesn't work in desktop mode: Need to map to desktop coordinates.
*Repeats windows bugs where cursor looses pressure/orientation info
almost bug for bug (Is this a feature? ;-)
*Cannot detect pressure/orientation int the "Brush Tracking" window: The
tablet context is attached to the main window, so no events get to the
popup, even if they overlap.
This is not how windows wintab functions.
***In Photoshop 6.
*Can only get tablet data in desktop mode: This is because the tablet
context is attached to the desktop. Which generates/receives no wine
events outside desktop mode.
* Eraser and pen pressure working. *But* to get them working, you must
have 3 XInput devices listed in your XF86Config file, They need to be
the last entries in the "ServerLayout" section and the following order:
eraser, tablet mouse. This is a far from ideal way of specifying the
devices Wintab should use :-/
I'll document this if someone can point me to a good place to put the docs.
*******To Do*************
1. Look at X11 errors. There appear to be some errors that deny some
users the
ability to access Wintab enabled apps. (I think I know how to fix this)
2. Improve orientation data. Orientation comes in as X-Y coords
(Implicit Z), and has to leave as spherical coords. This calculation
needs to be re-done.
3. When tablet context is on top, let it read XInput events from all the
app's top-level windows. (This simulates the fact that the context is
usually designed to cover the whole screen)
4. When tablet context is attached to desktop, read XInput events from
all the app's top-level windows.
5. Tests
~ --My current philosophy on tests is...
~ Use Photoshop & Painter, any formal tests
~ can be written if anyone else gets involved in patching Wintab, to
avoid regressions, and conflict.
**********Long term to do (Anyone interested?):*********
There's a lot of work that could be done here, but what gets done
and who does it probably depends upon whether anyone finds an app that
needs these features. I'd love to implement these, but realistically, I
don't
foresee doing this unless someone hires me to do so ;)
1. Improve configuration of wintab.
Wintab could probably do with some information entered into the
config file, to avoid the user having to
hack their Xfree86cfg file.
2. Handle Z-Order of context properly.
This entails
*sharing Z-Order between apps.
*Working out exactly what role windows have in
determining tablet context z-orders.
*Allow tablet contexts that don't cover the whole
screen/tablet.
*Handle inter-application clipping of tablet contexts
*Allow all application's windows to receive tablet events when tablet
context is on top
3. Implement non-system tablet contexts (Where system cursor not moved
by pen or mouse)
4. Unicodify
5. Implement various wintab extensions.
6. Implement wintab manager functions.
7. Tests.
*********Unknowns*********
1. How are wintab contexts are raised lowered?
Contexts have their own z-order independent of windows, and their own
viewport concept, based upon the tablet's coordinate system, not that of
the OS.
It appears that entering, or clicking on the window the tablet context
is attached to will raise/lower the context.
But I haven't done much testing on this.
In particular, what happens if more than one app request their tablet
context is attached to the desktop?
2. How Painter detects the eraser.
Have 3 possibilities
i. Windows can detect an eraser, and sends specific messages.
(I'm sure I've seen this, but can't work out where!)
ii. Only works if tablet and cursors are named correctly.
(Probably linked to wacom tablets only).
iii. I've missed something
3. Requirements of other applications
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCC8zI2vfwxdLxwWYRAsisAJ4q2gAYTgRc6f9wDI+Ruv943eDxOQCfcl3s
/ZKMUGwQOuw/SIIbOkIUbd0=
=R4M7
-----END PGP SIGNATURE-----
Hi Wei Li,
last year, you asked in
http://www.winehq.org/hypermail/wine-users/2004/06/0086.html
> I could not find the info regarding what operating systems > (such as AIX 5L v5.2, HP-UX 11i, Solaris Release Level > 9) will Winelib run on non-x86 machines. I'll really
> appreciate it if someone can provide my related link or
> info. I can only find the following link regarding the
> supporting OS but it does not provide Winelib's supporting
> OS info:
> http://www.winehq.org/site/docs/wine-faq/index 3.1.
> Under what hardware
> platform(s) and operating system(s) will Wine(Lib) run?
I'm sorry nobody got back to you -- the wine-devel
mailing list might have been a better place to ask.
I believe winelib runs on the following non-x86 operating
systems: Linux, Solaris, Mac OS X, and FreeBSD.
There's no reason in principle it couldn't run on AIX or HP/UX.
Some work has been done on an HP/UX port, but some
assembly would be required to complete it:
http://www.winehq.com/site/?issue=241#HP-UX%20Port
Cheers,
Dan
--
Wine for Windows ISVs: http://kegel.com/wine/isv
Hi,
I'm trying to use a program called "siap"[1] under wine. It's the required
program to pay taxes that the Argentinian government uses.
So, it's quite important for the free software community in Argentina to be
able to use it in a free software environment. However, I haven't heard
of any real success on it, so far.
I've been trying to make it run using winetools[2], and differents versions of
wine. The furthest I've gone, has been with version 20050310 and all the
"plugins" that winetools provides, installed.
Only then, could I install the application, run it, switch between the
different modules (although it worked only sometimes), but I can't really use
it.
There are a couple of important widgets that seem to be incompatible with
wine. But as I'm not an expert neither in Windows nor in wine, the one I could
really track down is a TreeView widget (from comctl32.dll) (from the main
window of the program), that is not fully implemented in wine, and by using a
native comctl32.dll (I tried using the win98, winme, win2k libraries) the
widget would work but some of the other stuff, like switching
to one of the modules wouldn't.
I made a screenshot to make this clearer, the wine version[3] and the w2k
version[4].
So, what should I do next?
Is there some documentation of how to implement a certain Windows widget in
wine?
Is anybody working in this dll, or has worked on this widget?
I'd appreciate any comments.
Thanks,
[1] http://www.afip.gov.ar/programas/siap_main.asp (spanish only)
[2] http://www.von-thadden.de/Joachim/WineTools/
[3] http://gnuservers.com.ar/~maxy/wine/siap-wine.png
[4] http://gnuservers.com.ar/~maxy/wine/siap-w2k.png
--
Saludos,
/\/\ /\ >< `/
Grand Theft Auto... the never ending struggle to get it working.
First I thought it was broken because of OLE...subsequently found out
the installer was freezing, because of hidden message boxes. Now I've
managed to install it in Desktop mode, but it dies when ran, with no
output of any kind...
Investigating shows:
000b:Call kernel32.SetUnhandledExceptionFilter(2027f1a8) ret=0115fbe9
000b:Ret kernel32.SetUnhandledExceptionFilter() retval=0115fb7c
ret=0115fbe9
000b:Call kernel32.GetModuleHandleA(015459f4 "mscoree.dll") ret=0115ae6b
000b:Call ntdll.RtlInitAnsiString(7fcaf528,015459f4 "mscoree.dll")
ret=2018d4fc
000b:Ret ntdll.RtlInitAnsiString() retval=00000000 ret=2018d4fc
000b:Call ntdll.RtlAnsiStringToUnicodeString(7fffcbf8,7fcaf528,00000000)
ret=2018d55b
000b:Ret ntdll.RtlAnsiStringToUnicodeString() retval=00000000 ret=2018d55b
000b:Call ntdll.RtlInitUnicodeString(7fcaf52c,7fffcc00 L"mscoree.dll")
ret=201a554d
000b:Ret ntdll.RtlInitUnicodeString() retval=00000018 ret=201a554d
000b:Call ntdll.LdrGetDllHandle(00000000,00000000,7fcaf52c,7fcaf534)
ret=201a555b
000b:Ret ntdll.LdrGetDllHandle() retval=c0000135 ret=201a555b
000b:Call ntdll.RtlNtStatusToDosError(c0000135) ret=201a558a
000b:Ret ntdll.RtlNtStatusToDosError() retval=0000007e ret=201a558a
000b:Ret kernel32.GetModuleHandleA() retval=00000000 ret=0115ae6b
000b:Call kernel32.ExitProcess(00000001) ret=0115ae8f
000b:Call ntdll.LdrShutdownProcess() ret=201b03bd
Looks like it doesn't like the missing mscoree.dll.
I thought the .NET framework was not a core windows dll?
Why would it require it? Also, installing a native dll doesn't seem to
help...
Susheel Daswani wrote:
> For my 'Antitrust & IP' course this semester I am writing a brief
> about why I think the remedy in the Microsoft antitrust case was
> inadequate.
Back in the day, I wrote an essay about this; it's online at
http://kegel.com/remedy/
in particular,
http://www.usdoj.gov/atr/cases/ms_tuncom/major/mtc-00028571.htm
I now think my essay was naive, but hey, I was young :-)
It would be interesting to see the complaints sent to the Technical Committee
( http://www.thetc.org/ ) but I doubt they're public.
You might also want to read http://www.lessig.org/content/testimony/msft/msft.pdf
if you haven't already.
> So my question for the WINE developers is "What materials from
> Microsoft would most aid the development of WINE"? The Windows API is
> of course public, so my guess is that isn't a huge bar to creating
> WINE. So what are the bars? Is it simply the scope of the project?
> Is there information that MS could divulge that would greatly aid the
> WINE effort? Would open sourcing part of Windows help?
As others have noted, the Windows API is not completely public
nor particularly well-defined. This makes things harder, but
it's not really the main obstacle.
Here are a few things a judge could order Microsoft to do that would help Wine:
* order them to break up into two companies, one for operating systems and .net, one for everything else
* donate gobs of cash to Wine
* offer a perpetual, transferrable, royalty-free, GPL-compatible license for its protocols and data formats
* support ODF in Microsoft Office
That last item is kind of indirect. It would make it much easier for
everybody to switch to OpenOffice, which would make it much easier
for everybody to switch to Linux, which is the whole point of Wine.
- Dan
--
Wonder why Aunt Tilly still won't use Linux? See http://kegel.com/linux/comfort
The patch has been found that breaks Photoshop, but 0.9.6 still brakes PS.
On 1/6/06, Aleksey <anime4christ(a)gmail.com> wrote:
> Great! Thanks!
>
> On 1/1/06, Elvis Pranskevichus <elprans(a)gmail.com> wrote:
> > Aleksey wrote:
> > > Yesterday I upgraded to WINE 0.9.3, and then tried running Photoshop
> > > 7. Photoshop gave me a hardware error. I thought, no problem, I'll
> > > just reinstall it, same result. Then I reconfigured WINE using
> > > winetools and tried again, same thing. Here is what I got in the
> > > Terminal when running Photoshop 7:
> > >
> > > fixme:actctx:QueryActCtxW stub!
> > > fixme:font:WineEngRemoveFontResourceEx :stub
> > > fixme:win:EnumDisplayDevicesW ((null),0,0x7fa7de2c,0x00000000), stub!
> > > fixme:win:EnumDisplayDevicesW
> > > (L"\\\\.\\DISPLAY1",0,0x7fa7de2c,0x00000000), stub!
> > > fixme:mscms:EnumColorProfilesA ( (nil), 0x7fa7e694, 0x7fa7e1ac,
> > > 0x7fa7e6f4, 0x7fa7e704 ) stub
> > > fixme:win:EnumDisplayDevicesW ((null),0,0x7fa7de34,0x00000000), stub!
> > > fixme:win:EnumDisplayDevicesW
> > > (L"\\\\.\\DISPLAY1",0,0x7fa7de34,0x00000000), stub!
> > > fixme:mscms:EnumColorProfilesA ( (nil), 0x7fa7e69c, 0x7fa7e1b4,
> > > 0x7fa7e6fc, 0x7fa7e70c ) stub
> > > err:shell:HCR_GetFolderAttributes HCR_GetFolderAttributes should be
> > > called for simple PIDL's only!
> > > fixme:font:WineEngRemoveFontResourceEx :stub
> > > fixme:font:WineEngRemoveFontResourceEx :stub
> > >
> > > Then I tried installing Photoshop CS, knowing that it worked fine with
> > > 0.9.2. Photoshop CS told me that certain required files was missing,
> > > but I forgot to get down the results from the Terminal. After that I
> > > downgraded to WINE 0.9.2 and both versions of Photoshop work great.
> > >
> > > A little side note: ImageReady 7 works great under 0.9.3, I did not
> > > test ImageReady CS. ImageReady 7 works great under 0.9.2 also, but
> > > ImageReady CS crashes.
> > >
> > > God Bless.
> > > - Aleksey
> > >
> > >
> >
> > Hi,
> >
> > I've found the patch that breaks the thing. GIT commit-ish is 0b17529332b0ef5ee57873afd4ded6f359e76781. (http://source.winehq.org/git/?p=wine.git;a=commit;h=0b17529332b0ef5ee57873a…).
> >
> > I haven't looked at it deeply, just done some git bisect's.
> >
> > --
> > Elvis Pranskevichus - elprans(a)gmail.com
> >
> >
>
To see how reasonable it might be to use OOo 2.0.1 and Firefox 1.5
under Wine routinely, I benchmarked their startup time
on a Fedora Core 5 test 2 system under four conditions:
native vs. with wine from cvs, and with 416MB RAM vs. 96 MB RAM
(by booting with mem=96M; this was to simulate running on
one of those cheapo 128MB boxes that uses shared video RAM).
This was on a zippy Compaq Presario 3000 Athlon 64 3000+.
All apps were downloaded from openoffice.org and mozilla.com.
Results for first run of app after booting (1st column is startup time):
5 Firefox run1 native 416MB
12 Firefox run1 wine 416MB
11 Firefox run1 native 96MB
15 Firefox run1 wine 96MB
11 ooo run1 native 416MB
15 ooo run1 wine 416MB
60 ooo run1 native 96MB
37 ooo run1 wine 96MB
So wine is 1.4 to 2.5 times slower at app startup generally,
but when ram is really short, win32 openoffice starts
up with wine 1.5 times *faster* than the native linux version!
(Maybe because the Microsoft tools are better at avoiding I/O
or relocations during loading?)
I then measured how long it took to start up the app the second
time, when the cache was nice and hot:
3 Firefox run2 native 416MB
4 Firefox run2 wine 416MB
4 ooo run2 native 416MB
6 ooo run2 wine 416MB
4 Firefox run2 native 96MB
6 Firefox run2 wine 96MB
36 ooo run2 native 96MB
28 ooo run2 wine 96MB
The times are uniformly faster on the second run,
but the patter holds, i.e. wine is 1.4-1.5 times slower than native
generally, but win32 openoffice under wine is 1.5 times *faster* than
the native version when starved for RAM.
- Dan
--
Wine for Windows ISVs: http://kegel.com/wine/isv