John Ames schrieb:
> Okay. I would really like to use FreeDOS, preferrably the full-install CD,
> and definitely with USB disk support. Problem is, the NIC in the computer I
> want to install it on (a 3Com 3C595-TX) does not appear to be recognized by
> either the default packet driver or the manuf
Hi,
Thanks everybody.
Reboot it's not a option. I'm creating a script for bios update. Part of
process is access a TCP/IP net, but I need to free memory to run a update
executable. I'll try using a TERMIN.COM and report it!
Best regards!
On Fri, Mar 20, 2009 at 3:47 AM, bwspos wrote:
>
>
> Fa
Eric Auer schrieb:
> Hi,
>
>> Okay. I would really like to use FreeDOS, preferrably the full-install CD,
>> and definitely with USB disk support. Problem is, the NIC in the computer I
>
> On modern PC, your BIOS already does USB disk support for you and DOS.
You mean USB legacy support (for stor
Do BIOS update 100 % step by step as the manual says. No experiments wit
h DOS versions, TSR's, boot medium (if you shall use legacy floppy then
do so). Otherwise you risk the BIOS update to fail as the developers did
not thought about your modified use.
Ok, well you can experiment if you have the
Hi
On Fri, Mar 20, 2009 at 10:12 AM, Michael Reichenbach <
michael_reichenb...@freenet.de> wrote:
> Do BIOS update 100 % step by step as the manual says. No experiments wit
> h DOS versions, TSR's, boot medium (if you shall use legacy floppy then
> do so). Otherwise you risk the BIOS update to fa
Hi Michael,
> Do BIOS update 100 % step by step as the manual says. No experiments wit
> h DOS versions, TSR's, boot medium (if you shall use legacy floppy then
> do so). Otherwise you risk the BIOS update to fail as the developers did
> not thought about your modified use.
I agree that unloadin
Eric Auer schrieb:
> Hi Michael,
>
>> Do BIOS update 100 % step by step as the manual says. No experiments wit
>> h DOS versions, TSR's, boot medium (if you shall use legacy floppy then
>> do so). Otherwise you risk the BIOS update to fail as the developers did
>> not thought about your modified u
Michael Horvath wrote:
> Option #2 (the default, and the one that doesn't work) results in the
> following error:
>
> "Illegal instruction occured.
> CS= IP=EEC3 SS=D0B4 SP=0004 ES=0070
> ...etc...
> ...etc...
> Aborting program
> EMM386 - unable to continue - Please reboot="
Ben Armstr
Hi Robert, Shane,
> Ben Armstrong ("a Program manager on the core virtualization team
> at Microsoft") recommends the following for MS-DOS on
> http://blogs.msdn.com/virtual_pc_guy/archive/2004/10/21/246136.aspx
Note that this is from 2004 so it cannot be about Virtual PC 2007 ;-)
> device=C:\D
Hi guys;
I've formatted my hard disk, installed the boot manager using the option in
xfdisk and installed freedos. Yet, LILO continues to remain the boot manager
on my hard disk and only shows LINUX as an available kernel.
I just received a 8-bit PIC microcontroller with a low pin developm
Robert Riebisch wrote:
>> "Line #1 in batchfile 'A:\INSTALL.BAT' too long"
>
> Please post the first line of "A:\INSTALL.BAT".
>
> Robert Riebisch
Good catch! When I read the batch file in FreeDOS the file is full of
gibberish. In Notepad on my WinXP machine, however, it is a properly
formatte
11 matches
Mail list logo
