| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2143.1 | | TAMARA::laceup.zko.dec.com::tamara::fitzell | It's not a bug it's functionally challenged ! | Tue Apr 22 1997 16:51 | 21 |
|
>> NT 7.0
We haven't done much testing with this version :-))
WordPerfect 7.0 is a 32 bit app which means on NT there is no integration,
what you get is the infamous Teamlinks Launch Voodoo er.. umm.. I mean
Tracking. After launching a file we have a background process that keeps
tabs on the application and the file, anytime the file changes we save it
back into the filecabinet. By changes I mean anything we can detect from
outside the application like size or date. When the app is shut down the
staging file is deleted and the reservation is cancelled. If they only
close the file within the app (which is what it sounds like they are doing)
we have no way of knowing that the application is done with the document so
we can't cancel the reservation. The file will have been saved into the
filecabinet by the background process but the reservation gets left hanging
until the application goes away. Basically what you get on NT with 32 bits
apps is the level of integration we have with NOTEPAD or PAINT.
Mike
|
| 2143.2 | Thanks, | OASS::ANDRES_B | | Thu Apr 24 1997 11:43 | 8 |
| Mike,
Thanks for the answer. As far as NT 7.0 I guess I'm getting a little
ahead of myself. I'm glad you can read between the versions.
Beth
|
| 2143.3 | Even exiting does not remove likc | OASS::ANDRES_B | | Thu Apr 24 1997 12:08 | 10 |
| The user at this site is exiting WP 7.0 and the reservation
icon (lock) is still remaining on the file.
I don't have a copy of WP 7.0 to test this. Has anyone tried
this iwth NT 4.0 and WP 7.0.
Thanks,
Beth
|
| 2143.4 | | TAMARA::laceup.zko.dec.com::tamara::fitzell | It's not a bug it's functionally challenged ! | Thu Apr 24 1997 14:10 | 10 |
| Beth,
Sorry I should have put this in my previous reply that NT4.0 decided to
obsolete some of the windows API functions that we used in the launch
tracking code. Typically it doesn't affect 16 bit apps but we really have
problems with 32 bit apps. Depending on which app you're lauching different
things can happen some benign others not so nice. Considerable work has
gone into V3.0 to fix it but given the size and complexity of the changes
there are no plans to put it in an ECO.
Mike
|
| 2143.5 | One More Question | OASS::ANDRES_B | | Thu Apr 24 1997 15:00 | 7 |
| Mike,
I just need to confirm one thing then. WordPerfect 6.1 is a 16 bit
app correct. I am beginning to get the 16 and 32 confused.
Beth
|
| 2143.6 | | XANADU::laceup.zko.dec.com::tamara::fitzell | | Fri Apr 25 1997 09:36 | 13 |
| Beth,
>>I just need to confirm one thing then. WordPerfect 6.1 is a 16 bit
>> app correct.
Yes it is.
>>I am beginning to get the 16 and 32 confused.
Join the club :-)). On NT a quick way to check is bring the task manager
up and if the exe is slightly indented under a NTVDM.EXE and it doesn't
have it's own PID it's a 16 bit app. If they have enabled the option of
running 16 bit apps in their own address space there may be more than one
NTVDM process and in that case all bets are off as to launch.
Mike
|