Jump to content
SSForum.net is back!

Recommended Posts

Posted

Hi,

 

i used SSME before and it always worked fine, until this afternoon. Now i always get an error report when im trying to start ssme.

 

I think one of the 2 things happened:

 

- When i closed ssme, my whole pc crashed, just froze up, i couldn't do anything so i pressed the reset button :/

 

- I tried opening a corrupt lvl file ( i downloaded it from ftp and and it was still incomplete >.<")

 

So i thought ssme had a corrupt setting or so, so i deleted all ssme entrys (that i could find) in the registry. I also redownloaded ssme v0.81 but i still get the error.

 

Does anyone know how to fix it, so i can work with ssme again ?

 

Thanks

Posted

here is the data report:

 

Error Signature

-----------------

AppName: ssme.exe

AppVer: 0.0.8.1

ModName: ssme.exe

ModVer: 0.0.8.1

Offset: 000346d2

 

Technical information

------------------------

Exception Information

Code: 0xc0000005 Flags: 0x00000000

Record: 0x0000000000000000 Address: 0x00000000004346d2

 

System Information

Windows NT 5.1 Build: 2600

CPU Vendor Code: 756E6547 - 49656E69 - 6C65746E

CPU Version: 00000F27 CPU Feature Code: BFEBF9FF

CPU AMD Feature Code: 0109E824

 

Module 1

SSME.exe

Image Base: 0x00400000 Image Size: 0x00000000

Checksum: 0x00000000 Time Stamp: 0x34873722

Version Information

Exception Information

Code: 0xc0000005 Flags: 0x00000000

Record: 0x0000000000000000 Address: 0x00000000004346d2

 

Version Information

Signature: feef04bd

StrucVer: 00010000

FileVer: (0.0:8.1)

ProdVer: (0.0:8.1)

FlagMask: 0000003f

Flags: 00000000

OS: 00000004

FileType: 00000001

SubType: 00000000

FileDate: 00000000:00000000

 

Module 2

ntdll.dll

Image Base: 0x7c900000 Image Size: 0x00000000

Checksum: 0x000af2f7 Time Stamp: 0x411096b4

Version Information

Signature: feef04bd

StrucVer: 00010000

FileVer: (5.1:2600.2180)

ProdVer: (5.1:2600.2180)

FlagMask: 0000003f

Flags: 00000000

OS: 00040004

FileType: 00000002

SubType: 00000000

FileDate: 00000000:00000000

 

Module 3

kernel32.dll

Image Base: 0x7c800000 Image Size: 0x00000000

Checksum: 0x000ff848 Time Stamp: 0x411096b4

Version Information

Signature: feef04bd

StrucVer: 00010000

FileVer: (5.1:2600.2180)

ProdVer: (5.1:2600.2180)

FlagMask: 0000003f

Flags: 00000000

OS: 00040004

FileType: 00000002

SubType: 00000000

FileDate: 00000000:00000000

 

Module 4

USER32.dll

Image Base: 0x77d40000 Image Size: 0x00000000

Checksum: 0x0009505c Time Stamp: 0x42260159

Version Information

Signature: feef04bd

StrucVer: 00010000

FileVer: (5.1:2600.2622)

ProdVer: (5.1:2600.2622)

FlagMask: 0000003f

Flags: 00000000

OS: 00040004

FileType: 00000002

SubType: 00000000

FileDate: 00000000:00000000

 

Module 5

GDI32.dll

Image Base: 0x77f10000 Image Size: 0x00000000

Checksum: 0x0004b007 Time Stamp: 0x41109697

Version Information

Signature: feef04bd

StrucVer: 00010000

FileVer: (5.1:2600.2180)

ProdVer: (5.1:2600.2180)

FlagMask: 0000003f

Flags: 00000000

OS: 00040004

FileType: 00000002

SubType: 00000000

FileDate: 00000000:00000000

 

and this goes on till module 31, then the stack of the treads, memory range and entire context

comes up in hexadecimal

like this

 

Thread 1

Thread ID: 0x00000c14

Context:

EDI: 0x7ffd4000 ESI: 0x00000000 EAX: 0x012d0000

EBX: 0x0012d34c ECX: 0x00001000 EDX: 0x7c90eb94

EIP: 0x7c90eb94 EBP: 0x0012d3c0 SegCs: 0x0000001b

EFlags: 0x00000246 ESP: 0x0012d324 SegSs: 0x00000023

Stack:

0x0012d320: 0012d474 7c90e9ab 7c8094f2 00000002 t......|...|....

0x0012d330: 0012d34c 00000001 00000000 0012d380 L...............

0x0012d340: 7c802530 012b0000 7c910331 000000dc 0%.|..+.1..|....

0x0012d350: 000000f0 00690074 0067006e 005c0073 ....t.i.n.g.s.\.

0x0012d360: 00770044 00670069 00000000 00000014 D.w.i.g.........

0x0012d370: 00000001 00000000 00000000 00000010 ................

0x0012d380: 4d2fa200 ffffffff 7c910331 7ffd4000 ../M....1..|.@..

 

Do you need more info ?

 

I start ssme.exe, few seconds later i get this error report

Posted

but ssme _worked_ until it crashed my pc on close once, then afterwards it doesn't want to start anymore, i think there's some bad registry entry for ssme or so.

 

So if you know which registry keys ssme writes, or config files, i can delete it, and maybe it will work again

 

Now that ssme doesn't work, i'm making my own map editor in vb :D . It will be more like a ssme clone, but with more features such as fill and such

Posted

nice, people would need that :D

 

Try deleting the old SSME and installing it to a different directory. I believe this error isn't caused by the registry, more by different VB dll's and archives. I don't know how to fix that though.

Check out your zone population statistics at stats.sshq.net!

 

 

Maverick

Subspace Statistics Administrator

Retired SSCU Trench Wars Super Moderator

TWCore Coordinator Administrator

Posted

SSME does not use any registry keys (except the file extension ones).

It uses the following DLLs (try to update, I guess): comctl32.dll, IMM32.DLL, LPK.DLL, USP10.dll, MSCTF.dll, imm32.dll, Msimtf.dll

 

A thought: maybe ssme.ini in c:\windows is corrupted?

 

By the way, !@#$%^&* already is a well-working map editor, why waste time on another one?

Posted

i never had any ssme.ini o_O"

 

And im making my own, because i love programming and learning how to make stuff blum.gif (to see if i can do it, ahhh the satisfaction is rewarding blum.gif )

 

Edit: it can load maps now, but not yet saving because i dont know how to save 256bitmap pictures in vb to a byte array, and some of the basic features, pencil, magnifier (from 1:4 to 2:1) and dropper.

 

Edit2: here is the first build of my pre-alpha version of DCME (Drake Continuum Map Editor, ... not very original eh?!) It doesnt support saving, or importing tilesets or special tiles like warpholes or rocks, but it's a start blum.gif . I also need to polish the gui a bit (different mouse cursors, toolbars ,...)

 

Edit3: possible bugs == very likely, although it only reads from an lvl file, back it up just in case :/

DCME.zip

Guest
This topic is now closed to further replies.
×
×
  • Create New...