Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD General Discussion
Socko
Newbie


Joined: 03 May 2002
Posts: 9
Location: USA

PostPosted: Sat Nov 08, 2008 3:46 am   

AV on installation.
 
date/time : 2008-11-07, 21:05:09, 15ms
computer name : SOCKO
user name : SockoBob <admin>
operating system : Windows XP Service Pack 3 build 2600
system language : English
system up time : 44 minutes 38 seconds
program up time : 1 minute 21 seconds
processor : AMD Athlon(tm) XP 3000+
physical memory : 1573/2047 MB (free/total)
free disk space : (C:) 86.65 GB
display mode : 1024x768, 32 bit
process id : $398
allocated memory : 27.12 MB
executable : CMUDPro.exe
exec. date/time : 2008-10-31 12:10
version : 2.37.0.0
compiled with : BCB 2006/07
madExcept version : 3.0h
callstack crc : $0a536775, $269d4843, $269d4843
exception number : 6
exception class : EAccessViolation
exception message : Access violation at address 0072AAEC in module 'CMUDPro.exe'. Read of address 00000010.

Main ($7b4):
0072aaec +000 CMUDPro.exe Lister 502 +0 pList.Count
00d27443 +017 CMUDPro.exe PARENT 5878 +4 TParentForm.FormClose
004a4e57 +017 CMUDPro.exe Forms 3201 +1 TCustomForm.DoClose
00abe7d9 +005 CMUDPro.exe MultiForm 219 +1 TMultForm.DoClose
00d2721e +006 CMUDPro.exe PARENT 5839 +1 TParentForm.DoClose
004a9901 +055 CMUDPro.exe Forms 5604 +12 TCustomForm.Close
004a88f8 +000 CMUDPro.exe Forms 5083 +0 TCustomForm.WMClose
004bf29b +2bb CMUDPro.exe Controls 5146 +83 TControl.WndProc
004c329f +4fb CMUDPro.exe Controls 7304 +111 TWinControl.WndProc
004a57ff +553 CMUDPro.exe Forms 3512 +136 TCustomForm.WndProc
004c29c8 +02c CMUDPro.exe Controls 7073 +3 TWinControl.MainWndProc
0047c4f0 +014 CMUDPro.exe Classes 11583 +8 StdWndProc
7e42a993 +016 USER32.dll CallWindowProcA
006d7e93 +0a7 CMUDPro.exe aqDockingUtils 1728 +7 CallDefWndProc
006d7f81 +0dd CMUDPro.exe aqDockingUtils 1776 +41 TaqWindowEventFilter.WndProc
0047c4f0 +014 CMUDPro.exe Classes 11583 +8 StdWndProc
7c90e450 +010 ntdll.dll KiUserCallbackDispatcher
7e42c1d0 +052 USER32.dll DefWindowProcA
7e42a993 +016 USER32.dll CallWindowProcA
004c339b +0d7 CMUDPro.exe Controls 7334 +23 TWinControl.DefaultHandler
004a7936 +05a CMUDPro.exe Forms 4576 +7 TCustomForm.DefaultHandler
004c4ec9 +0a1 CMUDPro.exe Controls 8254 +16 TWinControl.WMSysCommand
004a89c9 +055 CMUDPro.exe Forms 5114 +7 TCustomForm.WMSysCommand
0072bda8 +034 CMUDPro.exe zsForm 282 +3 TzForm.WMSysCommand
00abeee4 +038 CMUDPro.exe MultiForm 409 +3 TMultForm.WMSysCommand
004bf29b +2bb CMUDPro.exe Controls 5146 +83 TControl.WndProc
004c329f +4fb CMUDPro.exe Controls 7304 +111 TWinControl.WndProc
004a57ff +553 CMUDPro.exe Forms 3512 +136 TCustomForm.WndProc
004c29c8 +02c CMUDPro.exe Controls 7073 +3 TWinControl.MainWndProc
0047c4f0 +014 CMUDPro.exe Classes 11583 +8 StdWndProc
7e42a993 +016 USER32.dll CallWindowProcA
006d7e93 +0a7 CMUDPro.exe aqDockingUtils 1728 +7 CallDefWndProc
006d7f81 +0dd CMUDPro.exe aqDockingUtils 1776 +41 TaqWindowEventFilter.WndProc
0047c4f0 +014 CMUDPro.exe Classes 11583 +8 StdWndProc
7c90e450 +010 ntdll.dll KiUserCallbackDispatcher
7e42c1d0 +052 USER32.dll DefWindowProcA
7e42a993 +016 USER32.dll CallWindowProcA
004c339b +0d7 CMUDPro.exe Controls 7334 +23 TWinControl.DefaultHandler
004a7936 +05a CMUDPro.exe Forms 4576 +7 TCustomForm.DefaultHandler
004bf8e5 +015 CMUDPro.exe Controls 5267 +2 TControl.WMNCLButtonDown
004a85b4 +084 CMUDPro.exe Forms 4965 +11 TCustomForm.WMNCLButtonDown
004bf29b +2bb CMUDPro.exe Controls 5146 +83 TControl.WndProc
004c329f +4fb CMUDPro.exe Controls 7304 +111 TWinControl.WndProc
004a57ff +553 CMUDPro.exe Forms 3512 +136 TCustomForm.WndProc
004c29c8 +02c CMUDPro.exe Controls 7073 +3 TWinControl.MainWndProc
0047c4f0 +014 CMUDPro.exe Classes 11583 +8 StdWndProc
7e42a993 +016 USER32.dll CallWindowProcA
006d7e93 +0a7 CMUDPro.exe aqDockingUtils 1728 +7 CallDefWndProc
006d7f81 +0dd CMUDPro.exe aqDockingUtils 1776 +41 TaqWindowEventFilter.WndProc
0047c4f0 +014 CMUDPro.exe Classes 11583 +8 StdWndProc
7e4196c2 +00a USER32.dll DispatchMessageA
004ad974 +0fc CMUDPro.exe Forms 8105 +23 TApplication.ProcessMessage
004ad9ae +00a CMUDPro.exe Forms 8124 +1 TApplication.HandleMessage
004adca3 +0b3 CMUDPro.exe Forms 8223 +20 TApplication.Run
00eb1a1c +088 CMUDPro.exe cMUDPro 352 +20 initialization
7c912c01 +069 ntdll.dll RtlUnicodeStringToAnsiString
7c812c24 +0b6 kernel32.dll GetVersionExA

error details:
Install
Reply with quote
Fang Xianfu
GURU


Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom

PostPosted: Sat Nov 08, 2008 12:00 pm   
 
Please post bug reports in separate threads. Also, I removed some personal information from your report.
_________________
Rorso's syntax colouriser.

- Happy bunny is happy! (1/25)
Reply with quote
Socko
Newbie


Joined: 03 May 2002
Posts: 9
Location: USA

PostPosted: Sat Nov 08, 2008 1:58 pm   Post bug reports in seperate threads
 
Not sure what you mean? You want the problem I'm having on 1 thread and the bug report generated by the problem on another thread? If your thinking there is more than 1 bug report in this post there isn't. Or are you saying to post them in a different forum?
Reply with quote
Tarken Aurelius
Apprentice


Joined: 23 Oct 2008
Posts: 120
Location: Cincinnati, Ohio

PostPosted: Sat Nov 08, 2008 2:25 pm   
 
Bugs are supposed to go to the beta forum, but please read the stickys there before doing so.
_________________
Tarken Aurelius, quality triggers since 2004! Trigger consulting since 2008! Content Developer at BatMUD (www.bat.org)
Reply with quote
Fang Xianfu
GURU


Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom

PostPosted: Sat Nov 08, 2008 2:34 pm   
 
No, that's not what I meant, and bug reports are fine in either forum. Originally this post was a reply to a separate thread, part of the knowledge base, and I split it off. It was a reminder that, in future, instead of posting new reports in reply to another thread or KB article, you should post them in a separate thread.
_________________
Rorso's syntax colouriser.

- Happy bunny is happy! (1/25)
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Mon Nov 10, 2008 5:39 pm   
 
In any case, to get to the crash dump, I'm confused by the title of this post. How could this crash have happened during Installation? Do you really mean that it happened when you tried to run CMUD? I need to know exactly what you were doing when this error was displayed. I've never seen this one before.
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD General Discussion All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

© 2009 Zugg Software. Hosted by Wolfpaw.net