Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Dos (?)

Original Message
Name: Sebastian42
Date: January 2, 2008 at 02:21:12 Pacific
Subject: Dos (?)
OS: WinXP
CPU/Ram: PIII/256Mb
Model/Manufacturer: generic
Comment:
The first of a pair of floppy discs that allow booting a WinXp system, to be able to manage the NTFS files from A:\ through NTFSPRO, has an autoexec.bat file. If I add the line 'NTFSPRO' at the end of the autoexec.bat to autolaunch NTFSPRO, I achieve THAT aim, but the end of the process is no longer the A:\ prompt, instead a line appears that reads "Insert a disc with
batch file". (How) Can I get NTFSPRO AUTOlaunched, and still end up with an A:\ prompt ?

Basty


Report Offensive Message For Removal


Response Number 1
Name: IVO
Date: January 2, 2008 at 03:34:47 Pacific
Subject: Dos (?)
Reply: (edit)
As Win XP has no DOS but is a NT kernel system, I suppose you set up an emergency DOS based diskette to access NTFS from A:.

If so, specify what verion of DOS you used to set up the floppy and post your config.sys and autoexec.bat.

The problem you refer sounds like a shortage of conventional memory (the first 640 kB) due to the usually large size of NTFS DOS programs.

And what about the second floppy? What is its purpose?


Report Offensive Follow Up For Removal

Response Number 2
Name: Sebastian42
Date: January 3, 2008 at 01:27:32 Pacific
Subject: Dos (?)
Reply: (edit)
About the second floppy - NTFSPRO is too large to fit on one floppy, hence TWO.
If I type NTFSPRO (manually) after the DOS promts appears (from the first floppy) the
whole process works well. If, as I wrote, I add NTFSPRO to the autoexec.bat, NTFSPRO does get launched, but at the end, I do NOT get an A prompt, but instead the direction to insert another disc.

The only reference to DOS version I have found is displayed on screen and says the (unlikely) V5 ! (when even Win95 was already running V7 !)[NTFSPRO is of 12/5/2003;
Command.com is of 8/6/200]
Config.sys says : device=display.sys con=(ega,,1)
Autoexec.bat says : mode con codepage prepare=((850) ega.cpi)
mode con codepage select=850
keyb us,,keyboard.sys

Incidentally - a further refinement I'd hope for is to get DOSKEY working once the A:\ prompt appears. I don't know which DOSKEY version to add, nor how.


Basty


Report Offensive Follow Up For Removal

Response Number 3
Name: IVO
Date: January 3, 2008 at 02:39:34 Pacific
Subject: Dos (?)
Reply: (edit)
As NTFSPRO spans two floppies I suppose you need to eject the first and insert the second while the program is loading. If so the command requests the first one again to close the autoexec.bat: try to swap again the diskettes and you probably get the A:\> prompt.

I can mail you an open source version of doskey, if you like, with the related (easy) instructions to install.

Just curious, how do you get the bootable DOS floppy?


Report Offensive Follow Up For Removal

Response Number 4
Name: Sebastian42
Date: January 4, 2008 at 08:30:10 Pacific
Subject: Dos (?)
Reply: (edit)
IVO

"As NTFSPRO spans two floppies I suppose you need to eject the first and insert the second while the program is loading."
Correct
"If so the command requests the first one again to close the autoexec.bat"
Ingenious !
"I can mail you an open source version of doskey, if you like, with the related (easy) instructions to install."
That would be very much appreciated.
"Just curious, how do you get the bootable DOS floppy?"
I'm not SURE what you mean there. The instructions for making the floppies say that the NTFSPRO program must be ADDED to a floppy that has undergone the process available from its context menu in WinXP, one of the options in Format is "Create an MS-DOS startup disk".

I have worked out that once I have achieved an A:\ prompt as required, I can then type DOSKEY to activate that program - IF it has been added to the second floppy [that MAY change if I have to put the first floppy back in]. However, DOSKEY from WinXP retruns the comment that it can not run in a DOS program. Doskey from DOS6.22 triggers "Wrong DOS version". I'm answering you now because I had gone on-line to download DOS v5.0 and see if DOSKEY from IT is
acceptable (if I can extract it from dos5.exe !!!!). I will let you know after the experiment tomorrow.
My email address is jphilippa@optusnet.com.au, in case you want to send me what you promised but don't have access to my address.

Basty


Report Offensive Follow Up For Removal

Response Number 5
Name: IVO
Date: January 4, 2008 at 15:01:10 Pacific
Subject: Dos (?)
Reply: (edit)
Well, I spent some time to examine better the whole issue and now I can figure out the process you followed to create your two floppies.

Please, confirm I am right in saying you have to swap the diskettes to get the A> prompt.

If that is right, I think I can solve your doskey issue, but let me know what you want to achieve by using the NTFSPRO diskettes as other commands/tools may be added and the autoexec and config files improved.

Your mail address is accessible by clicking your (underscored) nickname, never show it by posting if you want to avoid spam!.

Sorry the delay in talking is worse than communicating with a mission to Mars, but I'm living in Milano (Italy).


Report Offensive Follow Up For Removal


Response Number 6
Name: Sebastian42
Date: January 4, 2008 at 21:20:51 Pacific
Subject: Dos (?)
Reply: (edit)
IVO
Much has happened since we last communicated. I can confirm that your solution did the trick - and REALLY that is what the message tried to convey - exactly as you put it "Put the first floppy back to access the batch file again".

I don't seem to have told you that NTFSPRO triggers a line on the screen that reads :
"NTFS File System Driver for Dos v5.0"

Expansion of DOS5.exe required a floppy !
It did NOT have DOSKEY - I now remember that was in innovation for DOS6 (or 6.22 ?)

Manually (without DOSKEY) I have tried to change the wrongly spelt Username of the Owner's WinXP account. The relevant file returns a 'not found' when I apply a RENAME, even though it is listed on the screen. Trying to change the attribute from HIDDEN with 'attrib -h \foldername' gives NO progress. NOTHING that I have tried succeeds - but many interesting things happen. I keep being told that the folder is a Windows System file and can NOT be moved or renamed. Even when the 'Registry Find and Replace' function of JV16PowerTools makes numerous changes to the Registry, the wrong name persists !

Basty


Report Offensive Follow Up For Removal

Response Number 7
Name: IVO
Date: January 5, 2008 at 12:42:56 Pacific
Subject: Dos (?)
Reply: (edit)
If you generated the bootable diskette by checking the DOS option in the Win XP dialog box to format a floppy, what you got is actually a Win ME based DOS command interpreter (command.com 08/06/2000 of size 93.040 bytes). Type ver to see the version.

You need a command interpreter from Windows 9X/ME (DOS 7.0 or higher) to manage LFN files accessed via NTFSPRO. That may cause some problems to Doskey from previous Win/DOS releases that however I am faithful to workaround.

Because the job requires a tricky work, please let me know if you are still interested, as what you report in the last section of your post is quite confuse to me. I am really glad to help you, but the work must be worth to do.

If you actually want to correct/replace a defective account/profile, better you post again, in Windows XP Forum, describing clearly what you want to achieve accessing the XP volume from an emergency DOS diskette with NTFS driver (your NTFSPRO).

I master XP and DOS quite fine, but I'm weak about security/administration issues.


Report Offensive Follow Up For Removal

Response Number 8
Name: Sebastian42
Date: January 6, 2008 at 01:56:04 Pacific
Subject: Dos (?)
Reply: (edit)
Irrespective of the outcome of my ultimate aim - renaming a WinXP account - I REMAIN INTERESTED in your offer of a DOSKEY, different from the ones I have. It would be a nice touch to add that to the NTFSPRO !

Incidentally, needing to replace the first floppy to complete the batch file, negates the advantage of launching NTFSPRO automatically from autoexec.bat

Those two are specifically DOS issues and appropriate (I think) to this forum.

Renaming of the account - which I only mentioned to tell you one purpose for NTFSPRO
- is indeed more appropriately dealt with elsewhere.

I find your claims in paragraph 1 & 2 confusing/paradoxical. Did you MEAN to say WinMe in BOTH paragraphs ?

"Type ver to see the version." Very interesting advice - but I don't know to apply it. It must be the DOSKEY you are referring to - if I can NOT get it to run, where would I type 'ver' ?

Basty


Report Offensive Follow Up For Removal

Response Number 9
Name: IVO
Date: January 6, 2008 at 02:59:13 Pacific
Subject: Dos (?)
Reply: (edit)
OK, I try to put at work Doskey, what version I'll decide while work is in progress.

More I try to fix the problem that forces you to swap the diskettes so allowing to insert the NTFSPRO command in the startup batch.

Any way it is likely you have to recreate the bootable floppies following my instructions.

About Win ME and ver just type ver at A> prompt to see the DOS version you are running.

Now I start to work, I'll keep you posted and if I'll achieve the target I'll send you the package.


Report Offensive Follow Up For Removal

Response Number 10
Name: Sebastian42
Date: January 7, 2008 at 01:24:40 Pacific
Subject: Dos (?)
Reply: (edit)
I feel flattered at having triggered some programming !

Basty


Report Offensive Follow Up For Removal

Response Number 11
Name: Sebastian42
Date: January 7, 2008 at 02:35:15 Pacific
Subject: Dos (?)
Reply: (edit)
I did the A:\ver you suggested and it DID say WinME [4.90.3000] (to my suprise !)
So I extracted DOSKEY from my WinMe and added it to the 2nd floppy, and sure enough
DOSKEY is enabled (after I call it) and it works ! I am SO excited !

I am not clear how I would automate the launching of DOSKEY - another autoexec.bat, but on the 2nd floppy ?

Basty


Report Offensive Follow Up For Removal

Response Number 12
Name: IVO
Date: January 7, 2008 at 04:00:34 Pacific
Subject: Dos (?)
Reply: (edit)
The fact you do have the right copy of Doskey avoids me the harder part of the job as I have different versions of the command from DOS 5.00 to Windows 98SE, but not the one native of WinME.

The result of ver would have made you confident about my experience in operating systems.

The autoexec.bat is the first and one batch that is automatically started as part of the boot sequence in a DOS/Win 9X/ME environment.

To automate the installation of Doskey you have to edit your autoexec.bat so

@echo off
mode con codepage prepare=((850) ega.cpi) > nul
mode con codepage select=850 > nul
keyb us,850,keyboard.sys
prompt $p$g
set dircmd=/O:GNE
doskey /bufsize:1024 /insert
ver
echo.
:: End_Of_Autoexec.bat

Omit /insert if you want overwrite behavior as native (any way controlled by the INS key).

Easy... but the problem is due to the need to store doskey on the FIRST floppy; to do so you have to recreate the floppy from XP, add to it the doskey program, edit the autoexec.bat as above and then load the NTFSPRO driver that spans two diskettes (via NTFSPRO Creator, isn't it?).

A smarter behavior is to load NTFSPRO automatically and then leave free the floppy drive, but that requires a further adding to the autoexec and and the setup of a ramdrive in main storage.

Again, are you interested?


Report Offensive Follow Up For Removal

Response Number 13
Name: Sebastian42
Date: January 7, 2008 at 05:41:45 Pacific
Subject: Dos (?)
Reply: (edit)
I had this ready to post before I saw your lastest response : "The (DOS) problem is solved ! - adding WinMe's DOSKEY.COM to the 1st floppy (and adding NTFSPRO, then DOSKEY to the autoexec.bat), makes it worth putting the first floppy back to trigger DOSKEY. DONE !"

I'm happy to send you a copy of the very small DOSKEY.COM from WinMe - or even the whole of DOS from WinMe - if you tell me how to select it out of \Windows\Command\ - total command is 2.9Mb - and give me an address to send it to - I seem unable to attach it to this post.

As for further work on 'my problem' - seems unnecessary since I've achieved what I wanted

Basty


Report Offensive Follow Up For Removal

Response Number 14
Name: IVO
Date: January 7, 2008 at 06:40:40 Pacific
Subject: Dos (?)
Reply: (edit)
Thank you for your offer. I'm glad you eventually solved your troubles putting the batch at work as you wish.

Don't care to send me the WinME's DOSKEY.COM, as I do not have nor like that OS. Just I had to deal with that environment as a fall-out of your post.

Any way if you need more support, contact me freely by e-mail: you find my address by clicking on IVO.

Have a nice day/night, Ciao
IVO


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Dos (?)

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




acer 312T BIOS problem

K7 Turbo possible max fsb?

Pc anywher problem

WinFLP & OE/Outlook2003

Computer resets after a few minutes


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC