Ray Davison wrote:
what if replacing AtapiCDD by another cdrom-driver?
Used a cdrom.sys V 4.14 internally dated Jan 99. CD is now readable.
I was mistaken, cdrom.sys does not really work. With oakcdrom.sys H:
properly reads the CD, A and B are still confused.
Ray
--
Ray,
It depends on what you want to do.
At work we use MS-Client 3.0 to talk to linux and windows boxes running
as file & print servers. Works pretty well even if we ran into a few
bugs in SAMBA on linux (2.2.7).
One of the best resources for doing that is "World of Windows
Networking" at http:/
Is it possible to connect FREEDOS to a LAN? I looked at the page below
but without descriptions I didn't recognize anything.
Ray
http://www.freedos.org/freedos/software/lsm.cgi?q=d&a=net
---
This SF.Net email is sponsored by: IBM Linux Tutori
Bernd Blaauw wrote:
Ray,
do you have more info?
which cdrom (the burned FreeDOS beta9 prerelease 4 ISO-file?) did you
use, in which cdrom-drive?
fdosboot.bin contains 9FREEDOS. Kernel is dated 31 Jan 04. I didn't
see the kernel identify itself during boot.
what if replacing AtapiCDD by anoth
Hi, maybe an interesting site:
http://www.devdrv.com/shsmod/
some chipsets use extra division by up to 8 to generate the
serial port clock, and the above software can reduce the
divisor to reach > 115.2 kbps. Do not expect that to run
with long cables or reliably or something :-).
Other interesti
> FYI, for dual-booting, I think this should be handled
> by moving / copying files when switching to the other
> DOS system.
I disagree: The boot process must not modify the disk
unless absolutely necessary. And it is NOT necessary
because we can have fdconfig and config on one disk,
coexisting.
Renaming bootup-files on-the-fly like win95 did with older MSDOS?
would be an option, but how to determine "when to rename, when not" ?
W9x has a line in the textfile MSDOS.SYS for this (if I recall correctly
dualboot=0|1)
Current freedos installation uses config.sys and autoexec.bat on the
hard
we tried, in the past. It's fairly simple but time consuming.
What is a problem, is the desire to automate things. For cdrom this is
easy, as all files are in one location.
For diskettes, programs are loaded on different disks.
disk 1 would be bootdisk
but since you don't want to swap disks too o
