Digital BW, The Print

I wonder if you use \\127.0.0.1, it may be more reliable.
\\computername might depend on the Windows network browser.

However, both of these assume the network's enabled and the new XPSP2
firewall's restricting access (in additional to the regular NTLM login
control (So if the printer's not attached to your own computer, you
might actually need to login before you can print to that printer)) so
it's not the most reliable way of doing things, but short of writing a
driver, I don't know anything more reliable for local machine
printing. (Also there are other firewall products, like Norton
internet security, BlackICE, ZoneAlarm etc)

I will look up some USB / device driver information today. I haven't
touched any windows device drivers for a long long time. 

Michael

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Roy Harrington"
<roy@h...> wrote:
> 
> 
> Richard and Michael,
> 
> You guys seem to know a bit more of the Windows internals.  
> 
> As I guess you know, I'm getting to the USB port by simply redirecting
> output to \\computername\sharename.   This works OK as long as a network
> exists.  But obviously this is one of the major hassles with getting QTR
> running.  Systems that are sometimes connected and sometimes not are
> particularly problematic.  
> 
> I'd be really interested in any info about other ways to do this
that are more
> reliable and fool-proof.  Or possibly just some diagnostic testing
to help
> identify what's blocking output on a particular system.