SCOUG Logo


Next Meeting: TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!








SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999


The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2021, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

December 2000


 Dear Mr. Know-It-All 

Mr. Know-It-All has the answers to even the really tough questions.


Q.  Dear Mr. Know-It-All,

My information folders do not display the lines correctly. How do I fix this?

A. Information folders are folders that open in tree view and display lines and plus/minus buttons to indicate the folder hierarchy. Sometimes, when these folders are created a necessary WPS setting that can't be controlled from the settings notebook does not get set. To correct this run the following REXX script:

sz = 'ObjectId' if SysSetObjectData(sz,'SHOWALLINTREEVIEW=YES') then say 'Turned on ALLINTREEVIEW for' sz else say 'Can not turn on ALLINTREEVIEW for' sz

Replace "ObjectId" with the Object ID of the folder to be changed. Don't forget to enclose the Object ID in '<' and '>' characters.

If the folder does not have an Object ID, use the full path name of the folder.


Q.  Dear Mr. Know-It-All,

I tried to install FP14 and OS/2 claimed it could not operate my hard drive. I had to restore from a backup to recover. What happened?

A. You probably have (or had) a hidden FAT32 C: partition on your drive. A defect was introduced in FDISK somewhere around FP10. The result of this defect is that just running FDISK updates the Master Boot Record (MBR) and changes a flag bit on the FAT32 partition. This defect was benign until FP14 where changes in OS2DASD.DMD caused the FAT32 partition to be assigned a drive letter and the drive letter of your Warp 4 boot partition would shift by one letter. The result is the dreaded "Cannot operate" message.

The only way to recover, as you found, is to restore the MBR to its original state. This could have been done by using a pre-FP10 version of FDISK and the /NEWMBR option.

If you want to update to FP14, be sure to revert FDISK to a pre-FP10 version to avoid the MBR rewrite.


Curious or in doubt, you can ask Mr. Know-It-All
OS/2 is his specialty and sharing solutions is his passion
Mr. Know-It-All lives in Southern California.