sure...

config.sys just has "lastdrive=z"

autoexec is-

@echo off
SET TZ=GHO+08:00
if exist MOUSE.COM MOUSE.COM
echo Loading...
echo enter the number for the image you want:
echo (1) for Windows 7 32 bit, (11) for same with .net 4
echo (2) for Windows 7 64 bit, (22) for same with .net 4
echo (3) for Vista 32 bit,     (33) for same with .net 4
echo (4) for Vista 64 bit,     (44) for same with .net 4
echo (5) for XP 32 bit,        (55) for same with .net 4
echo (6) for XP 64 bit,        (66) for same with .net 4
echo (7) for Master (win7),    (77) for same with VIM
echo (makenew) Will create a new image named "NewGhost.gho"
echo if you use makenew, don't forgot to go rename the file.
CD \GHOST

will von wizzlepig

I don't know whether this will suit you but can restore Ghost images to your networked computers without leaving your desk. A boot disc isn't needed. It works with Ghost 2003 too. You just need the free TBOSDT to copy a bootable DOS partition (from any computer) to a file and boot from the file. Once you have made the file it can be copied and each copy personalized with a different command line for Ghost. (the file is editable with PowerISO etc) The method is described in bootfile.txt, Example 1. Psexec is used to start the restore on the remote computer.

I use this method to restore images to my kids' computers if they have made a mess of the OS. The backup image can be on my computer or their computer.

Brian

Quote:

Yes!  But, I'm not an expert at it--I haven't played around with the necessary *syntax* to know for sure what I'm doing.  But here's the steps involved (I just don't know exactly where you have to apply the steps--for instance if you use the *menucolor* command, do you add the prompt escape codes at the beginning of the individual menu item's list in *config.sys*, or *autoexec.bat*, or.....

So, you have to load the DOS driver called *ansi.sys* in the config.sys file.  And you have to have *ansi.sys* in the list of files on your boot disk or disc.  *Ansi.sys* is included in WinXP's Windows>system32 sub-directory, but I don't know if that's the same one used in old school DOS--probably is though!  So like this in config.sys:

device=ansi.sys

or

devicehigh=ansi.sys

Here's the help file for DOS 6.22:  MS-DOS v6.22 Help: ANSI.SYS

Scroll down a ways and you'll find the escape code #'s for text and background colors--as well as *text attributes* such as *bold*, blink on, etc..

At the bottom of the above is a sample of what the syntax is for the DOS prompt:

Quote:

The *$e[* is the escape code beginning the ansi paramaters sequence.  Then, if I read that correctly, it's turning on text *bold* (the number *1*), and foreground (text) color *green* (the number *32*), and background color *black* (the number *40*).

The *m* ends the ansi escape codes for graphical codes.

The *$p$g* is just the *standard* DOS prompt appearance codes:

Quote:

Notice, you can make the DOS prompt much more interesting with the various codes as well!

Let me know how it turns out if you experiment with this!

Brian wrote on Nov 15^th, 2010 at 12:53pm:


Brian,

Ansi.sys should be one of the files that came with your DOS distribution.

Here's a few more examples of what you can do with ansi.sys.  My own home-brew utility CD boots to a DOS menu enhanced by ansi.sys commands (fig.1).  When shelling out to the command prompt, my DOS prompt embeds a reminder how to get back to the menu (fig.2).  My widely downloaded Dsrfix CD similarly embeds reminder hints (fig.3).

Brian wrote on Nov 17^th, 2010 at 3:59am:

Does it result in any strange characters?  Or does it just stay as ?  Do other prompt commands work?  (e.g., "prompt $d $t ")


Brian wrote on Nov 17^th, 2010 at 3:59am:

I assume that's declared in config.sys, and ansi.sys is in the root directory.  (When config.sys is being processed, there is no path variable yet so the path to ansi.sys must be explicitly specified if not in the root directory.)

Which DOS version are you using?  With MS-DOS 7.1 (aka, Win98se) the corresponding ansi.sys was 9719 bytes and had a datestamp of Apr 23, 1999.


Brian wrote on Nov 17^th, 2010 at 3:59am:

Visually, DOS screens are 80 chars by 25 lines, so if your menu design comprises more than 25 lines the top will scroll off the screen.  The design of my menu allows for 10 double-spaced menu items or 20 single-spaced items.

I use the DOS choice.com function to read alphanumeric keypresses plus [Esc], so programmatically I'm limited to 37 choices.

My configuration files are attached below for reference.

It must have been my ansi.sys. I tried nansi.sys (dated 1991) and now I get a green A:\>

Thanks. I copied ansi.sys from a Win98SE installation in Virtual PC and it works.

So three files work for me...

ansi.sys
nansi.sys
ansi.com