This group has been closed as of June 2, 2004. The archives are still
present for reference, but posting is no longer possible.

All members have been moved to a new mailing list with the same name,
just with the "netlabs.org" domain. I'm not posting it here for
obvious  reasons. Hope that list will remain fairly spam-free.

I first want to get some opinions, in order to find out, if I have
some isolated problems only on my system or if it is a more general
issue with XWP 1.0.1/2, before I possibly put it to XTracker.

Mostly/quite frequently when I (try to) open a folder in split view, I
either get a whole bunch of immidiate XWP warning beeps or at the
latest, when I additionally open another folder (standard, icon view).

The according entries in XWPlog then are like this, until I finally
somehow manage to kill/restart the WPS PMShell session:
-------------------
     Tree node count mismatch. G_lDirtyListItemsCount is 3,
treeBuildArray found 1.
2004-05-30 15:55:40:50 T001 fnwpSubclWPFolderWindow
(K:\projects\cvs\xworkplace-1-0\src\filesys\fdrsubclass.c, line 2492):
     Folder SUBCLFOLDERVIEW not found.
2004-05-30 15:55:50:03 T001 fnwpSubclWPFolderWindow
(K:\projects\cvs\xworkplace-1-0\src\filesys\fdrsubclass.c, line 2492):
     Folder SUBCLFOLDERVIEW not found.
[...some 655 more lines like this ..]
-------------------

So is this something (well) known and maybe already fixed?
Cleaning the Inis with XFix, CleanIni and CheckIni doesn't change
anything.


Oohh yeah,  I almost forgot, just another thing ;-)

Apparently over the last couple of weeks/few months I lost for
some/many (sub)folders the ability, to open them up with a MB2 click
on the according line in XWP's "Folder Contents" MB2 folder context
menu. Some, but also not all, often nested as 2. or 3. level
subfolders still work, while basically all of my Desktop default
folders and many others there already lost this feature.

Is there a known way to fix this or do I have to completely remove
XWP, clean the Inis and then do a reinstall with all those then
required tedious reconfigurations?

Thanks already
Wolfi

German resources for version 2.70 of lSwitcher have been uploaded to
Hobbes. The package can be downloaded from
http://hobbes.nmsu.edu/pub/incoming/lsw270de.zip. Eventually the file
will be in http://hobbes.nmsu.edu/pub/os2/util/wps/lsw270de.zip.

lSwitcher is a task switcher for OS/2 and eCS. The program adds new
features to Presentation Manager Alt-Tab switcher, extends the Alt-Tab
switching capability to OS/2 and DOS full-screen sessions, and adds a
convenient and feature-rich "Taskbar" to PM Desktop. The package also
includes an XWorkplace XCenter widget with the similar functionality.

On Sat, 15 May 2004 20:21:23 +0200, Ulrich Möller wrote:

>> Been there already! There is a problem with putting the PMVDDrop
>> object
>> in WP_NOWHERE because the object isn't awakened automatically when
the
>> WPS starts up and the PMVDDrop class doesn't get loaded. This isn't
>> the
>> case when the object is on the Desktop.
>> This prevents drag'n'drop from working with PMView - it uses a
>> function
>> within the DLL although it is not directly related to the WPS
support.
>
>If the only purpose of that object is to load that WPS class, why does
>Peter not simply add the class name to OS2.INI, PM_Workplace:IplLoad ?
>That's what the key is for.

I guess because he doesn't know about it. I will mention it to him.

At 17:17 15/05/04 +0200, Ulrich Möller wrote:
>On Sat, 2004-05-15 at 16:59, Alfredo Fernández Díaz wrote:
>> At 01:12 13/05/04 +0100, you wrote:
>> >I don't know why this thing is on the desktop in the first place. I
...
>> reliable location (in the sense of targetting a folder everyone has).
...
>Everyone has the "Nowhere" folder also. It even gets recreated by the
>WPS on startup if it can't find it. So using "Nowhere" is just as safe
>as the desktop, really.

Go and tell Peter Nielsen ;-)

Regards,
Alfredo.

On Sat, 2004-05-15 at 20:06, Paul Ratcliffe wrote:
> Been there already! There is a problem with putting the PMVDDrop
> object
> in WP_NOWHERE because the object isn't awakened automatically when the
> WPS starts up and the PMVDDrop class doesn't get loaded. This isn't
> the
> case when the object is on the Desktop.
> This prevents drag'n'drop from working with PMView - it uses a
> function
> within the DLL although it is not directly related to the WPS support.

If the only purpose of that object is to load that WPS class, why does
Peter not simply add the class name to OS2.INI, PM_Workplace:IplLoad ?
That's what the key is for.

On Sat, 15 May 2004 16:00:01 BST, Alfredo Fernández  Díaz wrote:

>>I don't know why this thing is on the desktop in the first place. I
>>moved mine to WP_NOWHERE and it can't cause any havoc there. I forget
>>how I did it now... probably deleted and recreated it. It's easy
enough
>
>Probably. I think the main reason to create the object there is to
have a
>reliable location (in the sense of targetting a folder everyone has).
>
>But we can always ask Peter Nielsen, he's alive and kicking!

Been there already! There is a problem with putting the PMVDDrop object
in WP_NOWHERE because the object isn't awakened automatically when the
WPS starts up and the PMVDDrop class doesn't get loaded. This isn't the
case when the object is on the Desktop.
This prevents drag'n'drop from working with PMView - it uses a function
within the DLL although it is not directly related to the WPS support.
In any case, he recommends not using the WPS functions via PMVDDrop
because of the file handle creation problem bloating the .INI files.

But PMVDDrop is currently still needed for PMView to work properly even
when not using the WPS functions - he is currenly looking at removing
that requirement which means you could then delete the object and
remove the class.
If you do require the WPS functions, then it seems the best thing to do
is force the PMVDDrop icon position to somewhere in the middle of the
screen and then make it invisible.

I therefore retract my advice to move PMVDDrop to WP_NOWHERE :-)

On Sat, 2004-05-15 at 16:59, Alfredo Fernández Díaz wrote:
> At 01:12 13/05/04 +0100, you wrote:
> >I don't know why this thing is on the desktop in the first place. I
> >moved mine to WP_NOWHERE and it can't cause any havoc there. I forget
> >how I did it now... probably deleted and recreated it. It's easy
> enough
>
> Probably. I think the main reason to create the object there is to
> have a
> reliable location (in the sense of targetting a folder everyone has).

Everyone has the "Nowhere" folder also. It even gets recreated by the
WPS on startup if it can't find it. So using "Nowhere" is just as safe
as the desktop, really.

At 01:12 13/05/04 +0100, you wrote:
>On Wed, 12 May 2004 19:01:50 -0400 (EDT), Jeffrey Smick wrote:
>
>>I can see others have given their two cents worth. I think you'll find
>the PMView dragdrop object is the problem. Here is
...
>I don't know why this thing is on the desktop in the first place. I
>moved mine to WP_NOWHERE and it can't cause any havoc there. I forget
>how I did it now... probably deleted and recreated it. It's easy enough

Probably. I think the main reason to create the object there is to have a
reliable location (in the sense of targetting a folder everyone has). But we
can
always ask Peter Nielsen, he's alive and kicking!

Regards,
Alfredo.

At 19:01 12/05/04 -0400, you wrote:
>I can see others have given their two cents worth. I think you'll find the
PMView dragdrop object is the problem. Here is
>a REXX script you can use to make the object visible. Once you can see it
you can move to a better place. Of course,
>then you can make it invisible again...
>
>HTH. Wish I could remember the guy who actually figured this out... it
wasn't me... was it Dink? Sorry whoever you are
>if that's wrong - I like to give credit where it's due.

Hi, it was me (perhaps not, but no one posted it in public). Thanks a lot.

Also the 'quick dirty and dangerous solution' quoted by David Graser (Hi
David!) as 'posted in xtracker' was mine. Which reminds me I'd have to add
the PMView ddrop stuff to the xtracker...

thanks for reminding me.

Regards,
Alfredo.

In article <E1BO2ja-0003Eu-00@...>,
"Jeffrey Smick" <jeff.smick@...> wrote:

> I can see others have given their two cents worth. I think you'll find the
> PMView dragdrop object is the problem. Here is
> a REXX script you can use to make the object visible. Once you can see it
> you can move to a better place. Of course, then you can make it invisible
> again...

:) Thanks! That works a treat.

Oddly, on this machine, which has been upgraded through several
versions of XWP, as well as at least a couple of versions of PMView,
the object doesn't sem to exist at all.

On the other desktop and on my laptop, I've now been able to move the
thing out of the way.

paul.


--
paulm@...
Marwick Computer Services - Chipping Norton, Oxfordshire, UK
OS/2, LAN and general Computer Consultants

In article <c7tqn5+9b9e@eGroups.com>, "David Graser" <dwgras@...> wrote:

> Download this
>
> http://www.norrsken-data-teknik.com/eCS/repairTools.zip
>
> Unzip, read the text file, and then if you want, run the "EnableComet.cmd

Thaks David. Don't need it for this machine, but its gone into the
tools collection for next time.

paul

--
paulm@...
Marwick Computer Services - Chipping Norton, Oxfordshire, UK
OS/2, LAN and general Computer Consultants

Ulrich Möller wrote:

>On Mon, 2004-02-02 at 20:54, Mike O'Connor wrote:
>
>>I noticed that on the eCs bugtracker you had my bug of >64MB bitmaps
>>possibly crashing the system without any real warning as "minor" - if
>>the drive in question only has 60MB free at the time, wouldn't you
>>consider that more than minor?
>>
>>I see that WXP 1.0.2 now has a workaround by aborting these large
>>files created from tiny originals soon after the icons are created and then
>>destroyed again - thanks.  Has this been promulgated through the eCS
>>system?
>>
>>
>Mike, I have created http://xtracker.netlabs.org/index.php?bug=569 to
>whose CC list you might want to add yourself. Not that I'll probably
>have much time to work on that in the nearer future, but maybe someone
>else will.
>

Hi Ulrich,
Thanks for getting around to that.  Have now signed-up.

--
Regards,
Mike

Failed the exam for
--------------------
MCSE - Minesweeper Consultant and Solitaire Expert
--------------------
[ISP blocks *.exe, *.cmd, *.bat, *.reg attachments]
[Please use zipped versions of above]

** Reply to message from "David Graser" <dwgras@...> on Thu, 13
May 2004 01:56:14 -0000

Moving PMVDDrop to WP_NOWHERE solves the issue very nicely.  The
following makes it always visible and moves it back and forth between
WP_DESKTOP and WP_NOWHERE.  Feel free to copy.

/* Make PMVDDrop visible */
Parse Upper Arg show .
Call Rxfuncadd 'SysLoadFuncs','RexxUtil','SysLoadFuncs'
Call SysLoadFuncs
rc = SysSetObjectData('<PMVDDrop>','NOTVISIBLE=NO')
If show <> '' Then Do
    Say 'Showing PMVDDrop'
    rc = SysMoveObject('<PMVDDrop>','<WP_DESKTOP>')
    If rc = 0 Then Say 'Error'
    Else Say 'Success'
End
Else Do
    Say 'Hiding PMVDDrop'
    rc = SysMoveObject('<PMVDDrop>','<WP_NOWHERE>')
    If rc = 0 Then Say 'Error'
    Else Say 'Success'
End
Return

> --- In xworkplace-user@yahoogroups.com, "Paul Ratcliffe" <paul@o...>
> wrote:
> > On Wed, 12 May 2004 19:01:50 -0400 (EDT), Jeffrey Smick wrote:
> >
> > >I can see others have given their two cents worth. I think you'll find
> > the PMView dragdrop object is the problem. Here is
> > >a REXX script you can use to make the object visible. Once you can see
> > it you can move to a better place. Of course,
> > >then you can make it invisible again...
> >
> > I don't know why this thing is on the desktop in the first place. I
> > moved mine to WP_NOWHERE and it can't cause any havoc there. I forget
> > how I did it now... probably deleted and recreated it. It's easy enough
> > to do with a bit of REXX.
>
> I used Jeffrey's script to make the object visible, moved it to the
> center of my desktop, went into its properites and selected the "lock
> in place", and then used his other script to make it invisible again.
>
> David

Chuck McKinnis
Covenant Solutions
http://pws.prserv.net/mckinnis/
505-286-3191

'An intellectually honest atheist' is an oxymoron.

On Mon, 2004-02-02 at 20:54, Mike O'Connor wrote:

> I noticed that on the eCs bugtracker you had my bug of >64MB bitmaps
> possibly crashing the system without any real warning as "minor" - if
> the drive in question only has 60MB free at the time, wouldn't you
> consider that more than minor?
>
> I see that WXP 1.0.2 now has a workaround by aborting these large
> files
> created from tiny originals soon after the icons are created and then
> destroyed again - thanks.  Has this been promulgated through the eCS
> system?

Mike, I have created http://xtracker.netlabs.org/index.php?bug=569 to
whose CC list you might want to add yourself. Not that I'll probably
have much time to work on that in the nearer future, but maybe someone
else will.

--- In xworkplace-user@yahoogroups.com, "Paul Ratcliffe" <paul@o...>
wrote:
> On Wed, 12 May 2004 19:01:50 -0400 (EDT), Jeffrey Smick wrote:
>
> >I can see others have given their two cents worth. I think you'll find
> the PMView dragdrop object is the problem. Here is
> >a REXX script you can use to make the object visible. Once you can see
> it you can move to a better place. Of course,
> >then you can make it invisible again...
>
> I don't know why this thing is on the desktop in the first place. I
> moved mine to WP_NOWHERE and it can't cause any havoc there. I forget
> how I did it now... probably deleted and recreated it. It's easy enough
> to do with a bit of REXX.

I used Jeffrey's script to make the object visible, moved it to the
center of my desktop, went into its properites and selected the "lock
in place", and then used his other script to make it invisible again.

David

On Wed, 12 May 2004 22:10:31 -0000, David Graser wrote:

>The fast, dirty and dangerous solution:
>1.- Setup a mainteinance system with rexx support.
>2.- Save the .CLASSINFO and .LONGNAME extended attributes of the
Desktop
>*only* (unless you need anything else).
>3.- Boot to a command prompt and delete the Desktop .EAs
>4.- Boot the mainteinance system and restore the saved Desktop .EAs
>5.- Boot your working system and cross your fingers.

This is overkill really. As you have XWP, it can be easier. Get
EABrowse from Hobbes, install it and open it. Then restart the desktop
but hold down the shift key to bring up the panic dialog. Go to
EABrowse and look at the desktop folder. Delete the .ICONPOS EA and
then exit the panic dialog. Much, much simpler.

>The slow, safe and clean solution:
>-Set your desktop settings to 'always maintain sort order', move
around
>icons, set 'save desktop position' on and off and do X and regular
>shutdowns
>a dozen times. The scroll bar will go away eventually when these
objects
>position are overwritten.

Why do you need a dozen shutdowns? The WPS saves the data the first
time.

The other alternative for moving Icon positions is to get the Extended
Desktop replacement class, which gives you a dialog in the Properties
notebook allowing you to move your desktop icons to pixel precision.
It's ancient IBM EWS but it works fine. I've had it installed for
countless years.
The file is called EXDESK.ZIP (from 1993 !!!) on
ftp://ftp.boulder.ibm.com/pc/pccbbs/os2_ews

On Wed, 12 May 2004 19:01:50 -0400 (EDT), Jeffrey Smick wrote:

>I can see others have given their two cents worth. I think you'll find
the PMView dragdrop object is the problem. Here is
>a REXX script you can use to make the object visible. Once you can see
it you can move to a better place. Of course,
>then you can make it invisible again...

I don't know why this thing is on the desktop in the first place. I
moved mine to WP_NOWHERE and it can't cause any havoc there. I forget
how I did it now... probably deleted and recreated it. It's easy enough
to do with a bit of REXX.

>
> HTH. Wish I could remember the guy who actually figured this out...
it wasn't me... was it Dink? Sorry whoever you are
> if that's wrong - I like to give credit where it's due.

Alfredo Fdez Díaz

He was the one who first reported it the the XWorkplace Bug Tracker.


>
> /* Make PMVDDrop visible */

Checked out our scripts.  They work great.  Thanks.  I have filed them
away for future use if needed.

David

I can see others have given their two cents worth. I think you'll find the
PMView dragdrop object is the problem. Here is
a REXX script you can use to make the object visible. Once you can see it you
can move to a better place. Of course,
then you can make it invisible again...

HTH. Wish I could remember the guy who actually figured this out... it wasn't
me... was it Dink? Sorry whoever you are
if that's wrong - I like to give credit where it's due.

/* Make PMVDDrop visible */
If RxFuncQuery('SysLoadFuncs')>0 then do
   call RxFuncAdd 'SysLoadFuncs','RexxUtil','SysLoadFuncs'
   call SysLoadFuncs
  end
rc=SysSetobjectData('<PMVDDrop>','NOTVISIBLE=NO')
if rc=0 then
   say 'Error'
else say 'Success'
exit

/* Make PMVDDrop invisible again */
If RxFuncQuery('SysLoadFuncs')>0 then do
   call RxFuncAdd 'SysLoadFuncs','RexxUtil','SysLoadFuncs'
   call SysLoadFuncs
  end
rc=SysSetobjectData('<PMVDDrop>','NOTVISIBLE=YES')
if rc=0 then
   say 'Error'
else say 'Success'
exit

On Wed, 12 May 2004 22:23:58 +0000, paulm@... wrote:

>In article <E1BNybB-0007MN-00@...>,
>"Jeffrey Smick" <jeff.smick@...> wrote:
>
>> Do you also have PMView installed? Its invisible dragdrop object on the
>> desktop sometimes causes this problem.
>
>Yes, I do. How do I fix the dragdrop object?
>
>regards, paul.
>
>--
>paulm@...
>Marwick Computer Services - Chipping Norton, Oxfordshire, UK
>OS/2, LAN and general Computer Consultants
>
>
>
>To Post a message, send it to:   xworkplace-user@eGroups.com
>To Unsubscribe, send a blank message to:
xworkplace-user-unsubscribe@eGroups.com
>Yahoo! Groups Links
>
>
>
>
>


Jeffrey R Smick
http://home.earthlink.net/~jeff.smick

"I believe OS/2 is destined to be the most important operating system,
and possibly program, of all time"
-Bill Gates

--- In xworkplace-user@yahoogroups.com, paulm@w... wrote:
> In article <E1BNybB-0007MN-00@s...>,
> "Jeffrey Smick" <jeff.smick@e...> wrote:
>
> > Do you also have PMView installed? Its invisible dragdrop object
on the
> > desktop sometimes causes this problem.
>
> Yes, I do. How do I fix the dragdrop object?
>
> regards, paul.
>
> --
> paulm@w...
> Marwick Computer Services - Chipping Norton, Oxfordshire, UK
> OS/2, LAN and general Computer Consultants

Taken from the XTracker bug report:

The cause: object positions in the Desktop stored as out of range values.
BTW they're not saved in the .INI files as C. Stirling said and others may
think but in the Desktop .EAs.

The fast, dirty and dangerous solution:
1.- Setup a mainteinance system with rexx support.
2.- Save the .CLASSINFO and .LONGNAME extended attributes of the Desktop
*only* (unless you need anything else).
3.- Boot to a command prompt and delete the Desktop .EAs
4.- Boot the mainteinance system and restore the saved Desktop .EAs
5.- Boot your working system and cross your fingers.

The slow, safe and clean solution:
-Set your desktop settings to 'always maintain sort order', move around
icons, set 'save desktop position' on and off and do X and regular
shutdowns
a dozen times. The scroll bar will go away eventually when these objects
position are overwritten.

David

In article <c7tq96+e22g@eGroups.com>, "David Graser" <dwgras@...> wrote:

> Are you running two Xcenters or XCenter and WarpCenter?  This can
> possible cause your problem.  If so, you might try removing one and
> seeing if this solves the problem.

No, just XCenter. Problem only seems to appear when I start using
XCenter, but I really don't like WarpCenter very much... And I don't
think I could live without XWP itself...

I have occasionaly run a launchpad (modified using BubblePad 1.05) as
well as XCenter, but in this instance, I hadn't installed it yet.

regards, paul.

--
paulm@...
Marwick Computer Services - Chipping Norton, Oxfordshire, UK
OS/2, LAN and general Computer Consultants

In article <20040512203103.6781D1BB4DB@...>,
"Charles Stirling" <charles.dive@...> wrote:

> Anything which is off or very close to top or bottom can cause it.  I get
> it on some boots or desktop refreshes and not on others as I think the
> desktop actually has 2 instances of itself.  On mine one is the problem
> the other not.  I sort of remember that it might also be something to do
> with the desktop ini position entries not being updated (maybe if nothing
> is moved enough).  Try moving everything away from edges and rebooting
> then move back but not "too" close.

Yeah, I've seen it sometimes as well. But this is persistent, which
I've not encountered before.

As for things being near the screen borders, only XCenter appears to be
close. I'll try shifting a few things and see what happens...

regards, paul.


--
paulm@...
Marwick Computer Services - Chipping Norton, Oxfordshire, UK
OS/2, LAN and general Computer Consultants

In article <E1BNybB-0007MN-00@...>,
"Jeffrey Smick" <jeff.smick@...> wrote:

> Do you also have PMView installed? Its invisible dragdrop object on the
> desktop sometimes causes this problem.

Yes, I do. How do I fix the dragdrop object?

regards, paul.

--
paulm@...
Marwick Computer Services - Chipping Norton, Oxfordshire, UK
OS/2, LAN and general Computer Consultants

In article <c7tqn5+9b9e@eGroups.com>, "David Graser" <dwgras@...> wrote:

> Download this
>
> http://www.norrsken-data-teknik.com/eCS/repairTools.zip
>
> Unzip, read the text file, and then if you want, run the "EnableComet.cmd

Ok, thanks. I'll grab it next time I'm online.

regards, paul.

--
paulm@...
Marwick Computer Services - Chipping Norton, Oxfordshire, UK
OS/2, LAN and general Computer Consultants

>> XWP and Xcenter, I now get a vertical scroll bar on the right of the
>> screen when the WPS loads. I've seen this before, but have no idea what
>> is causing it or how to get rid of it...

>Do you also have PMView installed? Its invisible dragdrop object on the
>desktop sometimes causes this problem.

Anything which is off or very close to top or bottom can cause it.  I get it on
some
boots or desktop refreshes and not on others as I think the desktop actually has
2
instances of itself.  On mine one is the problem the other not.  I sort of
remember that
it might also be something to do with the desktop ini position entries not being
updated (maybe if nothing is moved enough).  Try moving everything away from
edges
and rebooting then move back but not "too" close.


Charles

On Wed, 12 May 2004 18:26:46 -0000, David Graser wrote:

>> I've just done another reinstall on my test machine. After installing
>> XWP and Xcenter, I now get a vertical scroll bar on the right of the
>> screen when the WPS loads. I've seen this before, but have no idea what
>> is causing it or how to get rid of it...
>>


Do you also have PMView installed? Its invisible dragdrop object on the desktop
sometimes causes this problem.

Jeffrey R Smick
http://home.earthlink.net/~jeff.smick

That only which we have within, can we see without. If we meet no Gods,
it is because we harbor none. If there is a grandeur in you, you will
find grandeur in porters and sweeps.
-Ralph Waldo Emerson

--- In xworkplace-user@yahoogroups.com, paulm@w... wrote:
> I remeber this being discussed quite a while ago, but can't access any
> of the older messages in this area, so I'm hoping someone can tell me
> how to cure this...
>
> I've just done another reinstall on my test machine. After installing
> XWP and Xcenter, I now get a vertical scroll bar on the right of the
> screen when the WPS loads. I've seen this before, but have no idea what
> is causing it or how to get rid of it...
>
> Also, I've now confirmed that there is some sort of interaction between
> XWP and the comet cursor page of the mouse settings object. Due to
> (unrelated) problems, I reinstalled Warp 4 several times on the test
> machine yesterday. In each instance, whether it was installed with the
> standard (DDFP 3) mouse driver, Amouse or the singlemouse driver, after
> the installation, the comet cursor page was visible. In each instance,
> as soon as XWP was installed, the comet cursor page went missing.
> Backleveling WPCONFIG.DLL will bring it back, but doing so has a lot of
> impact on mouse performance - it crawls while the old DLL is in place.
> It doesn't matter whether it is the standard FP17 WPCONFIG.DLL or the
> updated on that comes with the most recent singlemouse driver - either
> of these interact with XWP and cause the comet cursor page to go
> missing.
>

Download this

http://www.norrsken-data-teknik.com/eCS/repairTools.zip

Unzip, read the text file, and then if you want, run the "EnableComet.cmd

David

--- In xworkplace-user@yahoogroups.com, paulm@w... wrote:
> I remeber this being discussed quite a while ago, but can't access any
> of the older messages in this area, so I'm hoping someone can tell me
> how to cure this...
>
> I've just done another reinstall on my test machine. After installing
> XWP and Xcenter, I now get a vertical scroll bar on the right of the
> screen when the WPS loads. I've seen this before, but have no idea what
> is causing it or how to get rid of it...
>
> Also, I've now confirmed that there is some sort of interaction between
> XWP and the comet cursor page of the mouse settings object. Due to
> (unrelated) problems, I reinstalled Warp 4 several times on the test
> machine yesterday. In each instance, whether it was installed with the
> standard (DDFP 3) mouse driver, Amouse or the singlemouse driver, after
> the installation, the comet cursor page was visible. In each instance,
> as soon as XWP was installed, the comet cursor page went missing.
> Backleveling WPCONFIG.DLL will bring it back, but doing so has a lot of
> impact on mouse performance - it crawls while the old DLL is in place.
> It doesn't matter whether it is the standard FP17 WPCONFIG.DLL or the
> updated on that comes with the most recent singlemouse driver - either
> of these interact with XWP and cause the comet cursor page to go
> missing.
>
> Any ideas gratefully recieved...
>
> paul.
>
> --
> paulm@w...
> Marwick Computer Services - Chipping Norton, Oxfordshire, UK
> OS/2, LAN and general Computer Consultants

Are you running two Xcenters or XCenter and WarpCenter?  This can
possible cause your problem.  If so, you might try removing one and
seeing if this solves the problem.

David

I remeber this being discussed quite a while ago, but can't access any
of the older messages in this area, so I'm hoping someone can tell me
how to cure this...

I've just done another reinstall on my test machine. After installing
XWP and Xcenter, I now get a vertical scroll bar on the right of the
screen when the WPS loads. I've seen this before, but have no idea what
is causing it or how to get rid of it...

Also, I've now confirmed that there is some sort of interaction between
XWP and the comet cursor page of the mouse settings object. Due to
(unrelated) problems, I reinstalled Warp 4 several times on the test
machine yesterday. In each instance, whether it was installed with the
standard (DDFP 3) mouse driver, Amouse or the singlemouse driver, after
the installation, the comet cursor page was visible. In each instance,
as soon as XWP was installed, the comet cursor page went missing.
Backleveling WPCONFIG.DLL will bring it back, but doing so has a lot of
impact on mouse performance - it crawls while the old DLL is in place.
It doesn't matter whether it is the standard FP17 WPCONFIG.DLL or the
updated on that comes with the most recent singlemouse driver - either
of these interact with XWP and cause the comet cursor page to go
missing.

Any ideas gratefully recieved...

paul.

--
paulm@...
Marwick Computer Services - Chipping Norton, Oxfordshire, UK
OS/2, LAN and general Computer Consultants