PKFSTGROUP at startup

[rjvs]

Don't know what I did to cause the 'Group Manager' dialog
to pop up automatically every time I start LT2007.
-
The startup text window messages read...
-
Customization file loaded successfully. Customization Group: ACADLT
Customization file loaded successfully. Customization Group: CUSTOM
Regenerating model.
Command: COMMANDLINE
Command: PKFSTGROUP
-
what's causing 'Command: PKFSTGROUP'?
-
Help anyone??

[lrlandusky]

As I understand it, PKFSTGROUP is the command line function for "group". Not sure why it would run that command at the startup though. I did a quick search for PKFSTGROUP and it turned up a several discussions.

Something in your workspace checked maybe???

[rjvs]

Thanks but I've searched the Windows Registry and done
text searches on LT's file folders and haven't been able
to find a fix yet... Perhaps someone from Adesk knows
what's going on...?
-
This Knowledge Base Solution didn't work.
http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=9028795&linkID=9240817

[lrlandusky]

Adesk solution seems a bit odd. They don't tell you to dock it and then close it? Does it always appear docked in the same position now?

A workspace is supposed to save exactly what you see on your screen. So if you open and close certain toolbars, pallets, properties, etc. it's supposed to open up the same way you left it (as long as you set your workspace properties to save every time).

[Anonymous]

Are you using a customized CUI?
Would loading the 'original' only fix the problem?
Did you install Sp2?
A reinstall of LT2007, skipping SP2 patch?

--
Dean Saadallah
Add-on products for LT
http://www.pendean.com/lt
--

[rjvs]

Yup, SP2 installed etc...but really focussed on CUI issue
as running LT as Administrator didn't have the problem...
After several hours of fooling around I re-checked the
Workspace Settings and noticed that the 'Automatically
Save Workspace changes' radio button was off. Clicked it
on then closed the 'Group Manager Dialog' and overwrote
AutoCAD LT workspace settings with 'Save Current As...'
That fixed it! ....Geeez!!!...back to work.
-
Thanks everyone
:( -> 🙂