Le lun 20/09/2004 à 19:10, J. Grant a écrit :
Hi Vincent,
Thanks for your reply.
Upgrading from a quite old version I may add... ($VAR-style variables in config are long gone, maybe a year now).
Yep, this WINE build was last used when I wrote an article on WINE 2003-02-18. I do not see why WINE should not be compatible with a config file which is only 17 months old though. Compatibility should be for the life of a product in use IMO. If that development time is too not available for WINE, I can accept that, but non-compatibility with recent config files like this should be avoided if possible in my view.
Talk to Alexandre on that :) Although 17 months begins to be old for Wine.
C:\windows>ls File not found
ls is Unix, you don't have access to it in wcmd. Use dir.
I had hoped for an alias, in the same way that "dir" works in nearly all GNU/Linux distros.
Does Windows support aliases? Does it provides ls? If the answer is yes to any of those two questions, then Wine is at fault, else no.
The f:: (double-colon) links point to the (Unix) device behind the Windows dir. They were created from your config.
Ok.
Wine just created the symlinks from your config. You had com2 and com3 in it, so it created the link.
Then I guess com2 and com3 were default in the mdk9.0 wine package "config" file, as I did not add those lines myself.
Probably. Nowadays most users don't have a config file.
Vincent