@ symbol / relative coordinates not working

[rberliner]

just upgraded CPU & software.
ACA 2010, Windows7.
When I try to use relative coordinates ("@5,3") typing the @ doesn't set up the relative coordinates, it alters the OSMODE. I don't get why it is doing this at all.

example: I type "rec"<CR>, pick a point, type @3,4 and this is what is in the text window:
---------------------------------------------
Command: rec RECTANG
Specify first corner point or [Chamfer/Elevation/Fillet/Thickness/Width]:
Specify other corner point or [Area/Dimensions/Rotation]:
>>Enter new value for OSMODE <4133>:
Resuming RECTANG command.

Specify other corner point or [Area/Dimensions/Rotation]: @
2D point or option keyword required.

Specify other corner point or [Area/Dimensions/Rotation]:
Command: 3,4

[rberliner]

Nobody's had this problem? Anyone?

[douglass]

I have never seen this problem before, but I did play around with it for a bit and did notice something that *might* help.

After I placed the first point of the rectangle, I held down the shift key for a few seconds before hitting @, and I did notice the OSMODE variable show up just like it did in the command line you pasted. I figured since shift+rightclick brought up the osnap menu that holding down shift mid-command had something to do with the osnaps.

So, for lack of better advice, try to be lighning-fast with your shift+2 to get the @, because if you hold shift too long it interrupts your input, or at least it seems like it.

And if this doesn't work, try setting TEMPOVERRIDES to 0 (default is 1), I believe this turns off the shift-override functions...or something like that.

[rberliner]

I think that's it. One file was doing it sporadically and being quick seems to work, or being reaaallly slow also (i.e. holding shift down long after). Thank you.