c) I was warned not to try !fdisk years ago since shelled out commands do not have access to keyboard,
so am leery of today trying !sysinfo | more but you could do something like !sysinfo > foofile.txt
then ct dos:/foofile.txt
d) although sysid command or ct messages config will tell you the system id when d3 is up,
be aware text file d3programs\SystemId seems to hold it also. {Or I did !echo 1234567 > SystemId
and then forgot about it years later, hard to be sure now...} Remember, when you open a support case
they will be all 'no tickky no washee' if you cannot cough up the system id. And winbox file save tapes are not
edible to linux based d3 boxes so you cannot sel-restore that messages config item onto another
non-winbox.
Expand the VME - not a good idea. Why not just clear the clog of hold files that nobody is using. SP-EDIT MUD seems a good idea if the users are that stupid.
Agreed Ross however I would suggest that you use "within" far more than anyone else I have ever met - I am afraid I never trusted it so it was no loss when the VME fell out of favour :-)
Is always useful when moving flashed code
Or if not Accuterm, something like TeamViewer which can punch through most firewalls (assuming not against corporate policy)
--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+un...@googlegroups.com
For more options, visit http://groups.google.com/group/mvdbms
Is DesignBais really that badly written.
Small Calls have been the order of the day for D3 for many years now. Big Blob code went out years ago. I regularly recompile and optimise over 1000 routines in a couple of minutes and VME size has never been an issue.
btw, I'm a bit surprised at the dismissal here of ever enlarging the vme. It's a harmless and sometimes helpful procedure, not some dirty little secret vice.
Thanks for the notes on which cad {and remember, not which (cad , ever!}
but I make that my second choice since they toss a bunch of escape strings in the output to do highlighting, and I'm typically going to copy and paste that from my terminal emulator screen to an editor session for use elsewhere.
Also it seems that Designbais may be shipping optimised code which is directly against recommendation because optimisation expands the size."Shipping FlashBASIC code is only recommended when a vendor wishes the code to run on a single platform, and when media size is not an issue"
!ipconfig at : prompt
<snip>!systeminfo at : prompt