Andre
Fri Jul 01 11:07:35 CDT 2005
Seems complicated and unlikely to work.
--
Andre
Extended64 |
http://www.extended64.com
Blog |
http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
"Tony Sperling" <tony.sperling@dbREMOVEmail.dk> wrote in message
news:%23zGfnRifFHA.3940@TK2MSFTNGP14.phx.gbl...
> Ah-, I readily confess, this is not within my area of expertise. But in
> all honesty, the whole idea of networking is to make it transparant where
> processes and data resides - such that if you have f.ex. Word on one
> machine and OpenOrrifice on another ( or Acrobat, or whatever) you can ask
> anyone of those apps to print a document that sits anywhere else on the
> network, provided that app understands the file format. The mind boggles,
> to be frank, to imagine a document would have to be written on one
> specific machine with it's own native drivers to print anywhere else. But
> then, I'm learning every single day.
>
> If, on the other hand, you were refering to a situation where you ask your
> 64bit app to print to a networked printer, I do see your point - but that
> would be underutilizing your network, don't you think? Or, a network with
> a straight-jacket, perhaps?
>
> Tony. . .
>
>
> "Rick" <rick@home.net> wrote in message
> news:eF0rJAdfFHA.3944@TK2MSFTNGP10.phx.gbl...
>> Even if you are networking, you need OS specific drivers on the computer
>> you are on.
>>
>> Please explain in detail how you think your approach would work without
>> an x64 print driver.
>>
>>
>> Tony Sperling wrote:
>>> . . .or you could network a second machine, wouldn't have to be anything
>>> fancy. A 486 and Win95 (shudder) would probably suffice, and it lets you
>>> print as you write. But 'dual-booting' is a good one too.
>>>
>>> Tony. . .
>
>