I finally had the chance to fiddle with Ghost.EXE under Dosemu -- as per
the earlier thread. Unfortunately, it won't even start -- complaining that
"an internal inconsistency" has been detected, and that I should contact 
Symantec for help. (I don't think they'll be very helpful, since what I'm 
doing is way outside the realm of the supported.)

For reference -- I have uploaded screenshots of the crash to my web site:

http://www.e.kth.se/~pvz/dosemu-ghost-crash-01.png
http://www.e.kth.se/~pvz/dosemu-ghost-crash-02.png

I ran this on the latest version of Knoppix, starting with the stable
binary distribution with Freedos. I just cp'ed over GHOST.EXE to the home
directory and tried to run that, so I wouldn't have to dive in to
configuration issues just yet. The configuration was completely standard 
and untouched as provided in the tarball of the binary.

(I tried to get that General Protection fault message copy/pasted, but I 
couldn't figure out how to do that. I tried selecting and middle clicking 
into the terminal, but nothing happened. Sorry for the inconvenience.)

I got similar (but not neccessarilly identical, I haven't checked the
specific numbers and addresses) when trying Dosemu 1.3.1. The version on
the screenshots is the binary of 1.2.2.

I don't know what to start with to debug this, or even if it's practical. 

I was also asked if GHOST.EXE used any form of DPMI -- and I don't know 
how to check that.

I will gladly provide any additional information or files required if
anyone feels they want to try debugging this. But as I said -- this is
completely out of my league -- so I should probably start looking for
alternative solutions to the problem, unless this problem has a simple 
fix. (I doubt it, but I can always hope, can't I? :-)

Anyway, thanks for all your help so far!

-- 
Per von Zweigbergk <[EMAIL PROTECTED]>


-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to