Humph.
acad.dvb. The other startup files didn't affect the problem. The acad.dvb
file is password protected, so, I hoped that opening the project would allow
me to debug it. Curious. Opening the project made the problem go away. It
must have initialized something that simply loading the project did not. It
turned out that I had a class module using application level events. It
really wasn't doing anything, just initializing (I was using it to teach
myself about application level event programs). At any rate. When I
commented out the initialization of the class module, the problem went away.
Go figure.
Mike
"Mike Weaver" wrote in message
news:D7A87B95CB46F93B204F66B4882BE52E@in.WebX.maYIadrTaRb...
> Well, I am narrowing things down a bit. I am running in a highly
customized
> environement and eliminated the problem by eliminating acad.lsp
acaddoc.lsp
> and acad.dvb. Now time for a bit more detective work to isolate the
> problem.
>
> Progress to be posted.
> Mike
>
> "Mike Weaver" wrote in message
> news:557A1A4CD881162769FF3E49F0DA8838@in.WebX.maYIadrTaRb...
> > This is one I can't find in the knowledge base:
> > unhandled access violation reading 0x000c exception at 6504e399h
> > This occurs on the following two configurations on unrelated drawings
when
> > exiting Acad (the drawing does get saved) and when opening a second
> drawing
> > in a session.
> > ##############################################
> > 1st ----
> > Win98 SE
> > A2Ki network deployment (pulls the exe off the server)
> > NT4 server w/ service pack 6
> >
> > 2nd ----
> > Win2K Pro Service pack 2
> > A2Ki stand alone
> > Same LAN
> > Any ideas what could be causing this error?
> >
> > Thanks in advance,
> > Mike Weaver
> >
> >
> >
>
>