cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

28001C tutorial file.

lhales
Newbie

28001C tutorial file.

Hey folks, can one or two of you check something out for me. Think I have
found a problem in the 28001C.sgm tutorial file and would like some
verification.

WARNING - Before trying this, make sure you have saved any other work you
may have open. Best approach is close all other files before attempting.
If you verify the problem, Epic WILL LOCK UP.

What I have found (with two different computers) is that if I open the
tutorial file (epic-path\tutorials\28001C\28001C.sgm) and try to scroll
through the file with the wheel on my mice (different mouse on each
computer), when I encounter a table the screen will freeze at that point
and Epic will be locked up. The task manager or the' X' are the only ways
to close Epic.

The reason I am asking for additional input is both my mice are Logitech
(one is a wireless notebook, and the other a wired USB optical) and both
are using the same version of Mouseware (9.79.024 according to the drive
details in the device manager).

So any Macro$carf (or other mouse maker) with a wheel checks would be
appreciated. Also any Logitech running the generic Windoze mouse drivers
or an older version of Mouseware (wheel mice only please).

I have submitted this as a problem to Arbortext, what I would be nice it
to be able to say this is a DOCTYPE problem, a mouse wheel problem in that
file or a Logitech mouse problem. Being the old aircraft maintainer, I
always appreciated all the info on a problem I could get in finding a
problem. Okay, there are some really obvious problems, like the F-4 pilot
who landed and reported his compass system not working properly. Not much
help, until we went out to the plane and found a nice round hole in the
wing tip where the compass transmitter should have been (there were bits
of broken plastic and wiring in the vicinity). Seems Charlie got lucky
and hit the plane with some ground fire. The pilot was luckier in that he
didn't get any more holes and crash.

Now I would like to emphasize that so far the 28001 file is the only one
that seems to have this problem. I've tried several other SGML and XML
files with tables and CANNOT replicate the problem any where else. So
when this blew me away last week while I was looking for a FOSI answer
(no, I don't know 28001 by memory) and I lost some work, I was a bit
(shall we say) miffed (being nice).

Remember to heed the WARNING above and repeated here for the third time.

IF YOU TRY THIS AND ARE ABLE TO DUPLICATE THE PROBLEM EPIC WILL LOCK UP
AND YOU WILL LOSE ANY UNSAVED WORK. (and yes I was yelling) 🙂

Many thanks.

Lynn
Tags (2)
9 REPLIES 9

Re: 28001C tutorial file.

Lynn
I just ran through the file on a computer running Windoze 2K and a MS Mouse. Using the mouse wheel, I breezed by all the tables in the tutorial file. No lock-ups.
That is only one computer, but it may be an indicator of what is to come. And then again I could be wrong as I usually am.

John T. Groves
W R Systems, LTD.
2500 Almeda Ave
Suite 214
Norfolk, VA 23513-2403
Ph. 757.858.6000 ext 442

Re: 28001C tutorial file.

I do not have the problem on my PC. I have an HID-compliant (HID=Human
Interface Device) wheel USB wired optical mouse with Microsoft driver
version 5.1.2600.0.

Re: 28001C tutorial file.

Oh yes, the other thing I should have added.

Macro$carf Windoze XP SP2 (shudder) on both machines.

Thanks John.

Lynn

Re: 28001C tutorial file.

Lynn,

Tested on my laptop HP (Alps touchpad + scroll function), no lock-ups.

Best Rgds,

Martti

Re: 28001C tutorial file.

No freeze on my machine... XP Pro SP1 / Wired Compaq Mouse / Epic 5.1

Re: 28001C tutorial file.

I forgot to mention on my previous post that I have Microsoft Windows XP
Professional version 2002 SP1.

Re: 28001C tutorial file.

Worked just fine here; Epic 5.0, WinXP Pro SP2, 1GB RAM, P4 2.6GHz,
Creative notepad USB wheel-rodent (optical).

Lynn Hales wrote:

>
> Hey folks, can one or two of you check something out for me. Think I
> have found a problem in the 28001C.sgm tutorial file and would like
> some verification.
>
> WARNING - Before trying this, make sure you have saved any other work
> you may have open. Best approach is close all other files before
> attempting. If you verify the problem, Epic WILL LOCK UP.
>
> What I have found (with two different computers) is that if I open the
> tutorial file (epic-path\tutorials\28001C\28001C.sgm) and try to
> scroll through the file with the wheel on my mice (different mouse on
> each computer), when I encounter a table the screen will freeze at
> that point and Epic will be locked up. The task manager or the' X'
> are the only ways to close Epic.
>
> The reason I am asking for additional input is both my mice are
> Logitech (one is a wireless notebook, and the other a wired USB
> optical) and both are using the same version of Mouseware (9.79.024
> according to the drive details in the device manager).
>
> So any Macro$carf (or other mouse maker) with a wheel checks would be
> appreciated. Also any Logitech running the generic Windoze mouse
> drivers or an older version of Mouseware (wheel mice only please).
>
> I have submitted this as a problem to Arbortext, what I would be nice
> it to be able to say this is a DOCTYPE problem, a mouse wheel problem
> in that file or a Logitech mouse problem. Being the old aircraft
> maintainer, I always appreciated all the info on a problem I could get
> in finding a problem. Okay, there are some really obvious problems,
> like the F-4 pilot who landed and reported his compass system not
> working properly. Not much help, until we went out to the plane and
> found a nice round hole in the wing tip where the compass transmitter
> should have been (there were bits of broken plastic and wiring in the
> vicinity). Seems Charlie got lucky and hit the plane with some ground
> fire. The pilot was luckier in that he didn't get any more holes and
> crash.
>
> Now I would like to emphasize that so far the 28001 file is the only
> one that seems to have this problem. I've tried several other SGML
> and XML files with tables and CANNOT replicate the problem any where
> else. So when this blew me away last week while I was looking for a
> FOSI answer (no, I don't know 28001 by memory) and I lost some work, I
> was a bit (shall we say) miffed (being nice).
>
> Remember to heed the WARNING above and repeated here for the third
> time.
>
> IF YOU TRY THIS AND ARE ABLE TO DUPLICATE THE PROBLEM EPIC WILL LOCK
> UP AND YOU WILL LOSE ANY UNSAVED WORK. (and yes I was yelling) 🙂
>
> Many thanks.
>
> Lynn

Re: 28001C tutorial file.

Folks,

Thanks for the responses and the checks. It is looking like I have a
problem me. Shoot I'm at a loss (unfortunately for you fine folks not for
words).

I've done the following,

1. Uninstalled and disconnected my Logitech mouse. (had to reboot here)
2. Put a Microsoft wheel mouse in its place.

Results are the file will still lock up.

Next

1. I've uninstalled and reinstalled Epic
2. Run Epic with the generic mouse driver.
Results SSDD (Same S*** Different Day)

So I'm not sure what the problem is. Think I'll write a simple save all
script and put it in the milspec folder in Epic. Then if I forget about
this problem and open the file, at least my work will be safe (saved?).

Again, thank you all.

Lynn

Re: 28001C tutorial file.

Well, Arbortext support just posted a note on my case. They were able to
duplicate it with the Logitech mouse driver. On that file only. DUH.

Actually, as I was looking at how to go about ensuring my files were saved
if I opened the 28001 tutorial, support added some additional info. Most
interesting.

1. The problem is repeatable with a Logitech mouse driver, but not with a
Logitech mouse and generic Macro$carf mouse driver (Ed and support proved
the last half, support and I did the first half)
2. Support tested the problem with beta to version 5.2 and the problem
was not there.
3. The problem is ONLY (so far) happening when the 28001C.sgm file is
opened and you try to use the mouse wheel to scroll through the document.

So for anyone out there using a Logitech mouse with Logitech Mouseware
here is a simple work around. I normally preach AGAINST doing what I am
going to recommend, but I think this may be an exception. I am
recommending a change to a distributed Epic file.

Okay, in the epic-path\tutorails\28001c folder there is a file called
28001C.ACL (the doctype.acl file you can read about in help topics 5716
and 1331). Modify this file and add the following line to the end of the
file

save_some_docs(1);

This command in discussed in help 139, but basically it will save any open
MODIFIED documents (without prompting, the is the "1") that are in an Epic
Edit window (this includes FOSI"s in tagged mode, as I don't use the
panels I didn't check this approach).

As I said, I normally don't support changing and Epic distributed file. As
this is a doctype.acl file, the fix is for that file and the problem seems
to be fixed in the next release (which would overwrite the tutorial folder
anyway), I don't think this would be a problem. If you are not
comfortable changing the distributed file, copy the folder elsewhere and
change the doctype file in your copy. If you never use the 28001C
tutorial, then don't worry.

Lynn
Announcements