Index > Scribe > 1.84 Bug
Author/Date 1.84 Bug
13/11/2003 12:25pm
Machine Specs:
1 Ghz Poweredge server
512 ram
30gig 3 drive raid 5
Win2k sp4 with all recent updates

In the 1.84 "Stable" Version:
I'm kind of new to scribe, and I've been using the email portion for a while without any problems.

But I wanted to try out the calendar part, so I went to the calendar, to todays date (11/13/03), and then I double clicked in the box for tomorrows date (the 14th) in "month" view, to make a test reminder.

This opened the calendar event window for that day. I gave it the subject name "Test".
In the "Start:" box it says "11/14/2003 9:01:30a"

If i click the "End:" box's left (day) dropdown box, and pick any date, say the same day, it shows up as Day/Month/Year (14/11/2003)

If i try clicking on the Day dropdown box in the "Start:" Field, the program crashes and gives me this error:

Call stack:
7800FA97: C:\WINNT\system32\msvcrt.dll Offset: 0xE61 (localeconv)
00419B38: C:\Documents and Settings\Administrator\Desktop\scribe184\Scribe.exe Offset: 0xF486 (ScribeWnd::Preview)
100112E4: C:\Documents and Settings\Administrator\Desktop\scribe184\Lgi.dll Offset: 0x1E (GView::_Paint)
77E3A2D0: C:\WINNT\system32\USER32.dll Offset: 0x177 (SetSystemTimer)
77FA15EF: C:\WINNT\system32\ntdll.dll Offset: 0x849 (LdrFlushAlternateResourceModules)
77E15B51: C:\WINNT\system32\USER32.dll Offset: 0xC (GetCursor)
0040A9D7: C:\Documents and Settings\Administrator\Desktop\scribe184\Scribe.exe Offset: 0x325 (ScribeWnd::Preview)
7C5987E7: C:\WINNT\system32\KERNEL32.dll Offset: 0x3E45 (FindFirstChangeNotificationA)

Unhandled Exception
Code: c0000005

In the options, the date is set specifically to the Month/Day/Year 12h format. It was set to default, but the crash happened with that setting too.

How stable is the unstable release?
Should I use that instead?
13/11/2003 5:20pm
The test release is pretty good, probably better than the stable release. The core is more stable, but a few of the edges are still a bit rusty.

I think you'll find test44 doesn't have these bugs. I tried reproducing them and couldn't.

If you do find any problems in the current build please report them here, or via email and I'll look into them.