SCOUG Logo


Next Meeting: Sat, 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-2024, 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
USA

SCOUG-HELP Mailing List Archives

Return to [ 21 | March | 2005 ]

<< Previous Message << >> Next Message >>


Date: Mon, 21 Mar 2005 18:04:33 PST8
From: Gary Wong <gary.wong@sbcglobal.net >
Reply-To: scoug-help@scoug.com
To: Steven Levine <steve53@earthlink.net > , scoug-help@scoug.com
Subject: SCOUG-Help: Re: POPUPLOG.OS2

Content Type: text/plain

Steven Levine wrote:

>In <423E234D.7050307@sbcglobal.net>, on 03/20/05
> at 05:28 PM, Gary Wong said:
>
>
>
>
>>I've been getting a SYS3175 and a POPUPLOG.OS2 entry every time I boot
>>up my eCS 1.2 on my P4 3.2GHz.
>>
>>
>
>
>
>>I think it may have started after I powered-off the machine during
>>shutdown, but before I got the "shutdown complete" message (a few months
>>ago).
>>
>>
>
>
>
>>Is this fixable?
>>
>>
>
>
>
>>03-20-2005 17:07:14 SYS3175 PID 0022 TID 0001 Slot 0025
>>C:\OS2\FFST.EXE
>>c0000005
>>1c0224b4
>>P1=00000001 P2=00000000 P3=XXXXXXXX P4=XXXXXXXX
>>EAX=00000000 EBX=00080710 ECX=00000006 EDX=0002fd34
>>ESI=00109659 EDI=00000000
>>DS=0053 DSACC=f0f3 DSLIM=ffffffff
>>ES=0053 ESACC=f0f3 ESLIM=ffffffff
>>FS=150b FSACC=00f3 FSLIM=00000030
>>GS=0000 GSACC=**** GSLIM=********
>>CS:EIP=005b:1c0224b4 CSACC=f0df CSLIM=ffffffff
>>SS:ESP=0053:0002ec2c SSACC=f0f3 SSLIM=ffffffff
>>EBP=0002ec34 FLG=00012206
>>
>>
>
>
>
>>DOSCALL1.DLL 0002:000024b4
>>
>>
>
>I suspect that this means the FFST database is corrupted, but I can not
>tell which file is corrupted from the above. You could try restoring the
>FFST files in \OS2\SYSTEM\RAS from your backup. You could also try
>running FFST Setup. This might fix the corruption or it might also crash.
>
>
>
How do I run FFST setup? I see a FFST.CMD in x:\ecs\install, but not
sure if I need to put CD #1 in the drive, or how to invoke it.

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 21 | March | 2005 ]



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

Copyright 2001 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.