Hi Detlef,
ah, I understand... I'm a Windows software developer trying to make our products running as smooth as possible under Wine. One of our products includes a fax printer driver and port monitor for faxing over ISDN boards.
The setup routine of our product will not use an .inf file to install the printer driver, but will use a ::GetPrinterDriverDirectory() call to get the printer driver dir, is then copying all the necessary files into this directory, fills a DRIVER_INFO_3 structure and then calls ::AddPrinterDriver()
This is probably a bit unusual, but not uncommon. I know some more professional products using this way to install printer drivers.
So to support this way of installing, the path returned by ::GetPrinterDriverDirectory() should definitely exist, which is also does under real Windows.
Am I wrong here?
Markus
-----Ursprüngliche Nachricht----- Von: wine.dev@web.de [mailto:wine.dev@web.de] Gesendet: Freitag, 12. Oktober 2007 14:14 An: wine-devel@winehq.org Cc: m.goemmel@compulab.de Betreff: Re: tools/wineprefixcreate.in: create default w32x86 path underspool/drivers
On Mi, 2007-10-10 at 13:10 +0200, Markus Gömmel wrote:
- "$CROOT/windows/system32/spool/drivers/w32x86" \
The above Path is created, when we add a Printer Driver in wine. Please update your wine.
When you do not start with a clean ~/wine, you need to remove the wine printers below "HKLM\System\CurrentControlSet\Control\Print\Printers" and the wine drivers below "HKLM\System\CurrentControlSet\Control\Print\Environments*".
A "wine notepad" does the rest.
When an application try to access this path, I expect, that they fail later, because we have no fake files for "w32x86/3/wineps.drv" and "win40/0/wineps16.drv" yet.
--
By by ... Detlef