Log message: Moved vxd support to winedos.
Patch:
http://cvs.winehq.com/patch.py?root=/home/winehq/opt/cvs-commit&id=8230
I did not know wine has vxd suppot I remeber trying kali and as it trys to load a vxd that does ipx->tcp/ip I was getting fixme's and the vxd was not loaded....
And to the topic why sould it be in dos when win95 and win98 support it I know winnt/winxp do not, I am not sure about the rest but this is not dos....
Hatky.
__________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
"hatky" == hatky hatkyinc@yahoo.com writes:
>> Log message: Moved vxd support to winedos. >> >> Patch: >> hatky> http://cvs.winehq.com/patch.py?root=/home/winehq/opt/cvs-commit&id=8230
hatky> I did not know wine has vxd suppot I remeber trying kali and as hatky> it trys to load a vxd that does ipx-> tcp/ip I was getting fixme's and the vxd was not hatky> loaded....
hatky> And to the topic why sould it be in dos when win95 and win98 hatky> support it I know winnt/winxp do not, I am not sure about the hatky> rest but this is not dos....
Wine doesn't support native VXD. But you can replace a native VXD with a builtin. But then you must rewrite the VXD.
Bye
Wine doesn't support native VXD. But you can replace a native VXD with a builtin. But then you must rewrite the VXD.
1. So why did they move VXD's to dos? 2. Do native VXD's in wine load for every windows version defined? 3. Do you mean a messy rewrite or just compilling with the winelib? 4. Since it's kind of a driver I get wine will never support real ones, not in the near fauter, right? 5. Was supporting real windows drivers ever came up? I know that if something like this would of been done it wouldn't be it wine but I wander, is there such a project?
__________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
- So why did they move VXD's to dos?
Dunno.
- Do native VXD's in wine load for every windows
version defined?
I think so, yes.
- Do you mean a messy rewrite or just compilling with
the winelib?
Basically a total rewrite. VxDs need to run in ring zero (kernel mode), and obviously the Linux kernel is pretty different to the windows kernel.
- Since it's kind of a driver I get wine will never
support real ones, not in the near future, right?
Probably not. I'm sure somebody reasonably smart with a lot of motivation could do it though.
- Was supporting real windows drivers ever came up? I
know that if something like this would of been done it wouldn't be it wine but I wander, is there such a project?
It has been raised in the past yes, especially as some apps need VxDs to run properly, but there is no easy solution to using them.
thanks -mike
- Was supporting real windows drivers ever came
up? I
know that if something like this would of been
done it
wouldn't be it wine but I wander, is there such a project?
It has been raised in the past yes, especially as some apps need VxDs to run properly, but there is no easy solution to using them.
I actually ment a real windows driver not a VXD but I forgot that about every windows version has other drivers but never the less it seems like if there was such a thing I could speed up games a lot since I remeber test from "tom's hardware" and any display test did beter on windows, asumeby due to drivers
__________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
hatky wrote:
Wine doesn't support native VXD. But you can replace a native VXD with a builtin. But then you must rewrite the VXD.
- So why did they move VXD's to dos?
because it's only used by some DOS based app
- Do native VXD's in wine load for every windows
version defined?
native VXD are never and will never be loaded by wine
- Do you mean a messy rewrite or just compilling with
the winelib?
Wine builtin VXD are a plain rewrite of existing VXD in Windows 3.x and 9x. But, most of the services available on those systems in Windows are not available in Wine (think of hardware access, DMA, interrupt...). So, I doubt we could port an existing driver (from source) to Wine. The only viable way is 1/ get the spec of the VXD, 2/ reimplement it in Wine.
- Since it's kind of a driver I get wine will never
support real ones, not in the near fauter, right?
yes.
- Was supporting real windows drivers ever came up? I
know that if something like this would of been done it wouldn't be it wine but I wander, is there such a project?
yes, but it's not Wine, it's ReactOS (but it will support the NT driver model, not the Win 3.X / 9x one).
A+
On Sun, May 18, 2003 at 04:53:08AM -0700, hatky wrote:
- So why did they move VXD's to dos?
Because they are the drivers for DOS-based Windows versions (9x, ME)? (Just guessing here)
- Do native VXD's in wine load for every windows
version defined?
No, they don't work in *any* version.
- Do you mean a messy rewrite or just compilling with
the winelib?
A complete reimplementation.
- Since it's kind of a driver I get wine will never
support real ones, not in the near fauter, right?
Correct.
- Was supporting real windows drivers ever came up? I
know that if something like this would of been done it wouldn't be it wine but I wander, is there such a project?
Drivers need hardware access, expect a certain memory layout, access to interrupts and whatever. Actually, this sort of project exists, it's called Bochs and implements a virtual PC. I think nothing less than that is going to work.
Ciao Jörg
-- Joerg Mayer jmayer@loplof.de We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
-
Eric Pouech -
hatky -
Joerg Mayer -
Mike Hearn -
Uwe Bonnes