SCOUG Logo


Next Meeting: Sat, Sep 21th, 2019
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 2019, 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

October 2004


 Dear Mr. Know-It-All 

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


Question:

Hi. I need to reinstall Smart Suite and the install fails with:

EPFIE602: An error occurred while attempting to create a directory. Ensure that you have write access to a drive with adequate disk space.

I've checked everything I can think of. I have between 2GB and 4GB of free space on the install volume and on the TMP volume. What else should I check?

Answer:

You have done your homework. These are the typical reasons why the Software Installer fails. Unfortunately, you have been bitten by IBM's tendency to hide information. It would be really easy if the message included a full pathname.

Do you happen to have read-only NTFS volume? If so, this could very well be your problem. When the Software Installer needs to create a work directory, it chooses the volume with the most free space. Unfortunately, the Software Installer neglects to verify that the volume is writable and the attempt to create the directory fails.

Try temporarily hiding the NTFS volume and see if this is sufficient to make the error go away.

If this is not your problem, you need to spend some quality time with the OS/2 Trace Facility to determine the actual volume and directory name.

Question:

I just resized some volumes and I can no longer run chkdsk from my maintenance volume. Chkdsk now fails with:

SYS0546 not enough memory is available to run CHKDSK.

Chkdsk was working just fine before the resize.

Answer:

This may be another case of IBM's tendency to hide information. Check the THREADS statement in CONFIG.SYS. This statement is often omitted or set to a relatively low value on maintenance volumes. If the statment is omitted, the maximum thread count is 64. Try increasing the maximum thread count and see if this is sufficient to make the error go away.

Chkdsk requires approximately 64 threads for every 9GB of disk volume space. You can use this rule of thumb to calculate a setting that will work for your volumes. However on reasonably current hardware, there is very little reason to not set

THREADS = 1024

Mr. KIA has no real desire to try to explain why the chkdsk programmers decided it was a good idea to translate a perfectly obvious SYS0164 error to an internal SYS0008 error and finally report this as a SYS0546 error.

Mr. KIA also has no real desire to try to explain why chkdsk requires so many threads to function. One possible theory is that it was a good way to maximize head motion during chkdsk processing.


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.


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

Copyright 2004 the 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.