You speak of an OE inbox folder on the Comcast server. That is a different file from the one that allows me to view my messages via the Comcast web site, right? The Comcast web site is still another way I can receive my mail and I will use that on the "bad" pc until I get this all sported out.
Maybe a quick, condensed explanation of how OE works is in order.
When you open OE, you have folders that, when you click on them, display your messages in the main window. This is the OE interface. The visual representation of data.
The data that makes up your messages is contained in DBX files, one dbx for each folder that is seen in the interface. The DBX files are stored in the Message Store folder. (This is where the pop3uidl.dbx was located).
When you move or delete messages in the folders in the interface, they remain in the DBX file. The program writes data to the DBX file to "tag" them for removal during the OE compact process.
So in the case of the Inbox (or any folder), you can empty the folder in the interface so it appears there are no messages in it, but they are still contained in the data in the DBX file, just ignored and not displayed in the interface because they are "tagged".
If the Inbox.dbx has been corrupted or damaged, it needs to be deleted and replaced with a new one that has no data in it. Remember, just because the folder in the OE interface appears empty, all the data is still in the Inbox.dbx in the Message Store folder.
That's all on your end.
The Inbox at the server is where the mail sits before downloading to your computer and OE.
As you have 2 other computers that seem to be OK, the message that was stuck in OE on your end is not likely to be damaged at the server Inbox. Otherwise things would be jamming up at the server Inbox and mail would not be downloading to any of your computers. It can probably be left alone.
However, due to differences in the 3 computers and installations of OE you have, there may be slight damage to that E-mail that will cause a problem with the 98SE machine, but not the other 2. That's why I thought it should be removed.
If you get rid of it at the server, it definitely won't cause a problem.