nvidia & windows filepro problems-all other software works fine

[Fairlight]

Only Kenneth Brody would say something like:
> Also, note that the Windows version of filePro is a full-fledged Windows
> application.  It happens to be a character-based rather than GUI-based,
> but it is still a Windows application.  But, yes, it runs in a console
> window.  (However, it is not a "DOS shell" running "DOS console mode".
> Especially since he's running under XP, which does not run on top of
> DOS, as 95/98/Me do.)

Poor phrasing on my part, better on yours.  Yes, I realise it's not layered
inside the separate interpreter in the native version.  It's more the
concept of the console window as a window type that concerned me and fired
alarm bells.

> I agree that a quick test of the console window will probably show that
> it also appears on all screen sets.  (And if it only appears on one set,
> I would be very surprised if starting filePro within that window made it
> appear on all sets.)

I never meant to imply that he should start fP from inside that window.  My
statement was just what it was--start a DOS shell, and see if that window
itself (not anything started from inside it) is failing to show up on the
other sets, same as fP apparently is not.  My theory being that it's the
console window type that's not playing nice, just as it apparently wasn't
from that one web site that lets you run your applications remotely (can't
remember the name...check the archives for the last few months).

I'm simply saying, "Start a DOS shell and see if -that window- appears in
multiple sets or not."  If it doesn't, then the combination of that and fP
not doing so would -seem- to point to console windows being problematic,
barring further information.

Sorry for any confusion.

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html