Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    WINPOINT    |    Support for the WinPoint software    |    1,004 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 742 of 1,004    |
|    Martin Foster to Tim Schattkowsky    |
|    My WinPoint install is broken    |
|    27 May 22 14:10:55    |
      MSGID: 2:280/464.27 7ba53006       CHRS: UTF-8 4       TZUTC: 0100       REPLY: 2:240/1120.29 7b31fc04       Hello Tim!              *** Thursday 26.05.22 at 19:35:56, Tim Schattkowsky wrote to Martin Foster:               MF>> - Tried to click on the second one but the mouse pointer wouldn't        MF>> move(locked up)        MF>> - Within a few seconds, my PC rebooted itself               TS> Okay, that sounds like a hardware/driver issue. Probably some data got        TS> damaged at that point.              Yep, I agree because I do tend to get occasional/mysterious reboots these days.               MF>> - Fired up WinPoint and clicked on the "Reports" folder in the message        MF>> tree and I got an "Access Violation" popup - see        MF>> https://stargate.org.uk/winpoint/screenshots/access_violation.jpg               MF>> - Clicked the "Ok" button to dismiss the popup and noticed that the        MF>> "Reports" message list was completely empty               MF>> Every time I click the "Reports" folder, I get the "Access Violation"        MF>> popup and an empty message list but having looked in the messagebase        MF>> directory, the "Reports" message base files are actually there.               MF>> How do I recover the situation?               TS> Make a backup of the files related to the report area. Use that old        TS> message base doctor (probably still does the job) to repair the files. If        TS> that does not work, just delete the files (and loose all those reports).              It worked and thank you very much indeed for your expert help :-)))              For the benefit of others, it was just a simple matter of executing       "wpdoctor.exe", which is in the same directory as the WinPoint executable, and       then selecting the "Reports" area from the list of areas in the dialogue and       then clicking the button to set it going. All very quick, easy and painless.       Here's the output from the repair utility .....              ---------- 8< ----------       13:22:05 Area: REPORT       13:22:05 * ERR! Die Datei C:\Users\ms_ac\AppData\Roaming\WinPoin       \MsgBase\REPORT.PackedIndex ist beschädigt       13:22:32 * Die Area wurde repariert       13:22:32 * Die Area hat 588 unindizierte Messages       13:22:32 * Die Area hatte 1 Fehler              13:22:32 * DONE Fertig       13:22:32 =============================================================       13:22:32 Es sind 1 Fehler aufgetreten       13:22:32 Gültige Nachrichten: 588       13:22:32 Ungültige Nachrichten: 0       ---------- 8< ----------              Another nice point is that the repair utility made a backup of the existing       corrupt index file and gave it an extension of ".Backup" .....              ---------- 8< ----------       26/05/2022 13:41 480,544 REPORT.PackedBody       27/05/2022 13:22 32,581 REPORT.PackedIndex       26/05/2022 13:41 26,321 REPORT.PackedIndex.Backup       ---------- 8< ----------              Nice! :)              Regards,       Martin              --- WinPoint 407.0        * Origin: WinPoint Test Rig - UK - (2:280/464.27)       SEEN-BY: 15/0 106/201 124/5016 129/331 153/757 7715 203/0 221/0 229/110       SEEN-BY: 229/111 112 113 317 426 428 470 664 700 266/512 280/464 5003       SEEN-BY: 280/5555 282/1038 292/854 8125 301/1 310/31 317/3 320/219       SEEN-BY: 341/234 396/45 460/58 633/280 712/848 770/1 2452/250       PATH: 280/464 712/848 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca