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

Autoboot/autorun from floppy

Original Message
Name: Cam_test
Date: July 7, 2005 at 06:41:46 Pacific
Subject: Autoboot/autorun from floppy
OS: window 3.1
CPU/Ram: intel 64mb
Comment:
How do i create a program/file system on a floppy that will run the .exe file from the same floppy without having to type in the execution file name at A:\>. The Auto exec on the C drive has been changed so the computer will boot into the A:\>


Report Offensive Message For Removal


Response Number 1
Name: hiho
Date: July 7, 2005 at 07:46:46 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Could you not point to the A:\*.EXE file in AUTOEXEC.BAT..............

Report Offensive Follow Up For Removal

Response Number 2
Name: jboy
Date: July 7, 2005 at 08:05:57 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
"The Auto exec on the C drive has been changed so the computer will boot into the A:\>"

That... makes no sense.

Life is hard; it's harder if you're stupid. -John Wayne


Report Offensive Follow Up For Removal

Response Number 3
Name: hiho
Date: July 7, 2005 at 09:44:17 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
I surmised he put an entry in AUTOEXEC so he arrived at an A:>_ prompt....who knows maybe we will be enlightened?

Report Offensive Follow Up For Removal

Response Number 4
Name: LinuxOS2
Date: July 7, 2005 at 12:06:51 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Cam test
Could you cut and paste your autoexec.bat and config.sys from a: + c: drives, it helps when we can see what you are talking about......
One way would be to boot from a: and call the file from autoexec there.....

Keep the old stuff running


Report Offensive Follow Up For Removal

Response Number 5
Name: jboy
Date: July 7, 2005 at 12:23:15 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
"maybe we will be enlightened?"

Colour me 'doubtful'

Life is hard; it's harder if you're stupid. -John Wayne


Report Offensive Follow Up For Removal


Response Number 6
Name: Mike Newcomb
Date: July 8, 2005 at 12:03:32 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
LinuxOS2's advice is good.

This is what I was going to suggest.

Good Luck - Keep us posted.


Report Offensive Follow Up For Removal

Response Number 7
Name: Rimfire
Date: July 9, 2005 at 22:24:43 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Is the "The Auto exec on the C drive" anything like the startup sequence in bios?

Report Offensive Follow Up For Removal

Response Number 8
Name: Mike Newcomb
Date: July 10, 2005 at 02:36:21 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Rimfire, talking dos, when a pc starts up, once dos has loaded (which uses 2 or 3 normally hidden files)it then uses two further files which 'personalise' the pc:-
CONFIG.SYS
AUTOEXEC.BAT

I do not think the bios should be confused with the these, as its purpose is basically to boot the pc enough to load the operating system (whatever that might be).

Good Luck - Keep us posted.


Report Offensive Follow Up For Removal

Response Number 9
Name: Mechanix2Go
Date: July 10, 2005 at 02:52:44 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Hi Mike,

Yep.

As long as we're at it. [we're at it again]

io.sys & msdos.sys are usually hidden. And command.com is usually read-only [+r].

M2


If at first you don't succeed, you're about average.


Report Offensive Follow Up For Removal

Response Number 10
Name: Mike Newcomb
Date: July 10, 2005 at 08:37:53 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Hi M2
I was trying to keep it simple and provide an overview as it seemed to me it the new question from a different poster changed the thread.

Hope I got it right. Regards - Mike

Good Luck - Keep us posted


Report Offensive Follow Up For Removal

Response Number 11
Name: jboy
Date: July 10, 2005 at 10:16:22 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
It's the OP, not RF, who doesn't appear to have the first clue about DOS startups.

Kids, it is advisable to do some research before posting the first question that pops into your heads. Informed posters ask better (and fewer) questions, and stand a better chance of comprehending the answers.

Ya gotta do the work - we all did

Life is hard; it's harder if you're stupid. -John Wayne


Report Offensive Follow Up For Removal

Response Number 12
Name: Rimfire
Date: July 10, 2005 at 15:06:09 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Thanks Mike for sharing that wisdom!

As we are all struggling to comprehend the original post, I thought it might be worth trying to clear up the terminology used.

This may be a question related to a workaround to leaving a boot floppy in the drive. But then it might be a serious question poorly expressed. Until the OP returns we can do nothing but speculate.

In the meantime, you can tell me the difference between a floppy and a hard disk if you wish!


Report Offensive Follow Up For Removal

Response Number 13
Name: Cam_test
Date: July 11, 2005 at 02:00:45 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
I will try and be clear. Once the pc is switched on it goes through the usual memory test, display bios, starting MS DOS. Then the PC changes directory to A:\> at this point i have to type in the .exe file name to run the program from the floppy. What I would like to know is what to create on the floppy to make the program run without typing in the .exe each time the PC is booted. I know very little about DOS this is why I posted

Report Offensive Follow Up For Removal

Response Number 14
Name: hiho
Date: July 11, 2005 at 02:11:56 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Point to the A:\*.EXE file in AUTOEXEC.BAT:

http://www.computerhope.com/ac.htm

lets surmise the software is "milling.exe", if your AUTOEXEC.BAT looked like this, yours will not but this is an example:

@echo off
SET BLASTER=A220 I5 D1
SET PATH=C:\DOS;C:\
LH MSCDEX.EXE /D:123
LH C:\CTMOUSE\CTMOUSE.EXE
A:

...then to run the "milling.exe"

@echo off
SET BLASTER=A220 I5 D1
SET PATH=C:\DOS;C:\
LH MSCDEX.EXE /D:123
LH C:\CTMOUSE\CTMOUSE.EXE
A:\cnc\milling.exe

...this would therefore launch the "milling.exe execution file, DOS does not care wether or not it is upper or lower case........


Report Offensive Follow Up For Removal

Response Number 15
Name: Rimfire
Date: July 11, 2005 at 02:45:33 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
As the floppy is dedicated to use one particular program, you should add the location of the program to the path staement if it is not located in the root directory. This allows the program to find any files it might look for.

The name of the executable should be at the end of the autoexec.bat file but before the 'end' statement. Putting it too early will cause dos not to execute commands until you exit the program. Putting it after the 'end' statement will cause it to be ignored.


Report Offensive Follow Up For Removal

Response Number 16
Name: Mechanix2Go
Date: July 11, 2005 at 02:49:06 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Hi Rimfire,

"end" statement in DOS?

M2


If at first you don't succeed, you're about average.


Report Offensive Follow Up For Removal

Response Number 17
Name: Rimfire
Date: July 11, 2005 at 03:02:14 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Hi M2,

Its been a while since I've had to write / edit a dos batch file. I believe that the end statement is optional and as such rarely used.

Damn, I really have forgotten. After a call statement is used, do we use the end or return?


Report Offensive Follow Up For Removal

Response Number 18
Name: Mechanix2Go
Date: July 11, 2005 at 03:21:10 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Hi Rimfire,

IIRR [I often don't] I have not used "end" or "return" in DOS.

It used to be common practice to:

goto end
...
...
:end

But that's simply a convention. It could just as well be:

goto blatz
...
...
:blatz

In NT, there's a "built-in" EOF, which allows for a "hasty exit" and the EOF at the end of the BAT need not be declared. But that's NT, not DOS.

BTW [we're at it again] I make it a practice to code:

::==
@echo off > quit.bat
...
...
::===

It creates a zero length, do nothing, quit.bat. Typical use:

if not exist %1 quit

===
As to OP's issue, it may suffice to have the last line:

x:\somedir\some.exe

But some good 'ol DOS progs would not run unless you are in the dir. [They couldn'y find their overlays / INIs etc]

Racking my brain here. Maybe dBase II was one of them.

In those cases:

c:
cd \somedir
some.exe

M2


If at first you don't succeed, you're about average.


Report Offensive Follow Up For Removal

Response Number 19
Name: Rimfire
Date: July 11, 2005 at 04:06:22 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
We digress!

I prefer adding the path to the path statement in a single use boot because;
1) Using the full path (as in HiHo's post) does not allow the program to find its files,
2) The CD command works well unless you have cause to use it again. Once the focus has been moved, the target programme no longer has direct access to its own files.

I now recall the only time I have had to use the call statement. It was to correct a multiboot configuration where the goto statement was used (to another batch file). This orphaned the rest of the autoexec.bat file.


Report Offensive Follow Up For Removal

Response Number 20
Name: hiho
Date: July 11, 2005 at 04:09:10 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Yes M2GO

I have have occasion to use the following ie:

CD C:\CNC
milling.exe

end statement? was that not for the old Spectrum BASIC?? LoL!!


Report Offensive Follow Up For Removal

Response Number 21
Name: Mechanix2Go
Date: July 11, 2005 at 04:30:08 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
I think END is used in QBasic.

Interestingly, a recent thread in 'programming' indicates that END in VB [6?] causes crashes.

M2


If at first you don't succeed, you're about average.


Report Offensive Follow Up For Removal

Response Number 22
Name: jboy
Date: July 11, 2005 at 08:34:04 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
"I know very little about DOS"

Ok - that much was evident

"Then the PC changes directory to A:\>"

If you're using a bootdisk, that is what you'd expect

As has been mentioned, all that is really necessary is to have a line in a:\autoexec.bat (not AUTO EXEC) invoking the file.

It *really* doesn't get much more basic than that - running commands is what DOS does - and it's with no small amount of amazement to find this has stymied you for 4 days now (probably longer).

good luck - might try some reading

Life is hard; it's harder if you're stupid. -John Wayne


Report Offensive Follow Up For Removal

Response Number 23
Name: hiho
Date: July 11, 2005 at 08:45:34 Pacific
Subject: Autoboot/autorun from floppy
Reply: (edit)
Try reading this and throw out any pre-conceptions before hand:

http://www.dostutor.pwp.blueyonder.co.uk/


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: Autoboot/autorun from floppy

Comments:

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


Data Recovery Software




how to setup call of duty to joytok

WindowsME / HotMail Problem

Corrupt memory

Convert fat32 to Ntfs

Best WinMo phone of 2008


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