MS-DOS with network support
#1
Posted 27 May 2011 - 10:04 AM
i have to build a MS-DOS floppy image which supports network (with login - password). I'm a little bit lost with tutorials, and as i've no idea about how MS-DOS works, it doesn't help me.
Please help me
#4
Posted 27 May 2011 - 11:13 AM
I'll try it and give you a feed back
#5
Posted 30 May 2011 - 07:58 AM
I download an image from netbootdisk. I put it in my PXE, it boots. There is an autoexec.bat which is supposed to set up network. But C: drive access is denied, probably because of PXE. So i think driver can not be installed.
Any idea ? For example, pre-install the driver ?
#6
Posted 30 May 2011 - 03:47 PM
Which image did you download? Why is it trying to access the C: drive? What messages are nearest to the error message? What is the error message?Any idea ? For example, pre-install the driver ?
#7
Posted 31 May 2011 - 07:18 AM
I don't know why it is trying access the C: drive. It boots, and when it is supposed to launch autoexec.bat, access to C: is denied. That's all, no more informations.
I tried many other images, but i don't know anything about DOS.
At work, already built images contain softwares (like HDDup), and i have no idea how it was done, no one does. It's an old trainee's work.
#8
Posted 31 May 2011 - 01:41 PM
How are you booting the floppy? From a real floppy disk, from grub4dos>image file?
I presume Real drive.
(As I presume too that wouldn't change the letter anyway )
Could it be linked to autoexec.bat's:
netboot\getdrive>%ramd%\a.bat
call %ramd%\a.bat
set a=%drive%
echo . Boot drive auto-detected as %a% drive
But anyway Config.sys=
install=NetBoot\RDISK.COM /S8 /:N
So I have no idea why it tries accessing C:
r.
#9
Posted 31 May 2011 - 01:50 PM
As always, what is your goal? (not how yout think you should reach it)
Anyway, post the contents of the autoexec.bat of the floppy image you are using.
If it calls an "a.bat" post also the contents of the latter...
Wonko
#10
Posted 01 June 2011 - 07:08 AM
Here is my Autoexec.bat : http://dl.dropbox.co...28/Autoexec.bat
betrand : i'm booting from PXE, not a real floppy
Edited by neeko, 01 June 2011 - 07:44 AM.
#11
Posted 01 June 2011 - 07:49 AM
:STEP4 MKDIR %ramdisk%NCDOS MKDIR %ramdisk%DOS
:STEP4
ECHO Ramdisk drive letter is %ramdisk%
Pause
MKDIR %ramdisk%NCDOS
MKDIR %ramdisk%DOS
Try booting from it.
What drive letter is displayed ?
WHAT id "HDDup"?
This?:
http://www.copyrsoft...emid=59&lang=en
Wonko
#12
Posted 01 June 2011 - 08:13 AM
Wow, %ramdisk% is full of void ^^
#13
Posted 01 June 2011 - 08:40 AM
FINDRAMD if errorlevel=6 GOTO DRIVEF if errorlevel=5 GOTO DRIVEE if errorlevel=4 GOTO DRIVED if errorlevel=3 GOTO DRIVEC GOTO END
Change the snippet above and add errorlevels, like:
FINDRAMD
if errorlevel=26 ECHO Z
...
...
if errorlevel=7 ECHO G
if errorlevel=6 ECHO F
if errorlevel=5 ECHO E
if errorlevel=4 ECHO D
if errorlevel=3 ECHO C
PAUSE
GOTO END
See the box here for reference:
http://www.robvander.../errorlevel.php
Wonko
#14
Posted 01 June 2011 - 09:09 AM
#15
Posted 01 June 2011 - 12:57 PM
Try again the initial change.Well, it echoes "C", and now ?
Explanation:
this:
FINDRAMDexecutes a program that returns an errorlevel depending on the drive letter the ramdisk drive (most probably loaded through a line in config.sys), in your setup the generated errorlevel appears to be 3.
the:
if errorlevel=3 GOTO DRIVEC(which was now replaced temporarily by "if errorlevel=3 ECHO C" and actually returned "C") tells to go to the "DRIVEC" label (jumping over the other parts of the batch).
Thus when the execution gets here:
:DRIVEC set ramdisk=C:\ GOTO STEP4the ramdisk variable should get value "C:\"
Now, when you get here:
you should read on the screen::STEP4
ECHO Ramdisk drive letter is %ramdisk%
Pause
MKDIR %ramdisk%NCDOS
MKDIR %ramdisk%DOS
Ramdisk drive letter is C:\
Press any key to continue ....
Can you check again?
Wonko
#16
Posted 01 June 2011 - 01:36 PM
So, it displays what you typed now.
But the access is still denied.
#17
Posted 01 June 2011 - 01:53 PM
You add a check point in the script ECHOing something or using SET and with a PAUSE immediately following it.
This way you check values of variables at various stages.
You move this check point (or add several ones) until you find WHICH actual command in the batch causes the problem, then you find a way to solve the problem.
Just as an example, the next addition I would make would be (after having modified first line to "::@ECHO OFF"):
:STEP4
MKDIR %ramdisk%NCDOS
MKDIR %ramdisk%DOS
PATH=%ramdisk%;%ramdisk%NCDOS;%ramdisk%DOS;A:\
SET PATH
PAUSE
SET TEMP=%ramdisk%
SET TMP=%ramdisk%
Wonko
#18
Posted 01 June 2011 - 02:06 PM
I don't know DOS at all, it used it for the last time more 10 years ago, to launch Publisher ^^
I can't either spend to much time on it, i have to take care about Win7PE and "Linux-PXE" in the same time. I'll try to do what you say anyway.
Thanks
#19
Posted 01 June 2011 - 08:55 PM
Also, if you are PXE-booting the floppy image, how are you doing so? With PXELINUX and MEMDISK?
#20
Posted 06 June 2011 - 07:45 AM
Also, if you are PXE-booting the floppy image, how are you doing so? With PXELINUX and MEMDISK?
Yep. It perfectly works with other DOS images.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users