1. winov32101.exe Driver
2. WOV32101.TXT File Contents

WOV32101.TXT Driver File Contents (winov32101.exe)

What changed from version 1.00 to 1.01 (16 June 2000)
-----------------------------------------------------

Summary
-------

- The driver doesn't install correctly in Windows 2000.
    First of all, Windows NT 4.0 installs all driver files to
    %windows%\system32\spool\drivers\w32x86 and
    %windows%\system32\spool\drivers\w32x86\2. The 2 is for the kernel
    mode type drivers used in NT 4. Windows 2000 only installs the files in
    %windows%\system32\spool\drivers\w32x86\2.  The API function
    GetPrinterDriverDirectory returns %windows%\system32\spool\drivers\w32x86
    and this is where the driver looks for its files - especially
    WOVL0409.LNG and WOVCP.EXE. The driver has been changed to add the
    "\2" to the path returned by GetPrinterDriverDirectory which is
    where version 2 drivers should be.
    Second, the "Datamax" printer item in the "Datamax" Program Manager
    group was not being created. This item is how the end-user launches
    the driver's control panel (WOVCP.EXE). The driver invokes wovcp to
    create the Program Manager group and item. wovcp uses the printer name
    for the item in the "Datamax Printer" group. The name was supplied to
    the driver in the form \\servername\printername in NT 4. In Windows
    2000 the name is given as \\servername\printername,LocalSplOnly. This
    name causes the DDE function in Program Manager, used to create the
    item, to fail. The driver now strips the ",LocalSplOnly" from the
    printer name.