Re: [Freedos-user] MSdos 7.1 question

[Alain Mouette via Freedos-user]

Hi, I would like to clarify some things:

FreeDOS is limited to 2Gb files, some special programs can use 4Gb (full 
32 bits sector number) but it is not the norm.


FAT32 is free, but IIRC there a patents problems with other newer formats

Disk size is not a problem, I have routinely installed very big 
partitions and FreeDOS can handle that just fine. Remember that FerrDOS 
has evolved a lot over time.


Alain

On 11/2/23 16:53, Rugxulo via Freedos-user wrote:

Hi,

On Wed, Nov 1, 2023 at 2:55 PM Michał Dec via Freedos-user
 wrote:

Do you know maybe where do these limits come from?

I thought it should be 4GiB for both since this is the file size limit
for FAT32.

IIRC, FAT16 in something like classic MS-DOS 6.22 supports max ~65000
files and 2 GB max file size and 2 GB max partition size. (But you can
have four primary partitions.)

FreeDOS supports FAT32 of much larger partition (2 TB?) and 2 GB max per file.


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Feelings on lfn

[Alain Mouette]

When sharing files to/from a Windows system it is VERY important...

But for pure DOS work I avoid it as much as possible

BTW, there is NDN navigator that supports it

Alain

On 11/7/22 10:19, John Vella wrote:
In my opinion, the only advantage is that long file names are more 
descriptive than 8.3 but that being said, I'm old and used to coming 
up with short but descriptive names, so I'm not really bothered 
one way or the other.


On Mon, 7 Nov 2022, 13:09 Joseph Norton,  wrote:

Hi listers:

I’m just curious about how you all feel about the use of lfn in
FreeDOS (or any real DOS).

I notice that the lfn option is rem’d out in the fdauto.bat file
by default, so it would appear that, while support seems to be
there, the feelings of the developers are leaning toward not using
it unless it’s necessary.

If I remember correctly, there are at least 2 DOS tsr’s that deal
with enabling long filename support.

I’m curious about what your feelings about lfn are.  Do you keep
lfn turned on, or off?  If so, why?

Thanks!

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOSshell replacement

[Alain Mouette]

On 7/30/22 21:09, Dave Stevens via Freedos-user wrote:

On Sat, 30 Jul 2022 23:48:54 +0200
Liam Proven  wrote:

Is there anything dead simple that isn't broken and is totally free?
midnight commander is gpl and simple, that any use to you?

I strongly recommendo NDN, Necromencer's Dos Navigator.
Very stable, 32 bit compatible and well behaved
http://ndn.muxe.com/

Alain



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] virt-install freedos

[Alain Mouette]

No more attached file, link here: 
https://www.dropbox.com/s/wk22xq6ecgb85ga/Tec_NetBootDisk%20-%20Cosmodata.html?dl=0


--
You should try *NetBootDisk*, it's a MS-Client

Attached a tutorial I made for a very basic instalation. (portuguese)

Alain

On 5/26/22 10:07, Louis Santillan wrote:
You also need to provide a ‘model’ on the ‘network’ parameter.  e1000 
or rtl8139 have DOS packet drivers available.


On Thu, May 26, 2022 at 4:29 AM  wrote:

Hello everybody. Thanks for the help so far, sorry for the delay
in responding.

The simplest way for me to create a FreeDOS VM on my server was to
install it on a local VM and copy the disk image to the server,
once there I created the VM with the following command.

virt-install \
    --name DOS01 \
    --network bridge=br0 \
    --ram 32 \
    --disk /kvm/disk/dos01.img \
--graphics=vnc,password=cadeafaca,listen=0.0.0.0,port=5913 \
    --hvm \
    --import

Almost everything worked.
The other VMs (Debian) are happy with the bridge interface but
FreeDOS returned the following error.

QEMU network detected.
Physical hardware networking is not supported at this time.

I've tried a few variations trying to use tap interface but still
no success. Any idea what to do?
Like the other VMs, I want this one to be directly exposed to my
internal network, not using NAT.

The point with all this is to try to rebuild the old BBS and DOS
is not exactly an environment I expect to see networking in.
Perhaps a simpler way is to simulate a serial interface and then
try to export it to the network.

Thanks everyone for the help!

Cesar

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Cutemouse /O

[Alain Mouette]

CuteMouse doesn't have any of these "elevating" resources. But whatever 
the mouse sends is passed over to the application. In DOS it is up to 
Appication to uses it


Alain

Em 21/01/2022 12:59, Mercury Thirteen via Freedos-user escreveu:
Most mice operate in a "staged" manner; that is, upon power-up even 
the most sophisticated mouse emulates a basic two button affair, until 
software jumps through a series of hoops to elevate its capabilities 
by sending a series of magic sequences of commands. The problem is 
that most applications only go as far as elevating the mouse to three 
button operation (if that - some perform no "elevation" at all, and 
leave you stuck with the most basic mouse mode) and never even attempt 
to activate wheel mode. Regardless of mode, however, the PS/2 
interrupt (at least for PS/2 mice) fires the same way.


This is done because an interface to the enhanced features of advanced 
mice was never standardized, so manufacturers made do with existing 
commands, but simply gave special significance to certain sequences of 
them which would not normally occur in typical application usage. One 
such example is setting the mouse acceleration with a specific series 
of values instead of the usual procedure of directly setting the 
desired acceleration value directly and leaving it at that.



On Friday, January 21st, 2022 at 10:43 AM, Travis Siegel 
tsie...@softcon.com  wrote:


I believe the problem with the scroll wheel is that it doesn't
generate

an interrupt, so if the mouse driver doesn't specifically look for the

scrool wheel, there's no way for the computer or operating system to

know that it is being used. I had a similar problem under windows

several years ago, and the solution was to turn off one of the
settings

in the dos prompt configuration. That also allowed right clicking
within

the dos prompt, (not just on the dos application, so you could select

paste, copy and such), but actually have the right click be passed to

the dos application. That particular configuration item has since

stopped working as it used to. But, on the other hand, it's really not

necessary anymore, since a right click does the proper thing now.
I have

no idea if there's an equivalent option for dos mouse drivers, but
I do

know if the driver doesn't support scroll wheels, then your mouse
won't

respond to the wheel, no matter how much you move it or click it.

Perhaps there's a command line parameter to activate the scroll
wheel on

your particular driver. I've never used the cute mouse driver, so
can't

say if it does have such a parameter or not.

On 1/21/2022 7:25 AM, Björn Morell wrote:

Hi,

The progs I found which can use scroll wheel

4Dos; Help,Select and History

Syschk

MPXplay

I have tried wheelk butit does not make any difference in any
program

I tried,

I really would love for it to work in File Wizard.

Have any of you found other programs or ways there scroll
mouse works ?

Bear

Freedos-user mailing list

Freedos-user@lists.sourceforge.net


https://lists.sourceforge.net/lists/listinfo/freedos-user


Freedos-user mailing list

Freedos-user@lists.sourceforge.net


https://lists.sourceforge.net/lists/listinfo/freedos-user






___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Proposal to add "unzip16.exe" to FreeDOS Disk Image

[Alain Mouette]

Agreed.

I don't likke FreeDOS getting automagic...

Alain

Em 09/02/2021 22:22, Deposite Pirate escreveu:

I think that's a great idea. I don't like the default FreeDOS UNIXish 
filesystem layout nor the installer and I just always install things manually 
to have files where I like them to be. Getting unzip16 which is needed to 
unpack most stuff often
requires jumping through hoops like finding it online, transferring it to the 
target system by whatever means available.
It would be a time saver if it was included with the freedos bootdisk(s).


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Is there any chance to emulate isa sound card over modern usb sound card

[Alain Mouette]

Well...

You would need to create a multi thread OS, then write a zilion drivers 
for USB, then a generic multi-chanel sound system... (BTW, it's called 
Linux)


Sorry, but at DOS times, the USB was not invented :( so it's support is 
very limited.
Would you be interested in developping that (for free), it may be 
usefull (for you, at least)



Em 16/06/2020 08:01, 温鹏 via Freedos-user escreveu:


ATT

Sorry, here is the usb sound card like on amazon


https://www.amazon.com/NOYITO-Decoder-Board-PCM2704-Sound/dp/B07DMTQM9V/ref=sr_1_2?dchild=1=mini+USB+DAC+PCM2704=1592305161=8-2


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bridged virtualbox adapter

[Alain Mouette]

Use netbootdisk.com to setup your NIC


Em 10/02/2020 09:02, Ben Barker escreveu:

Morning
I have a freedos install running on virtualBox, with the host machine 
being Ubuntu


If I run the networking in NAT mode, all is fine

If I try "bridged mode", then at startup fDos sees the network 
adapter, and reports:


Interrupt number 0x9 (9)
I/O port -xD020 (53280)
My ethernet address is 
but any attempt to see the outside network gives the error:

"cannot resolve host's hardware address"

My mtcp.cfg is:

PACKETINT 0x09 (tried a few values here...)
IPADDR x
NETMASK x
GATEWAY x
NAMESERVER x

Any ideas...?




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 Package LSM Data Verification

[Alain Mouette]

Please, beware of  Stallmanitis, it is a serious desease and highly 
contagious.

In the particular case of FreeDOS it bad, at the time of DOS programs 
were free but GPL was not widely known

Alain


On 18-05-2016 11:12, Tom Ehlert wrote:
>>> Without DOSLFN, no support at all for long filenames?
>> Correct. Although, I hear the was another very buggy one that was
>> around before DOSLFN. I don’t know the name.
> THIS.IS.RIDICULOUS.
>
> one of the worst manifestations of Stallmanitis ever.
>
> bye
>
> Tom.
>
>
> --
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 Missing Packages and XDEL

[Alain Mouette]

Thanks, I will keep that ;-)

Alain

On 07-05-2016 20:44, Jerome E. Shidel Jr. wrote:

Hello Alain,

I could not find your fix at 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/,
where can I get the fixed version, just in case I need to release 
some future fix…


I am not responsible for the packages provided by the Repo.

For now, until the next release that will include xDel, you can retrieve
the updated version from my server at http://dnld.lod.bz/xdel.zip



My pack inculdes 3 locales, en, pt_br and es (I believe that by Aitor 
SM).

Maybe some more come by ;-)

Alain



Thanks, Jerome


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 Missing Packages and XDEL

[Alain Mouette]

Nice :) :)

I could not find your fix at 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/,
where can I get the fixed version, just in case I need to release some 
future fix...


My pack inculdes 3 locales, en, pt_br and es (I believe that by Aitor SM).
Maybe some more come by ;-)

Alain

On 07-05-2016 19:05, Jerome E. Shidel Jr. wrote:

Hello Alain,



Here is the XDEL zip file:
https://www.dropbox.com/s/5xah8zlociu59yi/xdel206b.zip?dl=0

I updated the LSM but I am not 100% sure if the zip file is in
accordance with the rules, specially the HISTORY.TXT file.
If needed just send me a word and I can fix it


For the most part, I think it all looked ok.

I corrected the issues I found. Basically, the LSM needed to be in a
APPINFO directory and the doc needed to be moved as well.
Finally, Jim doesn’t want it to just say “GPL.” So, I expanded
that to “GNU General Public License” in the LSM.

I will include it in future builds and probably in the ALL package set.

Thanks, Jerome


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 - Preview 17

[Alain Mouette]

This disks boots well under VirtualBox (and any machine that I have seen 
so far...)
http://suporte.cosmodata.com.br/downloads/moni/CosmoData-M16012.iso

If you care to have a look, I hope that it helps...

Sorry, it is in portuguese. And there is a comercial program in it (it 
has a password) use it for test only

what I could no do is find a CD driver that works everywhere :(
my simple fix was to increase the size of drive A: so that everything 
that I nedd fits in it.

Alain


On 07-05-2016 18:38, Jerome E. Shidel Jr. wrote:
> Hello Corbin,
>
>> I'm really curious about the VirtualBox compatibility fixes, was there any 
>> major changes?
>> Corbin
>>
> Simple answer:
>
> Not really. :-)
>
> Long answer:
>
> The changes only effect VirtualBox. Real hardware and other Virtual Machines 
> are unchanged.
>
> Really, really, really long answer:
>
> Basically, there were two issues with compatibility in VirtualBox. Neither, 
> were bugs or problems in FDI or any of the utilities it relies upon. The 
> first issue was the installed FDCONFIG.SYS default option 1 would cause the 
> virtual machine to crash when loading JEMM. The second issue sprung up when 
> creating a El Torito Boot CD. Basically, when booting even a stripped down 
> version FreeDOS (more or less only the Kernel, FreeCOM and CD Driver), any 
> program that would access the CD portion of the media caused VirtualBox to 
> lockup.
>
> So, here was the solution.
>
> I added VirtualBox detection to the V8Power Tools vinfo utility. It already 
> detects CPUs from 8086-80686, DOSBox, QEMU and general emulation. I added 
> VirtualBox and VMware to it. I planned adding this detector since about 
> Preview 13, I just finally got around to doing it.
>
> Next, the logic that creates the FDCONFIG.SYS file was already setup in 
> Preview 16 to change the installed Default choice to Option 2. It was only 
> waiting on the vinfo utility.
>
> Finally, there is no way to make the El Torito CD work under VirtualBox at 
> present. This is not an issue with FDI. But, having the installer lockup part 
> of the way into the process (when it access the CD portion) would create a 
> very bad user experience. So, I made the best compromise I could. Under 
> VirtualBox, if you boot the CD, the installer UI is never seen. You get a 
> message telling you that it won’t work and to use one of the other 
> installation media and a command prompt. Not perfect, but the best solution 
> at present. This only is an issue under VirtualBox when booting the from the 
> CD. No other virtual machine platforms exhibit this issue. No other method on 
> VirtualBox does either. There is only one version of FDI for all media and it 
> uses the same utilities. I’m not pointing a finger at VirtualBox. But, it is 
> the primary suspect for the problem.
>
> Regardless of all of that, I have switched building of the FDI previews over 
> to using VirtualBox. Originally, I was building them in VMware. But, 
> VirtualBox is about 5 times faster in the build process. To build a release 
> under VMware took about 15 minutes. Under VirtualBox about 3. The occasional 
> rebuild of all of the package data information files used by FDIMPLES took 
> about 90 minutes. Now, under VirtualBox 15 minutes.
>
> Thanks, Jerome
>
>
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 Missing Packages and XDEL

[Alain Mouette]

Hello Jerome,

Here is the XDEL zip file: 
https://www.dropbox.com/s/5xah8zlociu59yi/xdel206b.zip?dl=0

I updated the LSM but I am not 100% sure if the zip file is in 
accordance with the rules, specially the HISTORY.TXT file.
If needed just send me a word and I can fix it

Alain


On 06-05-2016 15:23, Jerome E. Shidel Jr. wrote:
> Hello Alain,
>
> I mentioned several days ago, that if there anything additional anyone wanted 
> included to let me know.
>
> But, it is still not to late.
>
> However, XDEL is not on the FreeDOS Repo.
>
> As long as I receive it. It is open source and includes the source. Is 
> packaged up with the proper LSM data.
>
> I can include it on future releases.
>
> Thanks, Jerome
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS 1.2 needs you

[Alain Mouette]

I made a XDEL utility, clone of DRDO's but it was happily forgotten :(

Alain

On 06-05-2016 07:52, Jerome E. Shidel Jr. wrote:
> Hello All,
>
> FreeDOS 1.2 needs your help verifying package information. This is one of the 
> main holdups for the
> next OS release. Verifying this data is correct is essential. Especially the 
> the licensing information.
> GPL, GPLv2, MIT, BSD …… Other information, such as website, authors and etc, 
> should also be
>   verified and updated.
>
> So, please select some of these packages that you can verify the 
> APPINFO\.LSM text file
> data. The sooner this is done, the sooner we can have FreeDOS 1.2. :-)
>
> Update this thread to prevent double work and directly email me the updated 
> LSM file(s) (subject
> PKGNAME.LSM to prevent being filtered as spam) I have already removed a 
> couple packages for
> which I know the information is correct.
>
> Thank you in advance, Jerome
>
> ; FreeDOS Installer Package List File
>
> ; BASE Packages
>
> archiver\unzip
> archiver\zip
> base\append
> base\assign
> base\attrib
> base\chkdsk
> base\choice
> base\command
> base\comp
> base\cpidos
> base\ctmouse
> base\debug
> base\defrag
> base\deltree
> base\devload
> base\diskcomp
> base\diskcopy
> base\display
> base\dosfsck
> base\edit
> base\edlin
> base\exe2bin
> base\fc
> base\fdapm
> base\fdisk
> base\fdxms
> base\fdxms286
> base\find
> base\format
> base\help
> base\himemx
> base\jemm
> base\kernel
> base\keyb
> base\keyb_lay
> base\label
> base\lbacache
> base\mem
> base\mirror
> base\mkeyb
> base\mode
> base\more
> base\move
> base\nansi
> base\nlsfunc
> base\print
> base\recover
> base\replace
> base\share
> base\shsucdx
> base\sort
> base\swsubst
> base\tree
> base\undelete
> base\unformat
> base\welcome
> base\xcopy
> util\cwsdpmi
> util\fdnpkg
> util\graphics
> util\shsufdrv
> util\udvd2
>
> ; ALL Packages
>
> archiver\bz2
> archiver\gzip
> archiver\lzip
> archiver\lzma
> archiver\lzop
> archiver\tar
> edit\msedit
> net\mtcp
> net\vmsmount
> net\wget
> util\4dos
> util\biew
> util\bmp2png
> util\bootfix
> util\cdrcache
> util\cpied
> util\daa2iso
> util\dos32a
> util\doslfn
> util\foxcalc
> util\gcdrom
> util\gnubc
> util\grep
> util\less
> util\localize
> util\lscolor
> util\md5sum
> util\memtest
> util\part
> util\pg
> util\srdisk
> util\tee
> util\touch
> util\usbdos
> util\which
> util\xfdisk
> util\zerofill
>
> ; EXTRA Packages
>
> archiver\arj
> archiver\cabext
> archiver\lha
> archiver\lpq1
> archiver\p7zip
> archiver\unrar
> devel\bcc
> devel\bwbasic
> devel\cpp2ccmt
> devel\djgpp
> devel\djgpp_bn
> devel\djgpp_bs
> devel\djgpp_db
> devel\djgpp_fq
> devel\djgpp_fx
> devel\djgpp_gc
> devel\djgpp_gp
> devel\djgpp_mk
> devel\djgpp_ob
> devel\djgpp_rh
> devel\djgpp_tx
> devel\euphoria
> devel\fasm
> devel\fbc
> devel\fbc_help
> devel\fpc
> devel\insight
> devel\jwasm
> devel\nasm
> devel\ow
> devel\perl
> devel\regina
> devel\runtime
> devel\tppatch
> devel\upx
> edit\blocek
> edit\doshexed
> edit\e3
> edit\elvis
> edit\fed
> edit\mbedit
> edit\pico
> edit\tde
> edit\uhex
> emulator\atari800
> emulator\chip8
> emulator\fceu
> emulator\meka
> emulator\mines
> emulator\nosefart
> emulator\simcoupe
> emulator\sneese
> emulator\teo
> emulator\vice
> emulator\xf25
> emulator\z26
> emulator\zboy
> games\boom
> games\btitanic
> games\eliza
> games\empong
> games\ewsnake
> games\fmines
> games\freedoom
> games\frotz
> games\gnuchess
> games\hangman
> games\happylnd
> games\ivan
> games\kiloblas
> games\kraptor
> games\lincrawl
> games\liquiwar
> games\magnetic
> games\mirmagic
> games\nethack
> games\nge_nibb
> games\nyet
> games\psrinvad
> games\qtetris
> games\quadnet
> games\snova
> games\sudoku86
> games\tetris2k
> games\vertigo
> games\vitetris
> games\wing
> games\ww1
> games\xargon
> games\zmiy
> net\ctorrent
> net\curl
> net\dillo
> net\ethtools
> net\gopherus
> net\htget
> net\newsnuz
> net\ntool
> net\picosntp
> net\picotcp
> net\ping
> net\rsync
> net\vncview
> sound\adplay
> sound\bladeenc
> sound\dosmid
> sound\dwj
> sound\gsplay
> sound\lame
> sound\mplayer
> sound\mpxplay
> sound\opencp
> util\ansimat
> util\b64
> util\clamav
> util\clamdb
> util\desi3
> util\dialog
> util\dn2
> util\doszip
> util\fdshell
> util\foxtype
> util\gifsicle
> util\hexcomp
> util\hip
> util\hiram
> util\localcfg
> util\lptdrv
> util\ntfs
> util\opengem
> util\ozonegui
> util\password
> util\pbox
> util\pcisleep
> util\pngcrush
> util\savepart
> util\search
> util\sqlite
> util\terminal
> util\testdisk
> util\tinyaes
> util\unrtf
> util\utf8tocp
> util\wde
> util\xgrep
>   
> ; Thats all folks.
>
>
>
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> 

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

suit yourself...

I just made available what could be the starting point...
Well, I had it almost ready and I use it regularly, so I am sure that it 
works.


But of course, I undesrstand that the fun of it is making one's own ;-)

Alain

On 30-12-2015 17:58, Aitor Santamaría wrote:

Hello Alain,

This idea of Jim's is what is closer to what I had in mind.

I don't know how good would DOS programs requiring VGA (such as games) 
run, and in this case, I would find it more interesting to include X 
(or FLTK, I'm not used to it).


Aitor

On 20 November 2015 at 20:51, Jim Hall > wrote:


On Fri, Nov 20, 2015 at 1:10 PM, Georg Potthast
> wrote:
> Hi,
>
> I made a very small Linux distro called Nanolinux which is only
14 MB in
> size:
> https://sourceforge.net/projects/nanolinux/
>
> I could add Virtualbox to that and then you would get a bootable
ISO with
> about 50 to 70 MB in size that would run your DosemuLimpo
>
> (Although I did not manage to download that with the Firefox
browser,
> it does not recognize "ova" as a file extension. Maybe you put
it into
> a ZIP archive)
>
> Wonder if anybody would be interested to use this solution.
>

I, for one, would be very interested to see a text-mode "small" Linux
that boots up an instance of DOSEMU instead of login on the first
available virtual terminal. (I'd put a regular Linux login on the
second VT.)

This would provide an interesting "sandbox" to run Linux on new
hardware. It would remove issues with hardware compatibility on newer
systems.

I don't know how small such a thing would be, but since it doesn't
require a GUI (Nanolinux uses FLTK instead of X) and "only" needs to
support DOSEMU, I imagine it would be quite small, probably smaller
than the 14MB for your Nanolinux.


jh


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/freedos-user




--


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

On 23-11-2015 14:34, Geraldo Netto wrote:
>> A better alternative would be to start with a minimal version od Ubuntu
>> and stripp some things off.
> For this, maybe you could use the 'uck - ubuntu customization kit'
> Last version is from  2013 but with a few changes you can easily
> remaster ubuntu in a few minutes...
This looks like an alternative, are you willing to five it a try for 
next LTS?

Alain


--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

On 23-11-2015 17:09, Rugxulo wrote:
>> On 22-11-2015 20:45, Rugxulo wrote:
>>> I also added "c:\rugxulo" as host folder, so lemme try and see if
>>> reading from that works: yes!
>> I usualy don't use a host mount for C: as it can interfer with the
>> booting process and DOS's utilities
>> IIRC D: is default for that
> I'm not sure I understand. IIRC, it appeared as "/media/sf_rugxulo"
> (or some such), and I made it appear read-only. Also, IIRC, DOSEMU
> typically makes D:\ the Linux partition host, so you can access some
> files there.
C: corresponds to a directory inside ~/.dosemu, it contains everything 
that is needed for FreeDOS, including the dosemu utilities. So I never 
change that.
Yes, D: is mounted by default to the linux directory
So maybe the best might be to map anything else do E:, this is done in 
autoexec.bat using some dosemu directive, it should be easy ;-)

>
>>> Doom works without sound, which (AFAIK) is a fairly common fault, even
>>> under DOSEMU. I was using (updated) MBF, but shareware Doom won't even
>>> run at all.
>> Ok, sound is probably off, I never used it ;-)
> Sound isn't exactly important to me, but obviously in games it is nice
> to have. Not sure exactly how huge DOSBox (with all libs) would be,
> but that's presumably a better answer, at least for gaming.
Do you have any simple DOS program to play around with sound? I can 
check how to enable it
;-)

Alain


--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

That may sound nice, but it misses something that I consider essencial: 
It has to carry all hardware drivers so that it can work on any machine ...
Does anyone know how to do that?

And there is another point that is important for me: I intend to use 
FreeDOS along with other Linux things. This is easy with Ubuntu, but not 
with Buildroot.

A better alternative would be to start with a minimal version od Ubuntu 
and stripp some things off.

Alain

On 23-11-2015 11:55, Geraldo Netto wrote:
> Hi All,
>
> Well, Maybe we could use buildroot [1] to create such minimalist distro
> Buildroot is very flexible and allows to embed X
> Last time i played with it, i was able to create a distro in ~14MB
> (squashfs) with python and X
> I know that squashfs is not feasible for older machines, but we can
> tune the compression on buildroot :)
> The only thing is to add dosemu on it which is not difficult,
> but i would suggest to compile dosemu 'statically' and then copy the 
> binaries...
>
>
> [1] http://buildroot.uclibc.org/
>
>
> Kind Regards,
>
> Geraldo Netto
> Sapere Aude => Non dvcor, dvco
> http://exdev.sf.net/
>
> Em 20/11/2015 17:52, "Jim Hall"  escreveu:
>> On Fri, Nov 20, 2015 at 1:10 PM, Georg Potthast
>>  wrote:
>>> Hi,
>>>
>>> I made a very small Linux distro called Nanolinux which is only 14 MB in
>>> size:
>>> https://sourceforge.net/projects/nanolinux/
>>>
>>> I could add Virtualbox to that and then you would get a bootable ISO with
>>> about 50 to 70 MB in size that would run your DosemuLimpo
>>>
>>> (Although I did not manage to download that with the Firefox browser,
>>> it does not recognize "ova" as a file extension. Maybe you put it into
>>> a ZIP archive)
>>>
>>> Wonder if anybody would be interested to use this solution.
>>>
>> I, for one, would be very interested to see a text-mode "small" Linux
>> that boots up an instance of DOSEMU instead of login on the first
>> available virtual terminal. (I'd put a regular Linux login on the
>> second VT.)
>>
>> This would provide an interesting "sandbox" to run Linux on new
>> hardware. It would remove issues with hardware compatibility on newer
>> systems.
>>
>> I don't know how small such a thing would be, but since it doesn't
>> require a GUI (Nanolinux uses FLTK instead of X) and "only" needs to
>> support DOSEMU, I imagine it would be quite small, probably smaller
>> than the 14MB for your Nanolinux.
>>
>>
>> jh
>>
>> --
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
> --
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741551=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>


--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

On 22-11-2015 20:45, Rugxulo wrote:
> I also added "c:\rugxulo" as host folder, so lemme try and see if 
> reading from that works: yes! 
I usualy don't use a host mount for C: as it can interfer with the 
booting process and DOS's utilities
IIRC D: is default for that

> Doom works without sound, which (AFAIK) is a fairly common fault, even 
> under DOSEMU. I was using (updated) MBF, but shareware Doom won't even 
> run at all. 
Ok, sound is probably off, I never used it ;-)

> I don't know what would be best here. I'm no networking guru. 
Just two interesting options
Networking as NAT is easier but you are on a separate subnet and can 
access only the internet
Networking as Bridge puts you on the same network as your host and you 
also have access (can be accessed) you LAN

> Links2 also seems to work fairly well. Once you have those two pieces, 
> it's easy to grab other stuff. 
:)

> I assume you're aware of other DN variants (with sources, unlike NDN): 
> original DN151 or spinoffs like DN2 and DNOSP. Also don't forget 
> Doszip! ;-) But yeah, I like NDN too, obviously.
A long time ago I testes a lot of variants, NDNwas the only one that met 
some criteria like LFN and DPMI.
Once I got a version that is running 100% I never bothered to check again
;-)

Alain


--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

On 22-11-2015 21:19, Rugxulo wrote:
> I forgot to mention that you're using an older kernel and maybe an
> older shell too (0.84-pre XMS_Swap and not 0.84-pre2 XMS_Swap). Hmmm,
> but that's your translated version (which you lost sources for), so I
> can probably sympathize with that. I honestly don't know the
> difference (pre vs. pre2), probably minor, but it's (almost) always
> best to use latest versions of things.
Yes, I kept it because of the translation, and as it works just fine I 
will stick to it.
I remember that translatinf Command.com is a lot of work, compiners and 
such :(

> But back to the kernel: is there a reason to rely on 2039 here? (And
> your Cosmodata.iso seems to use 2038!) I vaguely remember something
> regarding i18n (nlsfunc) missing in some older versions, only added in
> semi-recent versions. Anyways, unless there's a regression, I'd
> recommend refreshing to latest 2041 kernel,
Cosmodata.iso was creates around FreeDOS 1.1, I made a full review of 
all new versions and updated them, along with the sources.
Maybe it could be done again sometime soon

>   if you ever decide to finalize and publish this .ova somewhere.
That is about the idea, I believe we could build something new allong 
the same lines.
This can be a entry point to many users to FreeDOS

Alain

--
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

On 20-11-2015 22:36, Rugxulo wrote:
> Just to give some minor feedback for your valiant efforts 
Thanks :) :)

> It does whine at bootup about "home/alain" (shared) not existing, but 
> I didn't test that functionality yet. 
That is just the shared folder configuration, it is the best way to 
access your machine's files.
I am not sure what would be the best default configuration

> Didn't test any graphical stuff (e.g. Doom) yet. 
when you can, please report :)

> I had to switch from (default) "bridged" to "NAT" first, in VBox 
> settings. 
I use Bridged to share resources on my local network.
We could change that in a general distribution

> Well, I haven't tested much else (e.g. Links2) yet, but I did use the 
> host (Linux) wget to grab the old FreeDOS/DJGPP build of wget from 
> iBiblio. Once I created a simple wattcp.cfg (and "set WATTCP.CFG=..." 
> accordingly in autoexec.bat) and created a wgetrc, then it seems to 
> work fine, e.g. grabbing a .ZIP file from https://sites.google.com/ 
:) :) :)

> The bigger problem, beyond even translated text, is the unfamiliarity
> of the keyboard layout. For instance, finding chars like '\' and '/'
> seems a bit difficult (at least to my uninformed self). A quick Google
> image search shows that some .br keyboards have a key to the left of
> the 'z' char, which I sadly do not, heh. Sure, numpad has '/' but it's
> not available in all contexts.
That should be configures in Autoexec.bat using standard FreeDOS keyb


> Other minor comments:
>
> * NDN (2006) isn't even latest (2010) version:  http://ndn.muxe.com/
I have been using this for years, as it is 'just-fine" I never bothered 
to upgrade.
I will have a look at the new one.

Alain


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

On 20-11-2015 21:41, Rugxulo wrote:
> On Fri, Nov 20, 2015 at 5:05 PM, Alain Mouette <ala...@pobox.com> wrote:
>> I personaly prefer a mainstream distribution. I used Ubuntu 14.04 LTS
>> The reason is that if other programs are need in the Linux part, it
>> would be easy to install.
>> Dosemu has a pretty good interation with Linux...
> I'm not sure what is the best foundation to build upon. Debian? Arch?
> Gentoo?? Linux From Scratch??? (Heck, even FreeBSD used to support
> DOSEMU, but nowadays you're probably stuck with an ancient QEMU 0.11
> or perhaps bhyve, which I've never tried).
My choice was not based on "smallest" but just "small enough". Ubuntu is 
what I use for a dozen VMs in my dayly use. I have a base-VM uppon which 
I build them all and I like to have some confort, I just used that one.

Just to give you an idea of a few things:
*) do it without Synaptic, it uses huge libaries
*) compile Dosemu on a different VM and copy to the target for install
*) unfragment the disk image
Also there could be a general cleanup of unused packages, I just left it 
all there

As you can see, I am absolutely not an optimization fanatic ;-)

In fact it may be the oposite, I use dosemu as a TOOL, and I usualy need 
other tools to work with it

Alain

>
> I'm not complaining. Your distro is interesting, but I'm not sure I
> have much insight for how to noticeably improve it.
>
> Puppy is quite a bit smaller than Ubuntu. I'm honestly not sure if
> they still make Ubuntu derivatives anymore. I'm still (sometimes)
> natively using ancient Lucid Puppy, which is considered quite old. I
> do see some builds (and forgot I briefly tested under VM) Tahr-Pup
> 6.x, but I don't know the details. The only real advantage to Puppy is
> leanness (perhaps too much), thus much smaller size. Of course,
> whichever Puppy version being compatible with an LTS release isn't bad
> by any stretch. Though I don't honestly know if it's worth switching,
> if you know what I mean.
>
> So I don't really keep up-to-date with Puppy by any stretch, even if I like 
> it.
>
> 1). http://distro.ibiblio.org/puppylinux/puppy-tahr/iso/
>
> (unfortunately, the following topics are somewhat old, so they may not
> apply to all versions)
>
> 2a). http://murga-linux.com/puppy/viewtopic.php?t=57096
> 2b). http://murga-linux.com/puppy/viewtopic.php?t=87318
>
> --
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] picoTCP: a modern, open-source TCP/IP stack for DOS

[Alain Mouette]

Due to zero interest in the VM with Linux+FreeDOS that I uploaded, it is 
unprobable that LIDOS will get much work done...

Remember that for FreeDOS, picoTCP is all about applications, so nothing 
needs to be done and should work out of the box in that VM

And anyway, I don't know how to run a DOS graphic program using Lidux 
hardware drivers. This is a real show stopper :(
If anyone knows how to do that, things may get interesting...

Alain



On 20-11-2015 11:34, Geraldo Netto wrote:
> Once again my overflow of gratitude:
>
> while (1) {
>   Mateusz++;
> }
>
> Alain, maybe we could update LIDOS with Mateusz picoTCP
>
>
> Kind Regards,
>
> Geraldo Netto
> Sapere Aude => Non dvcor, dvco
> http://exdev.sf.net/
>
>
> On 19 November 2015 at 17:00, Mateusz Viste  wrote:
>> Hello group,
>>
>> I write this message to share a little news about what I was doing in my
>> spare time these last two months: porting picoTCP to DOS.
>>
>> picoTCP is a modern, dual-stack, open-source TCP/IP stack. It has been
>> created by the good people at Intelligent Systems (Altran), primarily as
>> a stack designed for embedded computing (hence hardware with very
>> limited horse power). It is backed by a well established corporation and
>> it's actively maintained.
>>
>> I played with the stack for some times now, and ended up building an
>> entire DOS compatibility layer around it. A few patches were required to
>> the stack, a few days of development, many hours of debugging - but here
>> it is - the first public release of picoTCP for DOS!
>>
>> http://picotcp4dos.sourceforge.net
>>
>> The project contains three major parts:
>>
>> - ipcfg: a little tool that allows to configure networking on your DOS
>> machine (IP, DNS, etc). No, it's not a text file - I wanted to avoid the
>> complexity of parsing a text file, and opted for a binary configuration
>> file that is manipulated via ipcfg. It's much more flexible that a text
>> config file, while being much easier/faster to load at runtime.
>>
>> - ping: no need to explain, I guess... my ping tool for DOS, based on
>> picoTCP - crucial when it comes to testing your networking
>>
>> - an OpenWatcom library package (openwatcom, large memory model) - this
>> is for the fellow developers that would like to use the DOS version of
>> picoTCP inside their network-enabled, 16-bit DOS programs. I integrated
>> a packet driver schim, a DOS-compatible timer, as well as the whole IP
>> configuration logic, so it is now a simple (2 functions!) public API
>> that allows to load picoTCP, use it, and unload it.
>>
>>
>> *** Short how-to ***
>>
>> 1. Download picotcp4dos and unzip it on your drive
>> 2. Set the location where the config file will be stored, for example:
>> SET PICOTCP=C:\PICOTCP.DAT
>> 3. Bind picoTCP to the interrupt vector of your packet driver, example:
>> ipcfg int 60
>> 4. Configure your IP settings using ipcfg, or use DHCP (ipcfg dhcp)
>>
>> enjoy!
>>
>> Mateusz
>>
>>
>> --
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
> --
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

I personaly prefer a mainstream distribution. I used Ubuntu 14.04 LTS

The reason is that if other programs are need in the Linux part, it 
would be easy to install.
Dosemu has a pretty good interation with Linux...

Alain


On 20-11-2015 20:11, Luis Rivera wrote:
> would you consider DOSemu for tinycore linux?
>
> http://tinycorelinux.net/
>
> Cheers,
>
> Luis Rivera
>
>
> On 20 November 2015 at 16:01, Rugxulo  wrote:
>> Hi,
>>
>> On Fri, Nov 20, 2015 at 3:06 PM, Eric Auer  wrote:
>>> For DOS purposes, I would prefer a graphical Linux. It does not
>>> have to have huge and/or proprietary 3d accel drivers, a basic
>>> VESA driver should be enough to have fun with DOS games and the
>>> SB16 emulation and other goodies of DOSEMU.
>>>
>>> Of course this could also be a "framebuffer console" Linux, but
>>> when I have Linux anyway, I want to be able to also have multiple
>>> windows. A simple Window Manager like XFCE or LXDE can do that :-)
>>>
>>> For example Kwort Linux runs xfce4 well (?) on 64 MB, while
>>> LXDE Lubuntu and XFCE Xubuntu recommend 256 or 512 MB RAM...
>>> LXDE.org calls 256 MB Pentium II moderate and 512 MB P3 fast.
>> Perhaps (some variant of) PuppyLinux would suffice? Especially one
>> with compatibility to outside packages.
>>
>> a). http://slackbuilds.org/repository/14.1/system/dosemu/
>> b). http://bkhome.org/news/?viewDetailed=00293   (32-bit .iso is "only" 208 
>> MB)
>> c). http://www.slackware.com/releasenotes/14.1.php
>>
>> --
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
> --
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

On 20-11-2015 17:51, Jim Hall wrote:
> I, for one, would be very interested to see a text-mode "small" Linux
> that boots up an instance of DOSEMU instead of login on the first
> available virtual terminal. (I'd put a regular Linux login on the
> second VT.)
>
> This would provide an interesting "sandbox" to run Linux on new
> hardware. It would remove issues with hardware compatibility on newer
> systems.
>
> I don't know how small such a thing would be, but since it doesn't
> require a GUI (Nanolinux uses FLTK instead of X) and "only" needs to
> support DOSEMU, I imagine it would be quite small, probably smaller
> than the 14MB for your Nanolinux.
If someone solves the "Graphic problem", I am very willing to help.

alain
>
>
> jh
>
> --
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

Hi,
(top posting because the answer is global)

That is exactly what I did... A Linux distro with Lxde that runs 
Dosemu+FreeDOS
It has only basic utilities: File manager, Basic Editor and few 
configuration utilities, it could be made a bit smaller...

I chose Lxde over Xfce because it is being actively developped and it't 
basic ustilities are reasonably good.
OTOH, Xfce seems to be "old" and not very actively mantained.

Alain

On 20-11-2015 19:06, Eric Auer wrote:
> Hi Jim, Alain, Georg et al,
>
>> I, for one, would be very interested to see a text-mode "small" Linux
>> that boots up an instance of DOSEMU instead of login on the first
>> available virtual terminal. (I'd put a regular Linux login on the
>> second VT.)
> For DOS purposes, I would prefer a graphical Linux. It does not
> have to have huge and/or proprietary 3d accel drivers, a basic
> VESA driver should be enough to have fun with DOS games and the
> SB16 emulation and other goodies of DOSEMU.
>
> Of course this could also be a "framebuffer console" Linux, but
> when I have Linux anyway, I want to be able to also have multiple
> windows. A simple Window Manager like XFCE or LXDE can do that :-)
>
> For example Kwort Linux runs xfce4 well (?) on 64 MB, while
> LXDE Lubuntu and XFCE Xubuntu recommend 256 or 512 MB RAM...
> LXDE.org calls 256 MB Pentium II moderate and 512 MB P3 fast.
>
> Other possible choices, inspired by the Wikipedia list of WM:
> https://en.wikipedia.org/wiki/Comparison_of_X_window_managers
>
> http://windowmaker.org/themes.php (requirement info anybody?)
>
> http://www.fluxbox.org/screenshots/ (somewhat odd and basic?)
>
> Maybe too basic: Openbox w/o LXDE or www.joewing.net/projects/jwm/
>
> I personally find XFCE more versatile but also heavier than LXDE:
>
> https://help.ubuntu.com/community/Installation/LowMemorySystems#Adding_a_window_manager
>
> Have not tested OpenBox, IceWM, Fluxbox or FVWM-Crystal yet, you?
> The old FVWM2 or FVWM95 might be enough, if you like config files.
>
> Cheers, Eric
>
>
>
> --
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

On 20-11-2015 17:10, Georg Potthast wrote:
> I made a very small Linux distro called Nanolinux which is only 14 MB in
> size:
> https://sourceforge.net/projects/nanolinux/
It looks very nice :)
Justa a question: does it have all Linux hardware drivers so that it can 
run anywhere, including old and new machines?

> I could add Virtualbox to that and then you would get a bootable ISO with
> about 50 to 70 MB in size that would run your DosemuLimpo
Well, those are two different projects, to install VirtualBox it would 
grow too much. In fact What I did is the oposite: It is already 
installed inside VirtualBox so that anyone can use it

> (Although I did not manage to download that with the Firefox browser,
> it does not recognize "ova" as a file extension. Maybe you put it into
> a ZIP archive)
Done, 
https://dl.dropboxusercontent.com/u/33399957/FreeDOS/Ubuntu140432-DosemuLimpo-1.ova.zip
but wait, it is still uploading

> Wonder if anybody would be interested to use this solution.
I believe that you are in the direction of a very nice solution: a Linux 
that can be installed anywhere and run Dosemu+FreeDOS+Network. Without 
graphics it is quite easy to do, but not so interesting

Alain
> Georg
>
>> Hi,
>>
>> I have been using FreeDOS on a Linux VM for a few years now and I made a
>> special image to make it public:
>> https://dl.dropboxusercontent.com/u/33399957/FreeDOS/Ubuntu140432-DosemuLimpo-1.ova
>>
>> * VirtualBox Appliance, just: Files > Inport appliance... and you have a
>> full VM
>> * Based on Ubuntu LTS with LXDE, as light as possible to remain usefull
>> * Fast access to host files using VirtualBox share
>> * Dosemu and FreeDOS fully preconfigured, can run graphic programs
>> * Network fully functional, can talk to any device on your network
>> * 3 FreeDOS instance can access the network and talk to each other too
>> * There are a few Dosemu patches applied for graphics and keyboard
>>
>> Some of it (most) is in portuguese. If there is some interest I can make
>> an international version or some needed resource
>>
>> Alain Mouette - from Brazil ;-)
>>
>


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

I was not able to do that on my laptop (running Debian) years ago in any 
satisfactory way, that is why I started using VirtualBox...


It works fine with dosemu
And it works fine booting Freedos Clean directly on VirtualBox too

Alain

On 15-11-2015 03:16, Mark Spalenka wrote:
Using MEMDISK in GRUB to boot FREEDOS from the local hard drive on 
later model machines is what I am getting from you as a solution to 
boot FreeDOS from a local Harddrive on a laptop. If you have any other 
solutions that would allow me to boot FreeDOS from a Hard Drive I 
would be interested in learning. Once again, I just want to boot 
FreeDOS from my Harddrive on a Centrino or Later model PC. I have 
linux on this PC. I do not want to share any memory with another 
Operating System. This is called 'Booting Native' as I understand 
terminology. I want to boot FreeDos Native and then maybe, just maybe, 
put Linux in a DOS Box of memory. Any other suggestions? Thanks for 
the help.

Mark Spalenka



On Saturday, November 14, 2015 8:54 AM, Alain Mouette 
<ala...@pobox.com> wrote:



That is not "directly" bootable. It is a VirtualBox appliance, it is 
neant to be loaded inside Virtualbox:


In Virtualbox manager GUI, goto File > Appliance > import > everything 
else can be lefta as is...
Then you will get a new Virtual Machine, when you initialyzed, it will 
boot Linux

On the Desktop there are some Icons that will boot FreeDOS preconfigured.

I hope this help, feel free to ask again if needed.

Alain


On 13-11-2015 23:31, Mark Spalenka wrote:
I have loaded the FreeDOS onto my Hard drive with Linux(Unbuntu) but 
have not been able to boot directly to FreeDOS. The Boot Loader is 
GRUB.I have placed the FREE DOS info on aselection for GRUB. But 
still does not work. I am looking for someone whom may know the GRUB 
commands for loading FREEDOS. Any suggestions?

Mark Spalenka
markspalenka2...@yahoo.com <mailto:markspalenka2...@yahoo.com>



On Friday, November 13, 2015 1:13 PM, Alain Mouette 
<ala...@pobox.com> <mailto:ala...@pobox.com> wrote:



Hi,

I have been using FreeDOS on a Linux VM for a few years now and I made a
special image to make it public:
https://dl.dropboxusercontent.com/u/33399957/FreeDOS/Ubuntu140432-DosemuLimpo-1.ova

* VirtualBox Appliance, just: Files > Inport appliance... and you have a
full VM
* Based on Ubuntu LTS with LXDE, as light as possible to remain usefull
* Fast access to host files using VirtualBox share
* Dosemu and FreeDOS fully preconfigured, can run graphic programs
* Network fully functional, can talk to any device on your network
* 3 FreeDOS instance can access the network and talk to each other too
* There are a few Dosemu patches applied for graphics and keyboard

Some of it (most) is in portuguese. If there is some interest I can make
an international version or some needed resource

Alain Mouette - from Brazil ;-)


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net 
<mailto:Freedos-user@lists.sourceforge.net>

https://lists.sourceforge.net/lists/listinfo/freedos-user




--


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net  <mailto:Freedos-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/freedos-user



--

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net 
<mailto:Freedos-user@lists.sourceforge.net>

https://lists.sourceforge.net/lists/listinfo/freedos-user




--


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS running on Linux

[Alain Mouette]

Answering inline:

On 13-11-2015 23:44, Rugxulo wrote:
> Hi,
> On Fri, Nov 13, 2015 at 12:42 PM, Alain Mouette <ala...@pobox.com> wrote:
>> I have been using FreeDOS on a Linux VM for a few years now and I made a
>> special image to make it public:
>> https://dl.dropboxusercontent.com/u/33399957/FreeDOS/Ubuntu140432-DosemuLimpo-1.ova
> Exactly how big is it? (I'm guessing not very small. 2+ GB??)
It's 992M bytes. I used LXDE-core to keep it small but with some basic 
functionality: editor, file manager and a little configuration

>
>> * VirtualBox Appliance, just: Files > Inport appliance... and you have a
>> full VM
>> * Based on Ubuntu LTS with LXDE, as light as possible to remain usefull
> I guess I was naive in expecting someone to make a console-only
> version first. (Not that I'm complaining.)
I want very much to make one such, but I have a few concerns:
1) it will be usefull if based on a distro that has universal hardware 
drivers, including video
2) I have no idea of what would be the best way to run Dosemu+FreeDOS in 
graphics mode without a window manager but using Linux drivers. Or maybe 
a lighter window manager
3) This VM is based in configuration that I have been using and 
perfecting over the years for my day-job

>> * Fast access to host files using VirtualBox share
>> * Dosemu and FreeDOS fully preconfigured, can run graphic programs
>> * Network fully functional, can talk to any device on your network
>> * 3 FreeDOS instance can access the network and talk to each other too
> So packet driver stuff (Watt-32, e.g. Wget) works?
Y-E-S !!! Packet Drivers are fully configured and are working with any 
ethernet configuration of the VM
There is even a PING command included, but it doesn't use Watt-32.
I would appreciate some more testing ;-)

>> * There are a few Dosemu patches applied for graphics and keyboard
>>
>> Some of it (most) is in portuguese. If there is some interest I can make
>> an international version or some needed resource
> I don't think there is much interest in i18n. I think we're all too
> tired or just used to living without it, which is probably not ideal.
> :-/

I was not thinking of i18n, but most of it is in portuguese (that is 
what I use), I was thinking of an English only release.
Most of the scripts I wrote lately are already with english comments ;-)


Alain


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS running on Linux

[Alain Mouette]

Hi,

I have been using FreeDOS on a Linux VM for a few years now and I made a 
special image to make it public:
https://dl.dropboxusercontent.com/u/33399957/FreeDOS/Ubuntu140432-DosemuLimpo-1.ova

* VirtualBox Appliance, just: Files > Inport appliance... and you have a 
full VM
* Based on Ubuntu LTS with LXDE, as light as possible to remain usefull
* Fast access to host files using VirtualBox share
* Dosemu and FreeDOS fully preconfigured, can run graphic programs
* Network fully functional, can talk to any device on your network
* 3 FreeDOS instance can access the network and talk to each other too
* There are a few Dosemu patches applied for graphics and keyboard

Some of it (most) is in portuguese. If there is some interest I can make 
an international version or some needed resource

Alain Mouette - from Brazil ;-)


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] trouble printing in clipper when using freedos

[Alain Mouette]

Your problem is probably that the paralel port on your second computer 
is not labeled "LPT1"


You can several alternatives:
1) look in the BIOS if another LPT is available, that could happen even 
if you don't have a phisical connector.


2) That extension board probably has a configuration software, use it to 
configure that LPT to "1"

For NetMOS this utility is generaly nmdosin.com


Alain

Em 18-09-2015 09:15, Marlon Ng escreveu:

Hi guys.

I have a desktop computer with a motherboard that has a built-in 
parallel port.  When I boot into FreeDOS and run an old Clipper 
program, the program can print just fine, without editing any system 
files.  It just works.


I have another desktop computer in which the parallel port is an 
expansion, not built-in with the motherboard.  Upon printing using 
Clipper program, I get:

Error: Term/0
Quit / Retry
Something like that.  It cannot print.

I wonder if this is the answer:
http://help.fdos.org/en/hhstndrd/base/printer.htm
If it is, please help. I don't quite get it.

Other info that may or may not be relevant:
-- I believe the installed freedos is 1.0 , not the latest.
-- When running the Clipper program in Windows 7 via command prompt, I 
can print.  However, I had to go to Control panel, View devices and 
printers, right-click the printer (epson LX310) , Printer properties, 
Ports tab, Enable bidirectional support and enable printer pooling, 
checked LPT1, LPT2, and LPT3.  That made it possible for me to print 
in Clipper program.  Before doing all of that, I get an error like it 
cannot communicate with the printer.


Summary: Parallel port is only an expansion.  Using Clipper in Windows 
7 command prompt, it can print.  Using Clipper in FreeDOS, I get 
Error: Term/0


Thank you so much!


--


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Rugxulo IS A FRAUD!!!

[Alain Mouette]

Hi Jack...

Why do you need to be so agressive? YOU DO A GREAT JOB FOR FREEDOS, but 
not everyone has do do things your way...

Peace, please !!!

Alain

Em 30-06-2015 08:23, Jack escreveu:
 Note the following comments by Rugxulo in this post:
 www.bttr-software.de/forum/forum_entry.php?id=14140

 * If you want to try his latest drivers (Mar-18) [sic], grab them from
 * his DropBox, but since he doesn't even use FreeDOS (only MS-DOS 6.22),
 * I'm not sure if they work at all anymore:

 And note the following comments by Rugxulo in this post:
 www.mail-archive.com/freedos-user@lists.sourceforge.net/msg16396.html

 * I hope Jim Hall removes every ounce of work you've ever done for FreeDOS.
 * I hope he deletes it all from BASE, iBiblio mirror, and everything
 else.

 Now, note the following comments by Rugxulo in THIS post:
 www.mail-archive.com/freedos-user@lists.sourceforge.net/msg16472.html

 * BTW, I forgot I had Doom 1.9 (shareware) here (circa 1995), so I did a
 * quick install (no music, PC speaker sfx). It played just fine for
 * several levels, using default extender ... until I quit the game, then
 * it crashed/hung/beeped with MCB error.   :-P And that's on a more
 * modern machine than yours, of course not running LBACACHE but still
 * using (Mar-05, 2015) XMGR, UIDE, RDISK.

 Rugxulo, you are a FRAUD!!   A Charlatan and now a PROVEN FRAUD!!

 If you don't think my drivers work any more, and you want Jim Hall to
 remove all my work from BASE and IBiblio, they WHY ARE YOU STILL USING
 XMGR, UIDE, and RDISK??

 Because you are a DISGRACE to all humanity, you lousy FRAUD!!

 STOP using my drivers, you stinking FRAUD!!   Stop using them NOW, and
 NEVER use them again, you wretched FRAUD!!

 And Put your money where your [FOUL] MOUTH is and get Jim Hall to DELETE
 my drivers from IBiblio, EVERY LAST ONE since 2004, you despicable FRAUD!!

 STOP using my drivers and GET RID OF THEM ALL from Ibiblio NOW, you
 stinking
 FRAUD!!   No matter if you have Jim Hall do it, or do it somehow yourself,
 just DO IT NOW, you miserable FRAUD!!

 You have made a MOCKERY of this forum by breaking EVERY ONE of its Rules
 For Posting, which I now regard as either a JOKE or a bald-faced SHAM!!
 I DO NOT want my work associated with FreeDOS any more, CERTAINLY NOT for
 use by a PIG and a CRACKER like YOU, you two-bit FRAUD!!

 So DO IT NOW!!   STOP using my drivers, ALL OF THEM, if you think they
 no-longer work!!   And Get Them All OFF IBIBLIO too!!   They were NOT
 written to be used by a pitiful CRETIN like YOU, you FRAUD

 --
 Don't Limit Your Business. Reach for the Cloud.
 GigeNET's Cloud Solutions provide you with the tools and support that
 you need to offload your IT needs and focus on growing your business.
 Configured For All Businesses. Start Your Cloud Today.
 https://www.gigenetcloud.com/
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] For what architectures is FreeDOS designed?

[Alain Mouette]

Em 24-11-2014 22:38, Ralf Quint escreveu:
 In theory, you could run 8-bit object code if you had an NEC V20 or V30
 CPU which is 8086 compatible while also featuring an 8080 emulation mode.
 NEC also made a special version of their V50 CPU just for the PC-88VA
 which can execute Z80 code as well.

 But in neither case, you are going to be running FreeDOS (or any DOS) in
 those modes...
I remeber that there is a very good CP/M simulator for DOS, I used it a 
lot when migranting from CP/M to PC-DOS...
that would allow to run very old 8 bit programs...

Alain


--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] For what architectures is FreeDOS designed?

[Alain Mouette]

Em 24-11-2014 22:38, Ralf Quint escreveu:
 In theory, you could run 8-bit object code if you had an NEC V20 or V30
 CPU which is 8086 compatible while also featuring an 8080 emulation mode.
 NEC also made a special version of their V50 CPU just for the PC-88VA
 which can execute Z80 code as well.

 But in neither case, you are going to be running FreeDOS (or any DOS) in
 those modes...
 I remeber that there is a very good CP/M simulator for DOS, I used it a
 lot when migranting from CP/M to PC-DOS...
 that would allow to run very old 8 bit programs...
BTW, it did't use the V20 chip, I used it before the V20 existed and 
much later on a 386. So it would run really fas on a modern computer


Alain


--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Wherefore art thou, packet driver?

[Alain Mouette]

Is there a tutorial for using NDIS2 drives with freedos? I usualy use 
www.netbootdisk.com but it would be nice to be able to do it manualy

Alain

Em 22-08-2014 03:17, Ulrich Hansen escreveu:
 Don't forget you can use ndis (LAN manager) and odi (Novell netware) 
 drivers as packet drivers in DOS. With some additional tools.

 Am 22.08.2014 um 07:53 schrieb Louis Santillan lpsan...@gmail.com:

 There's 100 PCI drivers here
 (http://www.classiccmp.org/dunfield/dos/pktdrv.zip).

 On Thu, Aug 21, 2014 at 9:23 PM, Rugxulo rugx...@gmail.com wrote:
 Hi,

 N.B. The OP's subject line is too vague. You'd probably get more help
 with a more specific description of the problem. Some people don't
 have time to pore over all the various threads.

 Anyways, please keep reading below, I'll (weakly) respond inline.

 On Mon, Aug 18, 2014 at 3:50 AM, Mateusz Viste mate...@viste.fr wrote:

 The PCNTPK driver is meant to be used only on computers with the AMD
 PC-NET network card (which is also emulated by VirtualBox).

 You most probably have a different network card - what you need is to
 know exactly what network card you have (vendor/model), and then look
 for a matching packet driver. A packet driver is what makes it
 possible for TCP stacks under DOS to use networking.

 Mateusz
 Georg Potthast has some packet drivers mirrored on his website:

 http://www.georgpotthast.de/sioux/packet.htm

 He also has NICSCAN, which maybe will help ease your search:

 http://www.georgpotthast.de/sioux/pktdrv/nicscan.zip

 But don't get your hopes up too high, a lot of (wired) network cards
 these days probably aren't well-supported on DOS, if at all. Blame
 your manufacturer directly (write them an email, offer to pay them,
 etc).

 Keep reading below.

 On 08/18/2014 10:44 AM, Thsise Faek wrote:

 I just installed freedos on a computer (not VirtualBox, real install)
 and ive been trying to set up the network.
 What kind of computer? What network card? What does Linux detect it
 has? dmesg | grep eth0?

 Just like in the instructions, I went into the autoexec.bat, and removed
 the REM from REM LH PCNTPK INT=0x60. It gave me this error during
 startup (PCNTPK-DOS-015: Device not found.)

 Removing the LH and leaving only PCNTPK INT=0x60 gave me the same error
 during startup. Because of this I cant use any network functions.
 How do I fix this?
 Well, the obvious answer (that you seem to avoid, why?) is to use an
 emulator / hypervisor like VirtualBox. It works there, at least. I
 know that's not necessarily ideal, but it's better than nothing.

 Some of the more obvious packet drivers are in the set from Crynwr:

 http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/net/crynwr.zip

 However, once again, you have to know exactly what you want and how to
 set it up. I don't remember the details on searching for specific PCI
 IDs, so you'll have to hope that someone like Eric Auer or Bernd Blauw
 chime in here. Presumably you use something like PCISLEEP or BERNDPCI:

 1). 
 http://ericauer.cosmodata.virtuaserver.com.br/soft/pcisleep-2005mar12.zip
 2). http://ericauer.cosmodata.virtuaserver.com.br/soft/specials/berndpci.zip

 Wasn't there some database of all the various PCI devices? Was it some
 website? Anyone remember? (Probably Eric does.) Hmmm, maybe this is
 it:

 http://pciids.sourceforge.net/

 Hope some of this helps! Please report back to us with your results
 (successes, failures).

 --
 Slashdot TV.
 Video for Nerds.  Stuff that matters.
 http://tv.slashdot.org/
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user
 --
 Slashdot TV.
 Video for Nerds.  Stuff that matters.
 http://tv.slashdot.org/
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user

 --
 Slashdot TV.
 Video for Nerds.  Stuff that matters.
 http://tv.slashdot.org/
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Wherefore art thou, packet driver?

[Alain Mouette]

Thanks, I will test

:)
Alain

Em 22-08-2014 11:22, Ulrich escreveu:
 Hi Alain

 Am 22.08.2014 um 14:28 schrieb Alain Mouette ala...@pobox.com:

 Is there a tutorial for using NDIS2 drives with freedos? I usualy use
 www.netbootdisk.com but it would be nice to be able to do it manualy
 I once wrote a (maybe a biit lengthy) tutorial at:

 http://www.freedos.org/wiki/index.php/Networking_FreeDOS_-_NDIS_driver_installation

 In short (ten steps):

 1. Find the .dos driver for your card. Among your drivers installation files, 
 look for a directory called NDIS2.
 2. Get Microsofts free MS Client, f.i. from 
 http://www.ibiblio.org/pub/micro/pc-stuff/freedos/ftp.gcfl.net/pub/freedos/ms-clients/msclient/DSK3-1.EXE
 3. move it to a temporary folder and run dsk3-1.exe
 4. expand -r protman.do_
 5. expand -r protman.ex_
 6. Move protman.dos, protman.exe and netbind.com to a permanent directory 
 f.i. C:\NET
 7. Get dis_pkt.dos from 
 http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/net/dis_pkt11.zip and 
 copy it to C:\NET
 8. Make a file C:\NET\PROTOCOL.INI with the content

 [protman]
 DriverName=PROTMAN$

 [EL3C574]
 DriverName=EL3C574$

 [PKTDRV]
 drivername=PKTDRV$
 bindings=EL3C574
 intvec=0x60
 chainvec=0x68

 and replace EL3C574 with the name of your .dos-driver without the .dos 
 ending. Sometimes your .dos-driver comes with a .txt file that contains the 
 exact info.

 9. Add the following lines to FDCONFIG.SYS:

 DEVICEHIGH=C:\NET\PROTMAN.DOS /I:C:\NET
 DEVICEHIGH=C:\NET\EL3C574.DOS
 DEVICEHIGH=C:\NET\DIS_PKT.DOS

 10. Add the following line to AUTOEXEC.BAT:

 C:\NET\NETBIND.COM

 That's it. Please correct me, if anything is wrong or just different. It's 
 been some time.
 Ulrich

 Em 22-08-2014 03:17, Ulrich Hansen escreveu:
 Don't forget you can use ndis (LAN manager) and odi (Novell netware) 
 drivers as packet drivers in DOS. With some additional tools.

 Am 22.08.2014 um 07:53 schrieb Louis Santillan lpsan...@gmail.com:

 There's 100 PCI drivers here
 (http://www.classiccmp.org/dunfield/dos/pktdrv.zip).

 On Thu, Aug 21, 2014 at 9:23 PM, Rugxulo rugx...@gmail.com wrote:
 Hi,

 N.B. The OP's subject line is too vague. You'd probably get more help
 with a more specific description of the problem. Some people don't
 have time to pore over all the various threads.

 Anyways, please keep reading below, I'll (weakly) respond inline.

 On Mon, Aug 18, 2014 at 3:50 AM, Mateusz Viste mate...@viste.fr wrote:

 The PCNTPK driver is meant to be used only on computers with the AMD
 PC-NET network card (which is also emulated by VirtualBox).

 You most probably have a different network card - what you need is to
 know exactly what network card you have (vendor/model), and then look
 for a matching packet driver. A packet driver is what makes it
 possible for TCP stacks under DOS to use networking.

 Mateusz
 Georg Potthast has some packet drivers mirrored on his website:

 http://www.georgpotthast.de/sioux/packet.htm

 He also has NICSCAN, which maybe will help ease your search:

 http://www.georgpotthast.de/sioux/pktdrv/nicscan.zip

 But don't get your hopes up too high, a lot of (wired) network cards
 these days probably aren't well-supported on DOS, if at all. Blame
 your manufacturer directly (write them an email, offer to pay them,
 etc).

 Keep reading below.

 On 08/18/2014 10:44 AM, Thsise Faek wrote:

 I just installed freedos on a computer (not VirtualBox, real install)
 and ive been trying to set up the network.
 What kind of computer? What network card? What does Linux detect it
 has? dmesg | grep eth0?

 Just like in the instructions, I went into the autoexec.bat, and removed
 the REM from REM LH PCNTPK INT=0x60. It gave me this error during
 startup (PCNTPK-DOS-015: Device not found.)

 Removing the LH and leaving only PCNTPK INT=0x60 gave me the same error
 during startup. Because of this I cant use any network functions.
 How do I fix this?
 Well, the obvious answer (that you seem to avoid, why?) is to use an
 emulator / hypervisor like VirtualBox. It works there, at least. I
 know that's not necessarily ideal, but it's better than nothing.

 Some of the more obvious packet drivers are in the set from Crynwr:

 http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/net/crynwr.zip

 However, once again, you have to know exactly what you want and how to
 set it up. I don't remember the details on searching for specific PCI
 IDs, so you'll have to hope that someone like Eric Auer or Bernd Blauw
 chime in here. Presumably you use something like PCISLEEP or BERNDPCI:

 1). 
 http://ericauer.cosmodata.virtuaserver.com.br/soft/pcisleep-2005mar12.zip
 2). 
 http://ericauer.cosmodata.virtuaserver.com.br/soft/specials/berndpci.zip

 Wasn't there some database of all the various PCI devices? Was it some
 website? Anyone remember? (Probably Eric does.) Hmmm, maybe this is
 it:

 http://pciids.sourceforge.net/

 Hope some of this helps! Please report back to us with your

Re: [Freedos-user] CDRom Was Re: Dictionnary program not working

[Alain Mouette]

Under VirtualBox you can install FreeDOS and CDROM emulation runs 
perfectly (emulated by VirtualBox, not by FreeDOS)

Alain

Em 28-12-2013 13:36, Shérab escreveu:
 Hi,

 Still trying to use that old dictionary program for DOS.
 So the dictionary runs on  CD -ROM for which I have a .iso image.

 So far I mounted the .ISO file on, say, /cdrom/ and then created a
 symbolic link called e under ~/.dosemu/drives pointing to /cdrom.

 So of course, that way, the CD-ROM is not really emulated.

 Is there a way to access the .iso file from within dosemu / freedos
 through something that would emulate a CD-ROM driver better ?

 Thanks,
 Shérab.

 --
 Rapidly troubleshoot problems before they affect your business. Most IT
 organizations don't have a clear picture of how application performance
 affects their revenue. With AppDynamics, you get 100% visibility into your
 Java,.NET,  PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
 http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET,  PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Any interest in 486, 586, 686 kernels?

[Alain Mouette]

There is one thint that I am aware of, and I use in my OpenWatcom 
programs: In a 586 execution will be faster if the instructions are 
rearanged, but still using only 386 instructions...

Alain

Em 03-05-2013 03:48, Eric Auer escreveu:

 Hoi Louis,

 please explain the hack / patch: Is the only thing that
 you changed that the kernel is compiled for those CPUs?
 Are there actually any differences between them? I can
 imagine that OpenWatcom makes 186 and 286 the same and
 everything above 386 the same. Unless the kernel would
 contain heavy mathematical processing for which it is
 obvious that above-386 optimizes better ;-) You could
 tell the compiler to produce Assembly output (instead
 of binary) and compare the text. Or you could use some
 debug, disassembler (ndisasm?) or hex editor to compare
 before you UPX things, but of course that is more work.

 Thanks for comparing :-) Maybe this is more a topic for
 the kernel list. Note that if a few bytes are really
 only 10 or so, all this is probably more an academic
 exercise. Things get more exciting once you can save at
 least a cluster of disk space or a paragraph of RAM :-)

 Regards, Eric

 I hacked the 2041 kernel batch and make files included on the FD 1.1 iso to
 allow the kernel to be built by OpenWatcom as 8086, 186, 286, 386, 486,
 586, or 686.  The resulting 686 kernel boots fine in VirtualBox 4.2.12 in
 OSX 10.8.3 on my 2012 Mac Book Air 13 4GB.  The resulting kernel is a few
 bytes smaller compressed by upx than kernel installed by the FD 1.1 iso.
   I'm going to continue testing.  No source changes were made.  Not sure how
 the changes affect the nasm built files.




 --
 Get 100% visibility into Java/.NET code with AppDynamics Lite
 It's a free troubleshooting tool designed for production
 Get down to code-level detail for bottlenecks, with2% overhead.
 Download for free and get started troubleshooting in minutes.
 http://p.sf.net/sfu/appdyn_d2d_ap2
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with 2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] hexed12a.zip

[Alain Mouette]

Em 22-02-2013 01:56, Rugxulo escreveu:

 IIRC, in C, only globals and static are guaranteed to be zeroed. Auto
 vars on the stack are not, nor is heap returned from malloc.

NO variable is guarenteed to be seroed, just most compilers do. If you 
want it zeroed, just initialize and it will be dealt efficiently for 
static or local variables.

Alain

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] hexed12a.zip

[Alain Mouette]

I have seen otherwise...
Specialy some old compilers or embedded.

Alain - it is not because I am paranoiac that noone is chasing me


Em 22-02-2013 10:13, Mateusz Viste escreveu:
 On 02/22/2013 01:32 PM, Alain Mouette wrote:
 NO variable is guarenteed to be seroed, just most compilers do. If you
 want it zeroed, just initialize and it will be dealt efficiently for
 static or local variables.

 I have to disagree, since the standard says otherwise.

 Extract from ISO/IEC 9899:1990, chapter 6.5.7:

 If an object that has static storage duration is not initialized
 explicitly, it is initialized implicitly as if every member that has
 arithmetic type were assigned 0 and every member that has pointer type
 were assigned a null pointer constant.

 cheers,
 Mateusz

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] if not exist?

[Alain Mouette]

Yes, that trick works since very old MS-DOS versions
;-)

Alain

Em 14-02-2013 22:30, Eric Auer escreveu:

 Hi!

 If that doesn't work then a exist.c should be made that friend 1 errorlevel
 if so let me know and I make it

 You misunderstood, IF EXIST does exists but has to
 be used in a special way for directory checks ;-)

 Is there something like this in FD?

 Yes of course: Type if /? to see how it should work.

 IF NOT EXIST X:\ZZZ MD X:\ZZZ

 Everything in front of the MD is ignored, and there is an error if
 X:\ZZZ does exist.

 I made some experiments: IF EXIST and IF NOT EXIST do
 what they should do for files, but apparently cannot
 check existence of directories. The trick, which also
 should work with MS DOS, is to use a CHARACTER DEVICE
 because those exist in all directories by definition:

 IF NOT EXIST X:\ZZZ\NUL MKDIR X:\ZZZ

 That does what you wanted to do :-)

 Eric

--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] if not exist?

[Alain Mouette]

try this:

IF NOT EXIST X:\ZZZ\NUL MKDIR X:\ZZZ

Alain

Em 14-02-2013 22:15, Ray Davison escreveu:
 Is there something like this in FD?

 IF NOT EXIST X:\ZZZ MD X:\ZZZ

 Everything in front of the MD is ignored, and there is an error if
 X:\ZZZ does exist.

 TY
 Ray

 --
 Free Next-Gen Firewall Hardware Offer
 Buy your Sophos next-gen firewall before the end March 2013
 and get the hardware for free! Learn more.
 http://p.sf.net/sfu/sophos-d2d-feb
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] (no subject)

[Alain Mouette]

I can do it this way:

1) configure VMware as Bridge PCnet NIC
2) use the drivers from netbootdisk.com for the driver inside VMware. 
the guy there is making an excelent job of collecting new drivers

It just works...

Alain

Em 19-09-2012 19:53, George Brooks escreveu:
 I'm experimenting with FreeDOS in an effort to find a solution for
 access to a legacy DOS application. The environment is an HP laptop
 (6730s) running Win7 32-bit, VMWare Player v5 and FreeDOS 1.1. All
 proceeds smoothly until I try to gain access to a printer share via
 MSClient. (This is the only way I can see to get the application to
 print.) The challenge occurs when attempting to load the driver for the
 laptop's ethernet card - a Marvell Yukon. The driver is named yuknd.dos.

 I've tried a number of configurations based on postings found on the
 web. In an effort to narrow the problem down I entered the following
 into fdconfig.sys:

 device=c:\net\yuknd.dos

 When stepping thru boot, this line results in the error message
 Controller not found. What means, if any, are available to get over
 this? (The laptop also has wireless, but I suspect that is even more
 highly problematic.)

 Many thanks for sharing your wisdom.

 George

 ps: my apologies if my lack of understanding of lists has caused this to
 be a duplicate posting.


 --
 Live Security Virtual Conference
 Exclusive live event will cover all the ways today's security and
 threat landscape has changed and how IT managers can respond. Discussions
 will include endpoint security, mobile security and the latest in malware
 threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/



 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Big bootable disk for CD

[Alain Mouette]

The eltorito.sys is no use for FreeDOS, it is only for booting from the CD.

To access the CD when booted from the CD, you need to load a regular CD 
driver like UIDE. The problem is that it works with only a fraction of 
existing hardware end is also picky about memory driver. I believe that 
there are conflicts with memdisk loader...

You can see in my CD that I have a first green menu screen to select 
various memory manager and Driver options, but even with all those 
optins it works not everywhere...

That is why I made a bigger image and put all I want into it, this way 
it works *always* :)

Alain

Em 20-01-2012 11:39, Bob Cochran escreveu:
 Hi Eric,

 Thank you very much for your help with this, and I am going to try your
 method this weekend also. I want to learn both your method and the
 isolinux method. I still need to get that motherboard BIOS update done,
 which is my immediate goal. I also need to be able to update the
 firmware for an LSISAS1068 chip that is on a PCI Express adapter card, I
 have 3 of these cards to update. Now you see where my motivation comes
 from. Several times a year at least I have a need to learn and
 understand DOS. That is my longer term goal.

 I will buy some USB flash drives and play with them using the advice you
 give me below.

 One question. When you say that I must copy config.sys, and autoexec.bat
 you also mean I must edit these to load the drivers my system needs
 after the copying, right? For example I will need to edit the copied
 config.sys or autoexec.bat to load eltorito.sys and thereby have access
 to both the CD/DVD drive and USB devices? Since my keyboard is USB based
 this is an important question.

 Thanks

 Bob

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Big bootable disk for CD

[Alain Mouette]

The MKISOFS is the one that brings it all toghether. The freeDOS image 
is passed as an argument to be loaded in memory and then executed.

Anyway, this was a good feedback, I am planning a FreeDOS release withou 
my programs, and I will make that more clear and more specific, I gesse 
that the scrip that puts it all toghether may help.

Alain

Em 19-01-2012 01:47, Bob Cochran escreveu:
 Hi Alain, Bernd, Eric:

 I followed the instructions below from Alain, using my Fedora 14 (Linux)
 box. I didn't have 100% success but I am much closer! I created an image
 file in the manner described below. I wondered where to find command.com
 and kernel.sys...so I downloaded the FreeDOS iso for 1.1 and found those
 files in the one disk folder. I copied them to my image and then
 copied over my BIOS update files which are packaged in a directory.
 However I ran into trouble at Step 8: specifically, I couldn't figure
 out how to independently generate an isolinux folder or where to find
 isolinux to start with. So I copied over the ISOLINUX folder I found
 inside the FreeDOS 1.1 iso, and did some experimenting with the
 arguments to mkisofs. This got me a nice small iso image which I burned
 to CD.

 I then booted from this cd and got...the FreeDOS 1.1 installation screen
 in all its glory!

 In Alain's recipe below, it is not obvious to me how the FreeDOS.img
 file is connected to isolinux. I played with the tab key to see the boot
 arguments for the CD I made, and I get the impression that FreeDOS.img
 would be treated as the initrd= argument to isolinux. Am I right about
 that? In other words, isolinux takes the FreeDOS.img file, loads it into
 memory, and then passes control to it?

 Clearly, I need to read up more about using isolinux. I am very grateful
 to all of you for your help and advice. I'm making progress!

 Bob


 On 1/17/12 2:27 PM, Alain Mouette wrote:
 I have done this some time ago, it may help. It is for CD, but it would
 be nice to convert it to SD-card...

 Alain

 Em 15-06-2011 11:51, Alain Mouette escreveu:
 How can I make a big (6Mb) bootable image to use in the CD?
 This is the only part of the CD that I can read on *any* machine, I am
 using isolinux)
 With lots of help fom Eric Auer, I managed to make a bootable image with
 FreeDOS. Here is how I did it:

 1) Program needed: NASM, which I got from Debian
 $ sudo apt-get install nasm

 2) program from Eric for the boot sector:
 http://ericauer.cosmodata.virtuaserver.com.br/soft/specials/sys-freedos-linux.zip
 create a directory ./sys-freedos-linux and expand it there

 3) create file of the right size. 5760k was ok for me, there is some
 magic in the size and not everything will be ok. (more studies needed)
 $ dd if=/dev/zero of=FreeDOS.img count=11520
 11520+0 records in
 11520+0 records out
 5898240 bytes (5.9 MB) copied, 0.408512 s, 14.4 MB/s

 4) Prepare it with a FAT file system
 $ sudo mkdosfs -v FreeDOS.img
 mkdosfs 3.0.1 (23 Nov 2008)
 FreeDOS.img has 64 heads and 32 sectors per track,
 logical sector size is 512,
 using 0xf8 media descriptor, with 11520 sectors;
 file system has 2 12-bit FATs and 4 sectors per cluster.
 FAT size is 9 sectors, and provides 2867 clusters.
 Root directory contains 512 slots.
 Volume ID is 0cbb7ca7, no volume label.

 5) compile and write a suitable boot sector. This is a smart script by
 Eric Auer that configures it with the appropiate parameters
 $ ./sys-freedos-linux/sys-freedos.pl --disk=FreeDOS.img
 DOS boot sector for FreeDOS.img will be created by:
nasm -o /dev/stdout -dISFAT12
 ./sys-freedos-linux/bootsecs/boot.asm
 Using FAT12. Partn offset 0, CHS *x64x32  Drive 0, (0x0, 0x29),
 SerNo CBB-7CA7, Strings '   ',  'FAT12   '.
 Boot sector successfully updated.

 6) mount it in a directory
 $ mkdir bootimg
 $ sudo mount -v -o loop,uid=you,gid=you FreeDOS.img bootimg

 7) copy into it KERNEL.SYS, COMMAND.COM and all other files

 8) use it just the same way then the image made from a floppy, memdisk
 will recognize it. I used isolinux, here is how I created the iso:
 $ mkisofs  -R -v -A FreeDOS big boot CD -V FreeDOS-V1.x \
-b isolinux/isolinux.bin -c isolinux/boot.cat \
-no-emul-boot -boot-load-size 4 -boot-info-table  \
-o /mnt/dados/Segurver/FreeDOS-V1.x.iso   \
/mnt/dados/CDROM

 Alain

 --
 Keep Your Developer Skills Current with LearnDevNow!
 The most comprehensive online learning library for Microsoft developers
 is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
 Metro Style Apps, more. Free future releases when you subscribe now!
 http://p.sf.net/sfu/learndevnow-d2d
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Big bootable disk for CD

[Alain Mouette]

I have done this some time ago, it may help. It is for CD, but it would 
be nice to convert it to SD-card...

Alain

Em 15-06-2011 11:51, Alain Mouette escreveu:

 How can I make a big (6Mb) bootable image to use in the CD?
 This is the only part of the CD that I can read on *any* machine, I am
 using isolinux)

With lots of help fom Eric Auer, I managed to make a bootable image with 
FreeDOS. Here is how I did it:

1) Program needed: NASM, which I got from Debian
$ sudo apt-get install nasm

2) program from Eric for the boot sector:
http://ericauer.cosmodata.virtuaserver.com.br/soft/specials/sys-freedos-linux.zip
create a directory ./sys-freedos-linux and expand it there

3) create file of the right size. 5760k was ok for me, there is some 
magic in the size and not everything will be ok. (more studies needed)
$ dd if=/dev/zero of=FreeDOS.img count=11520
11520+0 records in
11520+0 records out
5898240 bytes (5.9 MB) copied, 0.408512 s, 14.4 MB/s

4) Prepare it with a FAT file system
$ sudo mkdosfs -v FreeDOS.img
mkdosfs 3.0.1 (23 Nov 2008)
FreeDOS.img has 64 heads and 32 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 11520 sectors;
file system has 2 12-bit FATs and 4 sectors per cluster.
FAT size is 9 sectors, and provides 2867 clusters.
Root directory contains 512 slots.
Volume ID is 0cbb7ca7, no volume label.

5) compile and write a suitable boot sector. This is a smart script by 
Eric Auer that configures it with the appropiate parameters
$ ./sys-freedos-linux/sys-freedos.pl --disk=FreeDOS.img
DOS boot sector for FreeDOS.img will be created by:
  nasm -o /dev/stdout -dISFAT12 
./sys-freedos-linux/bootsecs/boot.asm
Using FAT12. Partn offset 0, CHS *x64x32  Drive 0, (0x0, 0x29),
SerNo CBB-7CA7, Strings '   ',  'FAT12   '.
Boot sector successfully updated.

6) mount it in a directory
$ mkdir bootimg
$ sudo mount -v -o loop,uid=you,gid=you FreeDOS.img bootimg

7) copy into it KERNEL.SYS, COMMAND.COM and all other files

8) use it just the same way then the image made from a floppy, memdisk 
will recognize it. I used isolinux, here is how I created the iso:
$ mkisofs  -R -v -A FreeDOS big boot CD -V FreeDOS-V1.x \
  -b isolinux/isolinux.bin -c isolinux/boot.cat \
  -no-emul-boot -boot-load-size 4 -boot-info-table  \
  -o /mnt/dados/Segurver/FreeDOS-V1.x.iso   \
  /mnt/dados/CDROM

Alain

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Bootable FreeDOS CD or USB Drive for Flashing Motherboard BIOS

[Alain Mouette]

Have you seen my mesage from *today* 5:27pm (gmt-2)

Alain

Em 17-01-2012 21:04, Bob Cochran escreveu:
 Thanks everyone for all the responses. I guess there is not a how-to for
 creating a bootable FreeDOS CD? That is, it takes fiddling and
 experimentation and a successful method has not been posted to the
 FreeDOS wiki? The point of greatest interest is what files are needed on
 the CD, exactly (including all their dependencies...so if command.com
 has dependencies, I'd need to include those.) Also how exactly to make
 the CD bootable in a FreeDOS acceptable way.

 I really would like to be able to create such a CD and get the BIOS up
 to date.

 I deeply appreciate advice on how to really do it. I will fiddle with
 Alain's suggestion, I did something close to that a few months ago in a
 very similar effort but evidently missed some important step.

 Bob



 On 1/17/12 1:49 PM, Bernd Blaauw wrote:
 Op 17-1-2012 7:15, Rugxulo schreef:

 You can convert an existing bootable DOS floppy image into a .iso for
 burning to CD with the following (DOS) freeware tool:

 http://www.terabyteunlimited.com/downloads/mkbiso.zip
 Does this work for any size floppy image or only 1.44MB?

 In principle BIOS flashing can be done from a freely distributable
 floppy disk/image, containing KERNEL.SYS, COMMAND.COM and FLASHROM.EXE
 (though the flash program by BIOS maker or motherboard manufacturer
 might be more reliable).

 --
 Keep Your Developer Skills Current with LearnDevNow!
 The most comprehensive online learning library for Microsoft developers
 is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
 Metro Style Apps, more. Free future releases when you subscribe now!
 http://p.sf.net/sfu/learndevnow-d2d
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


 --
 Keep Your Developer Skills Current with LearnDevNow!
 The most comprehensive online learning library for Microsoft developers
 is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
 Metro Style Apps, more. Free future releases when you subscribe now!
 http://p.sf.net/sfu/learndevnow-d2d
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Big bootable disk for CD

[Alain Mouette]

Ah, ok, next message :)

Well, you can use mine :)

1) Grab this: 
http://suporte.cosmodata.com.br/downloads/moni/CosmoData-M15020.iso
2) don't touch the COSMODAT dir... (no big deal, there is a password on 
sensitive files)
3) the FreeDOS/Disk is a perfect image of the boot disk, the 
CosmoDOS.img is the booting image.

This iso works, you can burn it and test :)

It is a version a few months older then FreeDOS 1.1. It is full GPL, all 
sources are included :)

Alain

Em 17-01-2012 21:07, Bob Cochran escreveu:
 Alain,

 I would like to try your method. I did something like this a few months
 ago but evidently missed a step since my CD would not really boot. This
 was to enable flashing a BIOS update on a motherboard.

 Can you tell me the names of all the files needed in your step 7?
 Perhaps I missed a file.

 Thanks so much!

 Bob Cochran



 On 1/17/12 2:27 PM, Alain Mouette wrote:
 I have done this some time ago, it may help. It is for CD, but it would
 be nice to convert it to SD-card...

 Alain

 Em 15-06-2011 11:51, Alain Mouette escreveu:
 How can I make a big (6Mb) bootable image to use in the CD?
 This is the only part of the CD that I can read on *any* machine, I am
 using isolinux)
 With lots of help fom Eric Auer, I managed to make a bootable image with
 FreeDOS. Here is how I did it:

 1) Program needed: NASM, which I got from Debian
 $ sudo apt-get install nasm

 2) program from Eric for the boot sector:
 http://ericauer.cosmodata.virtuaserver.com.br/soft/specials/sys-freedos-linux.zip
 create a directory ./sys-freedos-linux and expand it there

 3) create file of the right size. 5760k was ok for me, there is some
 magic in the size and not everything will be ok. (more studies needed)
 $ dd if=/dev/zero of=FreeDOS.img count=11520
 11520+0 records in
 11520+0 records out
 5898240 bytes (5.9 MB) copied, 0.408512 s, 14.4 MB/s

 4) Prepare it with a FAT file system
 $ sudo mkdosfs -v FreeDOS.img
 mkdosfs 3.0.1 (23 Nov 2008)
 FreeDOS.img has 64 heads and 32 sectors per track,
 logical sector size is 512,
 using 0xf8 media descriptor, with 11520 sectors;
 file system has 2 12-bit FATs and 4 sectors per cluster.
 FAT size is 9 sectors, and provides 2867 clusters.
 Root directory contains 512 slots.
 Volume ID is 0cbb7ca7, no volume label.

 5) compile and write a suitable boot sector. This is a smart script by
 Eric Auer that configures it with the appropiate parameters
 $ ./sys-freedos-linux/sys-freedos.pl --disk=FreeDOS.img
 DOS boot sector for FreeDOS.img will be created by:
 nasm -o /dev/stdout -dISFAT12
 ./sys-freedos-linux/bootsecs/boot.asm
 Using FAT12. Partn offset 0, CHS *x64x32  Drive 0, (0x0, 0x29),
 SerNo CBB-7CA7, Strings '   ',  'FAT12   '.
 Boot sector successfully updated.

 6) mount it in a directory
 $ mkdir bootimg
 $ sudo mount -v -o loop,uid=you,gid=you FreeDOS.img bootimg

 7) copy into it KERNEL.SYS, COMMAND.COM and all other files

 8) use it just the same way then the image made from a floppy, memdisk
 will recognize it. I used isolinux, here is how I created the iso:
 $ mkisofs  -R -v -A FreeDOS big boot CD -V FreeDOS-V1.x \
 -b isolinux/isolinux.bin -c isolinux/boot.cat \
 -no-emul-boot -boot-load-size 4 -boot-info-table  \
 -o /mnt/dados/Segurver/FreeDOS-V1.x.iso   \
 /mnt/dados/CDROM

 Alain

 --
 Keep Your Developer Skills Current with LearnDevNow!
 The most comprehensive online learning library for Microsoft developers
 is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
 Metro Style Apps, more. Free future releases when you subscribe now!
 http://p.sf.net/sfu/learndevnow-d2d
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


 --
 Keep Your Developer Skills Current with LearnDevNow!
 The most comprehensive online learning library for Microsoft developers
 is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
 Metro Style Apps, more. Free future releases when you subscribe now!
 http://p.sf.net/sfu/learndevnow-d2d
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net

Re: [Freedos-user] Bootable FreeDOS CD or USB Drive for Flashing Motherboard BIOS

[Alain Mouette]

Well, what I want is to make a bootable SD-card with that same image... 
It is a standard isolinux image.

Has anyone made that?

Thanks,
Alain

Em 17-01-2012 22:49, Rugxulo escreveu:
 Hi,

 On Tue, Jan 17, 2012 at 12:49 PM, Bernd Blaauwbbla...@home.nl  wrote:
 Op 17-1-2012 7:15, Rugxulo schreef:

 You can convert an existing bootable DOS floppy image into a .iso for
 burning to CD with the following (DOS) freeware tool:

 http://www.terabyteunlimited.com/downloads/mkbiso.zip

 Does this work for any size floppy image or only 1.44MB?

 I don't know, but I'm assuming 1.44 MB is what most people use these
 days, so it's probably moot (esp. since that's all I've tried with the
 tool).

 There's also MBOOTCD, but I don't think I ever tried it.

 http://www.fysnet.net/mtools.htm

 In principle BIOS flashing can be done from a freely distributable
 floppy disk/image, containing KERNEL.SYS, COMMAND.COM and FLASHROM.EXE
 (though the flash program by BIOS maker or motherboard manufacturer
 might be more reliable).

 He didn't specify any more details, so I don't know what he wants to
 put on there or what other requirements he has. Looks like he might
 try Alain's solution instead. (I would almost suggest some of my own
 floppy images, but they're too old and quirky.)

 Either way, it shouldn't be too hard for him to figure it out. He can
 always come ask again for further help if needed.

 --
 Keep Your Developer Skills Current with LearnDevNow!
 The most comprehensive online learning library for Microsoft developers
 is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
 Metro Style Apps, more. Free future releases when you subscribe now!
 http://p.sf.net/sfu/learndevnow-d2d
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] 4th-Grade English.

[Alain Mouette]

Sorry for my english...
My native tong is Portuguese
My second one is French
Leaving English as the third one...

Alain

Em 21-10-2011 17:07, Jack escreveu:

 It is VERY TIRESOME, having to respond to posts on this board with
 I DID NOT say ... or I DO NOT agree ..., when one's REAL words
 are either misunderstood or often TWISTED for some other agenda!

 Many such replies would cause their writers to FAIL, QUICKLY, in
 almost all U.S. High-School Debate classes, from NOT speaking to
 the POINT of whatever the original post was!

 Is it REALLY true, that (A) using 4th-grade English [age 9 level],
 (B) proof-reading SEVERAL times before making posts, and (C) doing
 all possible to be CLEAR, are now NOT-ENOUGH on boards like this??

 Or does the U.S. Slept Thru High-School DISEASE [as so many here
 took GREAT SPORT in achieving!] now afflict not just OUR last 2 or
 3 whole generations of total idiots, but EVERYBODY world-wide??

 COME ON, People!!   DO NOT twist posts to suit your OWN agendas!
 PAY ATTENTION to the POINT of what people try to post, both here
 and elsewhere!!   And DO realize you just might have to WAKE UP!
   from such teenage slumber, and USE YOUR BRAINS, now-and-then, to
 UNDERSTAND what is obviously technical data, not just Tee-Hee!
 babbling from Slept Thru BRATS!!

 Sorry, but THERE IT IS!!, as the British might say!


 --
 The demand for IT networking professionals continues to grow, and the
 demand for specialized networking skills is growing even more rapidly.
 Take a complimentary Learning@Cisco Self-Assessment and learn
 about Cisco certifications, training, and career opportunities.
 http://p.sf.net/sfu/cisco-dev2dev
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Undeserved Comment Re: EMM/JEMM, A20, Etc.

[Alain Mouette]

Em 20-10-2011 17:22, Jack escreveu:

 In creating JEMM386, Japheth did not merely improve things!   He
 made FD-EMM386 RUN PROPERLY!

Finaly you agree with me! The Michel Devore's emm386 was tested very 
very much by the members of FreeDOS and Michel fixed ALL issues.

Michel started with somethin, I don't remember what. But he grew so much 
disgusted with these fights that when the last issue got fixed, he 
*disapeared*

Alain

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s

[Alain Mouette]

Em 18-10-2011 22:34, Rugxulo escreveu:
 On Tue, Oct 18, 2011 at 5:56 PM, Alain Mouetteala...@pobox.com  wrote:
 Em 18-10-2011 20:33, Rugxulo escreveu:

 BTW, call me naive, but does that above line even give you any UMB
 space?? If not (and NOEMS), why use EMM386 at all?? (Just use XMS.)
 :-/

 Other things did not work anly with XMS, among other things emm386 puts
 the machine in protected mode, this helped something...

 Eh? That would be weird. Hmmm, now that I think about it, I think
 CWSDPMI (and/or other DPMI hosts) can't handle fragmented XMS (or hog
 it all for themselves), so shelled out apps don't have anything to
 use. Perhaps you're relying on that? In that case, yes, the 4 kb pages
 help, oddly enough. Otherwise it's not so recommended (esp. since EMS
 isn't as widely used in most modern DOS apps), as you probably
 already know, esp. regarding DPMI 1.0 extensions and CWSDPMI r7.

 And es, you are right, it gave me no UMB, which in that situation is
 just a minor annoyance. My program is 32 bits so it does not need much
 lower memory.

 DJGPP, perhaps? If OpenWatcom, you could (should) try a different
 extender (DOS/32A or Causeway).

I use OpenWatcom, with Causeway. I tried WDOSX and DOS4G but they were 
not as relyable as Causeway.

 I guess UMBPCI is out of the question??

Completly, it is hardware dependant and does not behave well on unknown 
hardware.

 I tried but could not find a range to exclude that worked and would
 leave me some UMB :(
 I find that hard to believe.

Basicaly due to lack of time. It was kind of a emergency rescue...

 But luckily FreeDOS is pretty efficient
 anyways (at least with XMS available).

:)

Alain

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Ciosco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Undeserved Comment Re: EMM/JEMM, A20, Etc.

[Alain Mouette]

Hi Jack,

First of all, let me clear one MISSUNDERSTANDING... The EMM386 that 
works ok is from Michel Devore, which was extensevely tested by the 
members of FreeDOS.

Most of your answer regards GatesCo product, sory for the confusion

About the A20 issue. I used it because I had a very stange problem: 
after a crash (with only XMS) the machine never booted again from the 
disk!!! I had to boot once from a CD and reboot adain from the disk. 
That never happend to me and is completely unheard of...

Alain

Em 18-10-2011 23:25, Jack escreveu:

 I am DISMAYED by some of the recent comments on this board
 regarding old EMM386 v.s. JEMM386/JEMMEX, the A20 line
 etc.!

 First, I use and recommend JEMM386/JEMMEX with my UIDE and
 other drivers.   I absolutely REFUSE using old EMM386 by
 Gates  Co. because it has (A) Never-fixed BUGS in its VDS
 logic, (B) FAR too much Custom Crap for wretched Win/311
 as anyone can see in its 1.8-MB of source files, and (C)
 is a 125- or 130K driver that eats FAR too much run-time
 memory!   It sucks! in short, and I view UIDE lucky to
 be able to use its OWN UltraDMA, instead of what Gates and
 all his flunkies left us with as DMA when they DROPPED
 MS-DOS in 1995!   I also want NOTHING to do with FD-EMM386
 and anyone who wonders why can read the Revision Notes for
 JEMM386, to view all of what Japheth had to do BEFORE poor
 old FD-EMM386 worked even plausibly as the new JEMM386!

 Re: JEMM386/JEMMEX failing on some systems, this is likely
 due to modern address spaces that the JEMM drivers can't
 detect.   But Japheth once told me that he CHOSE to retain
 all of EMM386's memory-detection logic, so his drivers are
 compatible with what Gates  Co.'s [never updated] TRASH
 will do!So, do you really expect EMM386 will do a much
 better job of detecting memory??   I would NOT!!   If some
 system has a problem loading JEMM386, or loading EMM386,
 its user MUST experiment with the I= and X= commands, to
 selectively include/exclude address areas, until a desired
 EMM driver DOES load successfully!   Never-was, and never-
 will-be a fully automatic PC system, and sometimes a few
 experiments loading drivers (mine included) are NECESSARY!

 Finally, it is a bit LATE in the game! to be thinking of
 new schemes for handling the A20 line.   My own XMGR has
 exactly 4 methods:

(A) IGNORE A20 if it is found enabled when XMGR loads
 i.e. the DOS kernel turns it on forever.
(B) Use keyboard-port logic if /PN was given.
(C) Use port 92h i.e. IBM PS/2 logic if /PA was given.
(D) Ask the BIOS if port 92h logic is there, if neither
/PA nor /PN is given.

 XMGR doesn't handle the usually-ignored BIOS calls, any of
 the ancient Compaq, H/P, ATT 6300 or other 1990s-vintage
 schemes to handle strange A20 logic (all of which caused
 Gates  Co. HIMEM.SYS to reach 30K!), etc.Except for a
 bug in its port 92h logic, back in 2009, nobody has ever
 complained to me that XMGR's A20 logic was inaccurate,
 inadequate, etc.!

 So, why don't we just leave current A20 handling as-is??
 For 99.44% of us, it works fine!   Any strange system on
 which it does not work usually needs TROUBLE-shooting, NOT
 yet-another new A20 handling scheme!!


 --
 All the data continuously generated in your IT infrastructure contains a
 definitive record of customers, application performance, security
 threats, fraudulent activity and more. Splunk takes this data and makes
 sense of it. Business sense. IT sense. Common sense.
 http://p.sf.net/sfu/splunk-d2d-oct
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Ciosco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s

[Alain Mouette]

= = W A R N I N G = =

Em 18-10-2011 19:20, Rugxulo escreveu:

 If you're using FreeDOS 1.0 (2006), you may want to upgrade your EMM386 to 
 JEMM.

 http://www.freedos.org/software/?prog=jemm386

 http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/emm386/jemm386/JEMM575B.zip
 http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/emm386/jemm386/JEMM575S.zip

 I suggest JEMM386 X=TEST I=TEST or similar (see its README.TXT).

JEMM is not a replacement of EMM386. I used it this year and lost many 
user's databases. Jemm is too much optimized an this is hardware 
dependent, it does not work alike on all machines.

I reverted to EMM386 and everything is running smoothly again. I am 
responsible for just ove 100 (ONE hundred) DOS machines running 24/7 
with heavy database usage.

 The other strange thing is that first (Load FreeDOS with EMM386, no EMS
 (most UMBs), max RAM free) or third (Load FreeDOS including HIMEM XMS-memory
 driver) option in startup menu works normally, as I see (not investigated
 seriously, but at least it looks so).

 Sounds like an EMM386 bug. I know I don't speak for everybody, but
 I'll try anyways:  nobody uses old EMM386, use new JEMM386.;-)

I use and it old stable and relyable.

On 2 new machines (last+this month) I had problems with X=TEST, I made 
it work with
   EMM386 NOEMS X=C000-EFFF NODISABLEA20 NOVDS /VERBOSE
this was apparently due to some periferal in UMB not detected

Alain


 Fourth option can’t be chosen at all.

 You can edit it by hand (if savvy enough).

 So as I’m new to this kind of OS I ask where can I read about this problem
 with second menu option and how can I try to fix it, if it’s possible?

 http://home.mnet-online.de/willybilly/fdhelp-dos/

 N.B. to others, the news item has long ago scrolled off the main page,
 so we need to not forget to proofread this (FDhelp) one of these
 days!

 Just for now I’ve edited fdconfig.sys to hide menu and use the third option
 by default, but it doesn’t look like a good solution.
 What kind of hardware info may be helpful for solving this problem?

 Just upgrade to JEMM386 first, then we'll see.

 Though I would also suggest getting kernel 2040, but I don't think
 that specifically will fix anything here.

 http://sourceforge.net/projects/freedos/files/Kernel/2040/ke2040_86f32.zip/download
 http://sourceforge.net/projects/freedos/files/Kernel/2040/ke2040s.zip/download

 --
 All the data continuously generated in your IT infrastructure contains a
 definitive record of customers, application performance, security
 threats, fraudulent activity and more. Splunk takes this data and makes
 sense of it. Business sense. IT sense. Common sense.
 http://p.sf.net/sfu/splunk-d2d-oct
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s

[Alain Mouette]

I had already told Eric that this was useless...

Alain

Em 18-10-2011 20:33, Rugxulo escreveu:
 Hi,

 On Tue, Oct 18, 2011 at 5:10 PM, Alain Mouetteala...@pobox.com  wrote:

 = = W A R N I N G = =

 = = ACHTUNG = =

 Em 18-10-2011 19:20, Rugxulo escreveu:

 If you're using FreeDOS 1.0 (2006), you may want to upgrade your EMM386 to 
 JEMM.

 I suggest JEMM386 X=TEST I=TEST or similar (see its README.TXT).

 JEMM is not a replacement of EMM386. I used it this year and lost many
 user's databases. Jemm is too much optimized an this is hardware
 dependent, it does not work alike on all machines.

 Nothing works the same on all machines, esp. since we all use various
 PCs from different OEMs. It could be a BIOS bug, your error, some
 other software error, etc.

 Let's not be too hasty to blame JEMM (or Japheth) as most of us use it
 without problems. Granted, if it doesn't work for you, don't use it.
 But a nice, clear bug report (or even patch) would be ideal.   ;-)

 I reverted to EMM386 and everything is running smoothly again. I am
 responsible for just ove 100 (ONE hundred) DOS machines running 24/7
 with heavy database usage.

 There were several bugs in that old version that Japheth has fixed. So
 really neither is perfect (what is?).

 I use and it old stable and relyable.

 Except when running spellcheck.   ;-)

 On 2 new machines (last+this month) I had problems with X=TEST, I made
 it work with
EMM386 NOEMS X=C000-EFFF NODISABLEA20 NOVDS /VERBOSE
 this was apparently due to some periferal in UMB not detected

 Did you use X=TEST alone or X=TEST I=TEST ?? I think he was going
 for more MS-like auto-detection there, which is why it's slightly
 different handling now. (And for instance, I think one of the big
 issues with old EMM386 was heavily incomplete [broken?] VDS.)

 BTW, call me naive, but does that above line even give you any UMB
 space?? If not (and NOEMS), why use EMM386 at all?? (Just use XMS.)
 :-/

 --
 All the data continuously generated in your IT infrastructure contains a
 definitive record of customers, application performance, security
 threats, fraudulent activity and more. Splunk takes this data and makes
 sense of it. Business sense. IT sense. Common sense.
 http://p.sf.net/sfu/splunk-d2d-oct
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s

[Alain Mouette]

Usefull part bellow:

Em 18-10-2011 20:33, Rugxulo escreveu:

 On 2 new machines (last+this month) I had problems with X=TEST, I made
 it work with
EMM386 NOEMS X=C000-EFFF NODISABLEA20 NOVDS /VERBOSE
 this was apparently due to some periferal in UMB not detected

 Did you use X=TEST alone or X=TEST I=TEST ?? I think he was going
 for more MS-like auto-detection there, which is why it's slightly
 different handling now. (And for instance, I think one of the big
 issues with old EMM386 was heavily incomplete [broken?] VDS.)

 BTW, call me naive, but does that above line even give you any UMB
 space?? If not (and NOEMS), why use EMM386 at all?? (Just use XMS.)
 :-/

Other things did not work anly with XMS, among other things emm386 puts 
the machine in protected mode, this helped something...

And es, you are right, it gave me no UMB, which in that situation is 
just a minor annoyance. My program is 32 bits so it does not need much 
lower memory.

I tried but could not find a range to exclude that worked and would 
leave me some UMB :(

Alain

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Grr ... (Was: Re: mTCP-2011-10-01 is available

[Alain Mouette]

I had problems with networking in dos for a few users, a short time ago. 
After a lot of headache, I discovered that those were conections via 
ADSL that used PPPoE, which has a 28 bytes overhead.

So now I use
   MTU=1472
and I had no more problems ever since. I recommend to anyone, use 1472 
to avoid problems.

:)
Alain

Em 05-10-2011 20:45, Michael B. Brutman escreveu:

 Excellent, and you are welcome!  I am glad it is working this time
 around - I get embarrassed when I let broken code out.  Some questions:

 For best performance the following should be set in the mTCP config file:

   MTU 1500
   FTPSRV_FILEBUFFER_SIZE 16
   FTPSRV_TCPBUFFER_SIZE 16
   FTPSRV_PACKETS_PER_POLL 10

 The default for the buffer sizes is 8; 16 makes it noticeably better.
 I'm assuming you can use MTU 1500 on your network - if it is pure
 Ethernet that would be safe and optimal.  FTPSRV_PACKETS_PER_POLL has a
 very low default and it could be restricting performance.  Your machine
 is fast enough so setting it to 10 should be fine.

 What settings do you have at the moment, and can you try these settings
 and send me new numbers?

 You are correct - Datalight Sockets is at a disadvantage because of the
 TSR approach, but you can still use your machine while it is running.
 :-)  WATT32 should have the advantage of being able to use more memory
 for buffering, but it clearly can't run on an 8088.  Most people don't
 want to use an 8088 anyway ..


 Mike

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Grr ... (Was: Re: mTCP-2011-10-01 is available

[Alain Mouette]

Em 05-10-2011 21:39, Michael B. Brutman escreveu:
 On 10/5/2011 7:27 PM, Alain Mouette wrote:
 So now I use
  MTU=1472
 and I had no more problems ever since. I recommend to anyone, use 1472
 to avoid problems.

 Ah, interesting!  I should put that tip in the user notes.

 I set a default of 576, which is the minimum that a gateway must
 support.  SLIP and PPP users often must use less.  I probably should
 work on a utility to do some MTU path discovery to diagnose problems
 like that.

I monitored Firefox in that network with WireShark. ICMP is used to 
adjust the MTU, for every connection the first packet is sent with 1500, 
then it is resent with 1472. Terribly ineficinet, it works because 
mostly the first send packet is usually smaller.

I also don't have ICMP fully implemented, so it just did not work at all...

Alain

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS on bigger disk image

[Alain Mouette]

I have managed to do that with Eric's help. It is in the list archives:

http://www.mail-archive.com/freedos-user@lists.sourceforge.net/msg10922.html

I made it for 6M (4x floppy size), other sizes are equaly possible

Aain

Em 16-09-2011 10:00, Hoot, Joseph escreveu:
 Hi all,

 I've been using a 4M disk image that has freedos on it for awhile now to do 
 bios updates in my Dell iDRAC.  I'm finally crossing the threshold of 
 available space and need to create a new, larger, disk image.

 So what process would I go through to create this larger disk image?  Here 
 are some of the things that I've done so far from Linux:

 1) dd if=/dev/zero of=disk20M.img bs=1m count=20
 2) mkdosfs on the disk20M.img
 3) grabbed a FDOEM.144 img from the web and dd the boot sector off of it with 
 the following:
  dd if=FDOEM.144 of=disk20M.img bs=1 count=446 seek=62 skip=62 
 conv=notrunc
 4) mount -o loop disk20M.img /mnt-- and then copy whatever EXE's and such 
 that I wanted over to the disk.
 5) umount the disk20M.img from /mnt
 6) attempt to boot

 This process worked for me in the past, but I haven't been able to get it to 
 work now that I'm increasing the disk to 20M

 Does anyone have any advise on trying to get this to work?

 Thanks,
 Joe

 ===
 Joseph R. Hoot
 Lead System Programmer/Analyst
 (w) 716-878-4832 (Office - Receptionist/able to leave message)
 (w) 716-878-4863 (Direct - no voicemail)
 (c) 716-759-HOOT
 joe.h...@itec.suny.edu
 GPG KEY:   7145F633
 ===


 --
 BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
 http://p.sf.net/sfu/rim-devcon-copy2
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Heads up: DOS ain't dead forum is closing

[Alain Mouette]

Em 14-09-2011 08:14, Zbigniew escreveu:

 But, actually, why you want another DOSBOX to be created? You've got
 already DOSBOX and DOSEMU... it's not enough?

Well, it is not really satisfactory. DosBox does not have packet driver 
for networking and Dosemu is not getting any updates ant it getting hard 
to use in new distros.

(I sent 3 important patches and they have not been incorporated, infact 
there has not been a release since then)

Alain

--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerryreg; mobile platform with sessions, labs  more.
See new tools and technologies. Register for BlackBerryreg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FD 1.1 Bootfloppy Problems

[Alain Mouette]

Try emm386.exe, jemm is too much optimysed and does not work well on ALL 
machines.

Plain old emm386 uses a more conventional aproach en tries NOT TO USE 
hardware as much as possible, an then it is more universal. It is 
probably slower, but safer...

Alain

Em 30-07-2011 08:47, JPT escreveu:
 Hi,

 tried the floppy to partition and format the hardisk.
 It works if I choose not to load any drivers. ^^

 ie.
 1 - Install FreeDOS...
 3 - Dont load any drivers at all


 In the other cases, I get crashes.

 1 - Use default settings
 results in a JemmEx errormessage after loading the kernel.
 JemmEx: exception 06 occured ad cs:eip 02a3:...6af,errc 0
 after pressing escape
 JemmEx: exception 06 occured ad cs:eip 02a3:...15ae,errc 0
 again pressing escape gives an a: prompt

 2 - use alternative xms memory manager (xmgr)
 results in invalid opcode after loading the kernel.

 This is for hardware
 P3-800, Asus Cubx board, Intel i440BX
 chip, 384MB of RAM, Network 3Com 3c905b


 On Oracle VirtualBox it works, but takes a long time searching the IDE
 bus. (did not attach a harddrive)


 Now these problems are documented and the drive is formatted, I will try
 the old installer CD again.

 JPT


 ps. I made screenshots, but I did not attach them to this email. so if
 you need more details, give me an email adress where to send them.

 --
 Got Input?   Slashdot Needs You.
 Take our quick survey online.  Come on, we don't ask for help often.
 Plus, you'll get a chance to win $100 to spend on ThinkGeek.
 http://p.sf.net/sfu/slashdot-survey
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos  much more. Register early  save!
http://p.sf.net/sfu/rim-blackberry-1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Can't Install; FreeDOS 1.1 test release #2

[Alain Mouette]

I have been installing FreeDOS a lot, the only thing that works ALLWAYS 
including USB CDs, is what I describel in a message 15june2011...

Then I can have a huge A: (I made it with bytes) with all that I need.

There is no way to make something that recognizes the CD everywhere.

Alain

Em 20-07-2011 14:46, Bernd Blaauw escreveu:
 Op 20-7-2011 4:17, Virii schreef:
 What exactly goes wrong when you do what?
 At which step? Which error messages do you
 get, or do things hang? Crash? What sorts
 of everything did you try, what happened?

 It hangs at the language selection screen. The very bottom selection of the
 main menu looks for a non-existent FDBOOTCD.ISO. The readme states that it
 should load the ISO into a ramdisk. Etc...

 Language selection: think I fixed that last night.
 Bottom selection: decided to keep things easy this time, without ISO
 inside CD/ISO. Easily enough added again, the UPDATE batchfile which is
 on the A: part (\ISOLINUX\FDBOOT.IMG) creates the inner ISO (which is
 uploaded as TEST2) followed by the outer ISO (which I uploaded as TEST1
 earlier) on ramdisk (64MB required at least). After modifications
 followed by creation of both ISOs, you can decided for yourself which
 ISO to copy to harddisk.


 But, nevermind. [Smacks self in forehead...]

 hehe. They're test releases for a reason, I'm not able to fix and
 improve everything right away and in perfectly usable shape.

 I simply extracted the contents of the ISO to the C:\ partition, and
 successfully ran the setup from there.

 It complained about a few missing packages like doslfn, wattcp, wget, ...,
 but it installed. Can I just copy over the 'doslfn' from an older version's
 disc, or is that feature compiled into kernel now?

 Copy all you want, directory structure was modified a bit without
 telling the installer. As a consequence, the package is present but not
 installed.

 They works when I DEVLOAD them post boot-up, but the USB flash drive steals
 the DVD-RW drive's letter (E:\ in my case). USBUHCI, and USBDRIVE don't work
 at all for me. It not only wont load my USB drives, it doesn't even find
 them. Strangely enough if I load them before USBASPI/NJ32DISK, my flash
 drive is assigned M:\ instead.

 Strange indeed. CD-ROM driveletter can be altered if you want:
 option 1: SHSUCDX /D:FDCD0001,X
 option 2: SHSUCDX /D:FDCD0001 /L:X

 Your drivers taking over early driveletters is something I can't help,
 no experience with the USB drivers you mention.
 A commercial/trialware USB stack is at http://www.georgpotthast.de/usb/
 , might work, or not. Worked for me yet lacks functionality and disables
 USB legacy stuff so I ended up with a non-functioning keyboard till reboot.

 --
 10 Tips for Better Web Security
 Learn 10 ways to better secure your business today. Topics covered include:
 Web security, SSL, hacker attacks  Denial of Service (DoS), private keys,
 security Microsoft Exchange, secure Instant Messaging, and much more.
 http://www.accelacomm.com/jaw/sfnl/114/51426210/
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks  Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Kernel 2040 16-bit

[Alain Mouette]

Em 14-07-2011 13:29, Bernd Blaauw escreveu:
 Op 14-7-2011 5:09, Marcos Favero Florence de Barros schreef:
   I'm now using the 32-bit 2040 kernel, because none of these
 errors has ever appeared under the previous 32-bit kernels, and
 I'm hoping they will not appear under the new one either
 [fingers crossed].

   Any advice is welcome.

 Thanks for reporting the issues you're experiencing with the FAT16
 kernels, multiple versions. Do you have a way of verifying
 file/filesystem/disk integrity outside of FreeDOS?

Maybe using Norton utilities 8, it shows really usefull information...

Alain


 FreeDOS has no 32bit kernels, there's a FreeDOS32 project somewhere but
 that hasn't gotten very far yet. The 16 and 32 for FreeDOS kernels
 purely indicate what they support:
 * either FAT12 and FAT16 filesystems
 * or FAT12 and FAT16, but also FAT32 filesystems
 (or rather partitions using these filesystems)

 It's usually fine to run FAT32-enabled kernels. However that's no reason
 to have FAT16-only kernels contain certain bugs.

 I've not tried FAT16 kernel and CHKDSK as you have. I've not tried using
 CHKDSK either on FAT32 drives, doubt it supports it.

 Latest FreeDOS CHKDSK is 0.92
 ( http://users.telenet.be/imre/FreeDOS/ckdsk092.zip ).

 maybe I'll find some opportunity to try and see if I can reproduce your
 issues (CHKDSK on FAT16 kernels reporting errors with files, while on
 FAT32 kernels no such issues).

 Bernd

 --
 AppSumo Presents a FREE Video for the SourceForge Community by Eric
 Ries, the creator of the Lean Startup Methodology on Lean Startup
 Secrets Revealed. This video shows you how to validate your ideas,
 optimize your ideas and identify your business strategy.
 http://p.sf.net/sfu/appsumosfdev2dev
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on Lean Startup 
Secrets Revealed. This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Big bootable disk for CD

[Alain Mouette]

Hi, I am still having problems making an intaller from CD. I came across 
an HP machine (MS219BR) that no drive recognizes and also external USB 
CD drivers. So...

How can I make a big (6Mb) bootable image to use in the CD?

This is the only part of the CD that I can read on *any* machine, I am 
using syslinux)

thanks,
Alain

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Big bootable disk for CD

[Alain Mouette]

Em 15-06-2011 11:51, Alain Mouette escreveu:

 How can I make a big (6Mb) bootable image to use in the CD?
 This is the only part of the CD that I can read on *any* machine, I am
 using isolinux)

With lots of help fom Eric Auer, I managed to make a bootable image with 
FreeDOS. Here is how I did it:

1) Program needed: NASM, which I got from Debian
$ sudo apt-get install nasm

2) program from Eric for the boot sector:
http://ericauer.cosmodata.virtuaserver.com.br/soft/specials/sys-freedos-linux.zip
create a directory ./sys-freedos-linux and expand it there

3) create file of the right size. 5760k was ok for me, there is some 
magic in the size and not everything will be ok. (more studies needed)
$ dd if=/dev/zero of=FreeDOS.img count=11520
11520+0 records in
11520+0 records out
5898240 bytes (5.9 MB) copied, 0.408512 s, 14.4 MB/s

4) Prepare it with a FAT file system
$ sudo mkdosfs -v FreeDOS.img
mkdosfs 3.0.1 (23 Nov 2008)
FreeDOS.img has 64 heads and 32 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 11520 sectors;
file system has 2 12-bit FATs and 4 sectors per cluster.
FAT size is 9 sectors, and provides 2867 clusters.
Root directory contains 512 slots.
Volume ID is 0cbb7ca7, no volume label.

5) compile and write a suitable boot sector. This is a smart script by 
Eric Auer that configures it with the appropiate parameters
$ ./sys-freedos-linux/sys-freedos.pl --disk=FreeDOS.img
DOS boot sector for FreeDOS.img will be created by:
 nasm -o /dev/stdout -dISFAT12 
./sys-freedos-linux/bootsecs/boot.asm
Using FAT12. Partn offset 0, CHS *x64x32  Drive 0, (0x0, 0x29),
SerNo CBB-7CA7, Strings '   ',  'FAT12   '.
Boot sector successfully updated.

6) mount it in a directory
$ mkdir bootimg
$ sudo mount -v -o loop,uid=you,gid=you FreeDOS.img bootimg

7) copy into it KERNEL.SYS, COMMAND.COM and all other files

8) use it just the same way then the image made from a floppy, memdisk 
will recognize it. I used isolinux, here is how I created the iso:
$ mkisofs  -R -v -A FreeDOS big boot CD -V FreeDOS-V1.x \
 -b isolinux/isolinux.bin -c isolinux/boot.cat \
 -no-emul-boot -boot-load-size 4 -boot-info-table  \
 -o /mnt/dados/Segurver/FreeDOS-V1.x.iso   \
 /mnt/dados/CDROM

Alain

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Problem with XMGR (was: UIDE)

[Alain Mouette]

After all my strugling with UIDE, I got it working on almost all machines...

On one machine I got a strange XMGR problem:

On first try, XMGR (with /B) reports cannot determine A20 method and 
dos not load, repeating it imediatly (without /B) it loads with A20 
allways on. Sorry, these are aproximate messages, the machine is 2 
hours from here and another person was there. I did this double load, by 
singlestepping and saying No to jemm386.

On the same machine Himem.exe worka just fine, using A20 allways on

== Could there be a default behaviour to avoid this problem?

Thanks,
Alain


Em 19-05-2011 13:40, Bernd Blaauw escreveu:
 Op 19-5-2011 2:28, Alain Mouette schreef:
 I managed to make a Boot CD that works almost in all machines. The only
 one that is not working is Virtual PC 2007. it locks uppun execution
 of JEMM386 from a CD image. XMGR is used because it is required by UIDE.

 Technically UIDE doesn't require XMS nor an XMS manager if omitting the
 caching function.
 The /N1 /N3 /B parameters should do fine, for example perform a F5 clean
 boot, then:
 DEVLOAD UIDE.SYS /D:FDCD0001 /N1 /N3 /B

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] **NO** Problem with XMGR, **NOR** with UIDE!!

[Alain Mouette]

Sorry Jack... I won't bother you again

Alain

Em 10-06-2011 22:38, Jack escreveu:

 I am getting VERY TIRED of responding to FALSE problems about my
 drivers!!

 Last month, an entire thread on this forum was labelled Problem
 with UIDE, when that actually was FALSE!   The problem was only
 a device-driver conflict, and it took several posts here to note
 UIDE was being run WITH some unknown CD-ROM boot driver!   And
 after all that, the thread CONTINUED to use the heading Problem
 with UIDE, which it WAS NOT!!

 In that thread, near its end, we also have the post noting --

 I managed to make a Boot CD that works almost in all machines.
 The only one that is not working is Virtual PC 2007.   It
 locks uppun execution of JEMM386 from a CD image.   XMGR is
 used because it is required by UIDE.

 That is totally FALSE!   UIDE does NOT specifically demand using
 XMGR and will run just fine with MS-DOS HIMEM, Japheth's HIMEMX,
 or any other correctly written XMS manager driver.   UIDE only
 requires that SOME driver -- it DOES NOT care which one! -- sets
 up the necessary XMS memory for UIDE to use as its cache!!

 And today, I note the following new post, in the same thread now
 labelled Re: [Freedos-user] Problem with XMGR (was: UIDE) --

 On one machine I got a strange XMGR problem:
 On first try, XMGR (with /B) reports cannot determine A20 method
 and does not load, repeating it immediately (without /B) it loads
 with A20 allways on.  Sorry, these are aproximate messages, the
 machine is 2 hours from here and another person was there.  I did
 this double load, by singlestepping and saying No to jemm386.
 On the same machine Himem.exe worka just fine, using A20 allways
 on

 As anyone can see in the XMGR.ASM source file, NONE of the above
 messages will be displayed by XMGR, as none of them EXIST in its
 source!   XMGR is also written to use (A) no A20 line handling
 if it sees A20 already on at load-time, (B) IBM PS/2 Port 92
 handling of A20, or (C) old-style Keyboard port handling for
 the A20 line as its normal default.

 XMGR will never -- I say again, NEVER! -- display that it cannot
 determine which method to use for handling the A20 line!   One
 of the above 3 methods is ALWAYS present, on today's PC systems!
 The many strange schemes for handling A20 (which made MS-DOS
 HIMEM.SYS end up over 30K bytes long!) are long since obsolete
 and no-longer in use, as far as I know.   And as far as I know
 is pretty good, since there have been FEW (legitimate!) problems
 with XMGR for a long time!

 XMGR can display NOTE:  A20 line found on!, if that is so when
 the driver loads.   But, it CANNOT display A20 allways on, and
 the use or non-use of its /B switch does NOT affect which method
 for handling A20 will be used.   Obviously, the PC system does
 not change, between XMGR'S boot and its final loading in upper
 memory, so it is FOOLISH to think that /B could have any effect!

 If the message cannot determine A20 method is being displayed,
 I quite strongly suggest that it is coming from SOMEWHERE ELSE!!
 Maybe, that other system 2 hours away was in fact using MS-DOS
 HIMEM at that time, since as I recall HIMEM could display such a
 message, if all its miserable 30K of init logic gets confused!
 Or, maybe some other program or driver -- but NOT XMGR!!

 I am SORRY, if people don't like hearing all this from me -- But
 there are those who need to be A BIT MORE POSITIVE re: problems,
 before they so-quickly RUSH to call them Problem with UIDE, or
 Problem with XMGR, or problem with anything BUT their own lack
 of reliable-and-true information ABOUT their problems!!!


 --
 EditLive Enterprise is the world's most technically advanced content
 authoring tool. Experience the power of Track Changes, Inline Image
 Editing and ensure content is compliant with Accessibility Checking.
 http://p.sf.net/sfu/ephox-dev2dev
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Problem with UIDE

[Alain Mouette]

Hi Japheth,

I am glad that you are here, it is nice to have our little family 
mantaining contact.

I managed to make a Boot CD that works almost in all machines. The only 
one that is not working is Virtual PC 2007. it locks uppun execution 
of JEMM386 from a CD image. XMGR is used because it is required by UIDE.

Image of the screen: 
http://suporte.cosmodata.com.br/downloads/moni/tmp/trava02.png
Image of the CD that I used: 
http://suporte.cosmodata.com.br/downloads/moni/CosmoData-M14093c.iso

The problem only happens booting from the ISO, and my problem is making 
a distribution CD with FreeDOS...

Alain

Em 18-05-2011 02:05, japhethx gmail escreveu:
 1). NOEMS is rarely used, and a lot of things don't handle it well.
 ...
 ... I wouldn't do this. Just load a XMS
 driver only (and not via NOEMS).

 NOEMS is ok and safe, the switch which causes problems with some programs is
 FRAME=NONE.

 2). Actually, I've noticed JEMM386 will hang if you aren't careful,
 esp. on newer machines due to memory conflicts.

 True. In v5.74, there's a tool MEMSTAT which will tell what parts of the
 BIOS-ROM region ( which is E000-, not just F000- ) are to be excluded
 to be safe.

--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Problem with UIDE

[Alain Mouette]

Hi Jack,

(I hope this messags comes though, 5th try...)

I am encountering a strange problem with UIDE. It happens with some 
machines but not all, one of the failing machine is nearby so I can make 
more tests easely...

I am using UIDE and XMGR from 10-May-11, I made my config from your 
example (whole file attached), jemm386 is 572 dated 13mar2008 (complete 
config at the end):
device=a:\dos\xmgr.sys /B
device=a:\dos\jemm386.exe I=TEST NOEMS
device=a:\dos\xmgr.sys
device=a:\dos\uide.sys /D:CDROM

It works ok booting from floppy and from hard-disk, but it does not work 
when booting from the CDROM. It stops with this screen and the HD led on:
http://suporte.cosmodata.com.br/downloads/moni/tmp/trava01.jpg

Please help, I am trying to make a universal installer...

Alain
--

menucolor=10
menu
menu ┌───┐
menu │ Disco de instalaçäo do FreeDOS │
menu │ │
menu │ │
menu │ │
menu │ 1. Driver de CD: UIDE (padräo) │
menu │ 2. Sem CD-ROM │
menu │ │
menu └───┘
menu
menudefault=1,5

1? echo Driver: UIDE
2? echo Driver: Sem CD

screen=0x12
dos=high,umb
buffers=15,0
files=100
fcbs=4,0
lastdrive=Z

1? device=a:\dos\xmgr.sys /B
1? device=a:\dos\jemm386.exe I=TEST NOEMS
1? device=a:\dos\xmgr.sys
1? device=a:\dos\uide.sys /D:CDROM

2? device=a:\dos\himem.exe
2? device=a:\dos\emm386.exe NOEMS X=TEST

country=055,850,a:\dos\country.sys
shell=A:\command.com A:\ /E:1300 /p


--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Problem with UIDE

[Alain Mouette]

Hi Bernd, Hi Jack,

Em 17-05-2011 14:04, Bernd Blaauw escreveu:
 Op 17-5-2011 17:45, Alain Mouette schreef:
 I am using UIDE and XMGR from 10-May-11, I made my config from your
 example (whole file attached), jemm386 is 572 dated 13mar2008 (complete
 config at the end):
 device=a:\dos\xmgr.sys /B
 device=a:\dos\jemm386.exe I=TEST NOEMS
 device=a:\dos\xmgr.sys
 device=a:\dos\uide.sys /D:CDROM

 It works ok booting from floppy and from hard-disk, but it does not work
 when booting from the CDROM. It stops with this screen and the HD led on:
 http://suporte.cosmodata.com.br/downloads/moni/tmp/trava01.jpg

 Please help, I am trying to make a universal installer...

 Alain,

 I've recently encountered the same issue, not sure if it's purely
 limited to booting from CD-ROM.
 In my case I tend to use Syslinux --  Memdisk --  Disk Image ( --
 bootsector --  kernel --  config.sys --  shell --  autoexec.bat --
 commandline)

 1) Does loading everything except UIDE work for you?
 2) Does loading everything except UIDE work for you, if you later load
 UIDE from the commandline? DEVLOAD UIDE.SYS /D:CDROM
 3) If you replace the XMGR/JEMM386/XMGR by Japhet's JEMMEX, does that
 work? ofcourse still load UIDE from config.sys
 4) If you replace the XMGR/JEMM386/XMGR by Japhet's HIMEMX + JEMM386,
 does that work? ofcourse still load UIDE from config.sys
 5) Does the same behaviour happen under MSDOS? Slightly more difficult
 question ofcourse, but FreeDOS kernel/shell occasionally is easy to
 hang/crash, SHELLHIGH is a culprit at times, for example.

 I think JEMM is at 5.74 by now, can't hurt to use latest version I guess.

 This should work:
 DEVICE=A:\DOS\HIMEMX.EXE
 DEVICE=A:\DOS\JEMM386.EXE I=TEST NOEMS
 DEVICE=A:\DOS\UIDE.SYS /D:CDROM
 DOS=HIGH,UMB
 DOSDATA=UMB

 Or:
 DEVICE=A:\DOS\JEMMEX.EXE I=TEST NOEMS
 DEVICE=A:\DOS\UIDE.SYS /D:CDROM
 DOS=HIGH,UMB
 DOSDATA=UMB

I just foud how to make it work (kind of...)

I boot normaly, single-stepping, loading all *except IEDE*, than I do:
   SET COMSPEC=C:\COMMAND.COM   (it's the same)
   C:
   DEVLOAD A:\DOS\UIDE.SYS /D:CDROM

it loads, and I can access drive C:, but if I access A: it locks just 
the same, with the HardDisk led on.

== so, imho, the drive A: is disapearing when UIDE is loaded. It looks 
like an iteraction between the BIOS boot driver which creates A: for the 
CD boot image and UIDE :(

For reference, I created the iso in Lunix with:
mkisofs -pad -R -v -A FreeDOS -b FreeDOS/FreeDOS.img -V FreeDOS-c11 -o 
/mnt/dados/Segurver/FreeDOS-c11.iso /mnt/dados/CDROM

Thanks,
Alain


--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Problem with UIDE

[Alain Mouette]

Em 17-05-2011 14:02, Tom Ehlert escreveu:
 Hi Alain,

 most likely UIDE disturbs the BIOS boot drive emulation
 I have no idea if UIDE can work around this.

 you can work around this by

 create a virtual disk
 copy A: to virtual disk (including autoexec.bat)
 so that A: is no longer needed

 execute autoexec.bat from virtual disk

 only then
DEVLOAD a:\dos\uide.sys /D:CDROM

Yes, that is consistent with my last experiment, How do you recomend to 
create a RAMdisk and use it as A: ?

I know there are a few options, but which one will work better with 
FreeDOS, specialy that I have to create it with another letter, fill it 
up, change it to A: later on ??

Alain




 am 17. Mai 2011 um 17:45 schrieben Sie:

 Hi Jack,

 (I hope this messags comes though, 5th try...)

 I am encountering a strange problem with UIDE. It happens with some
 machines but not all, one of the failing machine is nearby so I can make
 more tests easely...

 I am using UIDE and XMGR from 10-May-11, I made my config from your
 example (whole file attached), jemm386 is 572 dated 13mar2008 (complete
 config at the end):
 device=a:\dos\xmgr.sys /B
 device=a:\dos\jemm386.exe I=TEST NOEMS
 device=a:\dos\xmgr.sys
 device=a:\dos\uide.sys /D:CDROM

 It works ok booting from floppy and from hard-disk, but it does not work
 when booting from the CDROM. It stops with this screen and the HD led on:
 http://suporte.cosmodata.com.br/downloads/moni/tmp/trava01.jpg

 Please help, I am trying to make a universal installer...

 Alain
 --

 menucolor=10
 menu
 menu ┌───┐
 menu │ Disco de instalaçäo do FreeDOS │
 menu │ │
 menu │ │
 menu │ │
 menu │ 1. Driver de CD: UIDE (padräo) │
 menu │ 2. Sem CD-ROM │
 menu │ │
 menu └───┘
 menu
 menudefault=1,5

 1? echo Driver: UIDE
 2? echo Driver: Sem CD

 screen=0x12
 dos=high,umb
 buffers=15,0
 files=100
 fcbs=4,0
 lastdrive=Z

 1? device=a:\dos\xmgr.sys /B
 1? device=a:\dos\jemm386.exe I=TEST NOEMS
 1? device=a:\dos\xmgr.sys
 1? device=a:\dos\uide.sys /D:CDROM

 2? device=a:\dos\himem.exe
 2? device=a:\dos\emm386.exe NOEMS X=TEST

 country=055,850,a:\dos\country.sys
 shell=A:\command.com A:\ /E:1300 /p


 Mit freundlichen Grüßen/Kind regards
 Tom Ehlert

--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Problem with UIDE

[Alain Mouette]

Em 17-05-2011 14:04, Bernd Blaauw escreveu:

 I've recently encountered the same issue, not sure if it's purely
 limited to booting from CD-ROM.
 In my case I tend to use Syslinux --  Memdisk --  Disk Image ( --
 bootsector --  kernel --  config.sys --  shell --  autoexec.bat --
 commandline)

Do you mean that this should work, or this from your other message:

  Most fun part is having your floppy image, which contains Syslinux
  and a smaller floppy image. Then you'd have CD --  1.44MB image --
   Syslinux --  small image

In either case, is there a clear tutorial about how to make it? I did a 
little digging with google, but most syslinux explanations are unclear, 
complex and for other situations :(

 1) Does loading everything except UIDE work for you?

Yes

 2) Does loading everything except UIDE work for you, if you later load
 UIDE from the commandline? DEVLOAD UIDE.SYS /D:CDROM

Lock the same, if I change comspec it works intill i try to use A:

 3) If you replace the XMGR/JEMM386/XMGR by Japhet's JEMMEX, does that
 work? ofcourse still load UIDE from config.sys

No difference

 4) If you replace the XMGR/JEMM386/XMGR by Japhet's HIMEMX + JEMM386,
 does that work? ofcourse still load UIDE from config.sys

Will do it today

 5) Does the same behaviour happen under MSDOS? Slightly more difficult
 question ofcourse, but FreeDOS kernel/shell occasionally is easy to
 hang/crash, SHELLHIGH is a culprit at times, for example.

withou any dos high the result does not change...

 I think JEMM is at 5.74 by now, can't hurt to use latest version I guess.

Found it! it is not mirired ad ibiblio...
I will test it today

Thanks,
Alain


 This should work:
 DEVICE=A:\DOS\HIMEMX.EXE
 DEVICE=A:\DOS\JEMM386.EXE I=TEST NOEMS
 DEVICE=A:\DOS\UIDE.SYS /D:CDROM
 DOS=HIGH,UMB
 DOSDATA=UMB

 Or:
 DEVICE=A:\DOS\JEMMEX.EXE I=TEST NOEMS
 DEVICE=A:\DOS\UIDE.SYS /D:CDROM
 DOS=HIGH,UMB
 DOSDATA=UMB

--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Problem with UIDE

[Alain Mouette]

(top posting to make it shorter)

I do need as much conventional memory as I can get, and even the it is a 
tight fit...

So everyone belives that
   JEMM386 X=TEST NOEMS
is safer? if so, I will change...

Thanks,
Alain

Em 17-05-2011 16:35, Rugxulo escreveu:
 Hi,

 On Tue, May 17, 2011 at 10:45 AM, Alain Mouetteala...@pobox.com  wrote:

 I am encountering a strange problem with UIDE. It happens with some
 machines but not all, one of the failing machine is nearby so I can make
 more tests easely...

 I am using UIDE and XMGR from 10-May-11, I made my config from your
 example (whole file attached), jemm386 is 572 dated 13mar2008 (complete
 config at the end):
 device=a:\dos\xmgr.sys /B
 device=a:\dos\jemm386.exe I=TEST NOEMS
 device=a:\dos\xmgr.sys
 device=a:\dos\uide.sys /D:CDROM

 It works ok booting from floppy and from hard-disk, but it does not work
 when booting from the CDROM. It stops with this screen and the HD led on:
 http://suporte.cosmodata.com.br/downloads/moni/tmp/trava01.jpg

 Definitely try latest JEMM386 5.74, but honestly, I think the problem
 is two-fold (blindly guessing, so I could be wrong):

 1). NOEMS is rarely used, and a lot of things don't handle it well. I
 think this means VCPI is still available as well as UMBs but not EMS.
 In other words, I guess? you're trying to save precious conventional
 memory by using JEMM386 while only using XMS (no EMS). Honestly,
 unless you really *need* that much conventional memory free (unlikely,
 as FreeDOS is pretty efficient), I wouldn't do this. Just load a XMS
 driver only (and not via NOEMS).

 2). Actually, I've noticed JEMM386 will hang if you aren't careful,
 esp. on newer machines due to memory conflicts. In particular, your
 I=TEST parameter is pretty dangerous. I think typically it works
 better if you do X=TEST I=TEST (or maybe even not at all). Lemme
 search my old mails for a sec ...

 Apparently, BioMenace (DOS game, now freeware, see 3D Realms site)
 needs both EMS (hence EMM386) and XMS and (at least for my other,
 older P4) X=TEST I=TEST NORAM. Normal JEMM386 loading just hung, and
 anything else didn't give it enough EMS to load to E1L3 without
 crashing the program due to insufficient memory. I blame ACPI, natch.

 P.S. Maybe I'm way off, and I know you're talking about a vaguely
 different problem, but just keep in mind, EMM386 can be tricky on
 newer hardware with weird memory configs (ACPI). That's the whole
 point I was trying to make, however futile it may seem. (You can also
 run JEMM386 LOAD at any time but that doesn't give you UMBs. JEMMEX
 doesn't let you run as pure XMS only.)

 --
 Achieve unprecedented app performance and reliability
 What every C/C++ and Fortran developer should know.
 Learn how Intel has extended the reach of its next-generation tools
 to help boost performance applications - inlcuding clusters.
 http://p.sf.net/sfu/intel-dev2devmay
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Problem with UIDE: Solved

[Alain Mouette]

Thanks to all of you that have helped me with this problem. It could 
have taken ages to test and understand what was happening...


Many Thanks to Eric Auer who had a LOT of patience with me, I manage to 
make it run. So here is my minimalistic setup. I hope that someone can 
publish it somewhere...


1) Have a directory with the all the CD content, let's call it 
/mnt/dados/CDROM, inside it create a single directory called 
*isolinux* (I was not able to change it's name)


2) Have a bootable floppy, that includes the CDROM driver. Create an 
image in the .../CDROM/FreeDOS directory with

*dd if=/dev/fd0 of=FreeDOS.img*

3) Download Syslinux from 
http://syslinux.zytor.com/wiki/index.php/ISOLINUX, in a temporary 
directory. Copy the files core/*isolinux.bin* and memdisk/*memdisk* into 
the .../CDROM/isolinux directory (no subdirectories).


4) in the isolinux directory create this *isolinux.cfg* simple file
---isolinux.cfg
*default FreeDOS
label FreeDOS
kernel /isolinux/memdisk
append initrd=/FreeDOS/FreeDOS.img
*--

5) create the .ISO with mkisofs:
*mkisofs  -R -v -V FreeDOS-1.x   \
-b isolinux/isolinux.bin -c isolinux/boot.cat\
-no-emul-boot -boot-load-size 4 -boot-info-table \
-o /mnt/dados/FreeDOS-1.x.iso\
/mnt/dados/CDROM
*
That is all folks, I am amazed how this simple thing gets overly complex 
in all explanations in the internet!!!


Alain

--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Code pages in dot-matrix printers

[Alain Mouette]

On 24 pin Epson printers, you can print graphics as fast as printing 
text. there is a special mode where consecutive high definition dots 
cannot be on, which is the text mode printing trick...

But I believe that even if you use the more universal mode, it will be 
fast enough, specially if compared with the alternative which is no mode 
at all...

It woul be best if you could devise a method to automaticaly translate 
the screen bitmaps do printer bitmaps...

Alain

Em 06-05-2011 13:51, Henrique Peron escreveu:
 Hi Mark,

 it's not about willing to accept. Unfortunately, printing on graphics
 mode seems to be the only common denominator among all brands and models
 of printers.

 Naturally, if someone needs a character table which is already hardcoded
 to his/her printer, all (s)he will have to do is to setup his/her
 printer accordingly and print on text mode. However, many printers have
 a very reduced set of character tables; furthermore, there are a lot of
 codepages which I created for FreeDOS which naturally aren't hardcoded
 anywhere.

 Last but not least - the DOS drivers you pointed us to refer to 32-bit DOS.

 Henrique

 Em 6/5/2011 11:20, Mark Blain escreveu:
 Henrique Peronhpe...@terra.com.br   wrote in
 news:4dc2ebc0.30...@terra.com.br:

 I just read a PDF file Epson ESC/P Reference Manual. It explains
 that 24-pin printers can receive definitions on 241 characters
 into its RAM but those 9-pin LX printers cannot. They can only
 receive 6 characters. It seems that uploading a codepage into a
 printer's RAM is out of the question. :-(

 Perhaps the idea (which is what I did once with a 9-pin Epson
 LX-800 that I had) is to manipulate the printer head directly.
 That would leave CPI files and hardcoded printer codepages out of
 the equation. That would force me to manually provide the data
 (through a TXT file) which would be sent to a printer through some
 program which would pose as a printer driver. I would like to
 elaborate more on this but it seems this is the wrong freedos-list
 to do that. I have some ideas and perhaps we could work together
 on a printer driver for FreeDOS.
 If you're willing to accept the very slow printing speed of your
 printer's graphics mode then you may want to investigate GhostScript,
 which already provides a wide variety of fonts, sizes and printer
 drivers.
 http://en.wikipedia.org/wiki/PostScript#.22Hello_world.22
 http://pages.cs.wisc.edu/~ghost/doc/AFPL/get510.htm


 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user

 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Code pages in dot-matrix printers

[Alain Mouette]

In the printes, fonts should have

Low Res  9 pin: 72/6 = 12 pixels
Low Res 24 pin: 180/6= 30 pixels
Hi Res   9 pin: 144/6= 24 pixels
Hi Res  24 pin: 360/6= 60 pixels

This for the whole line (glyph + spacing). Can tou imagine how to 
convert your database to work with these resolutions?

Alain

Em 06-05-2011 23:33, Henrique Peron escreveu:
 Hi Eric, Mark,

 Ok - I have a glyph database of 8x16 chars in a single text file.
 Would that do for a start? Or the idea is to wait for someone volunteer
 on developing software to automatically convert screen fonts to the printer?

 Henrique

 Em 6/5/2011 17:09, Eric Auer escreveu:
 Hi Mark, Henrique,

 ghostscript in general is a nice tool and there are ports for
 DOS which work in FreeDOS or are even made for FreeDOS, I think
 that for example Blair made one such port. Using 32 bit DOS C
 compilers is no big problem, things still run on 16 bit DOS but
 you will need a 386 or newer CPU. Another nice detail is that
 ghostscript can output several printer languages, PDF and PS.

 However, the main purpose of ghostscript is to read postscript.
 As such, it is not meant to be used as a small tool or even a
 driver to convert plain text into a picture of that text with
 a given bitmap font. In fact, ghostscript would be a *very*
 bloated software if you only want to do that ;-)

 Eric

 PS: I think 8x16 fonts or 16x16 fonts are not that bad. And it
 is indeed true that graphics modes with a limited horizontal
 resolution print much faster... In fact 180x180 dpi fits text
 printing, speed and compatibility very well on ESC/P printers.



 ...
 Last but not least - the DOS drivers you pointed us to refer to
 32-bit DOS.
 Ah, I didn't catch that.  You could find an older 16-bit GhostScript,
 but it doesn't sound like scalable fonts are your current goal.

 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user

 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Code pages in dot-matrix printers

[Alain Mouette]

There is a manual here
http://support.epson.ru/upload/library_file/14/esc-p.pdf
and some info here:
http://webpages.charter.net/dperr/links/esc_p2.htm

is this what you want?

Alain

Em 04-05-2011 14:31, Henrique Peron escreveu:
 Thank you very much my friend! :)


 Em 4/5/2011 07:53, escape escreveu:
 Hello Henrique

 I have an good-old dot-matrix printer, but unfortunately without any
 manual. But I think it's not a big problem, as in-printer codepage can
 be printed. Still I bet, that in this case there is only two options
 possible: cp437 or some slight variation of cp866. I will send you
 results as soon, as I can get some time to recover it from storage, set
 it up and print-out ASCII-chart.


 On 28.04.11 10:05, Henrique Peron wrote:
 Hi all,

 is there anyone out there which happens to have user guides/reference
 manuals of those old dot-matrix printers?

 If so, there are, in general, pages on those guides that show tables of
 characters (Code pages).

 My e-mail address is hperon AT terra.com.br ; in case someone wants to
 help me, I could be contacted through the e-mail address just informed.

 The idea is to convert all useful info into new codepages for FreeDOS.
 Let me mention two cases as examples: I've been looking (for a few years
 already) for the description of codepages 854 and 776.

 Thanks in advance.

 Henrique Peron


 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user

 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user

 --
 WhatsUp Gold - Download Free Network Management Software
 The most intuitive, comprehensive, and cost-effective network
 management toolset available today.  Delivers lowest initial
 acquisition cost and overall TCO of any competing solution.
 http://p.sf.net/sfu/whatsupgold-sd
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Boot from PenDrive with Data...

[Alain Mouette]

Hi,

I need to make an install Pendrive for FreeDOS and a program of mine.

Today I have a CDROM setup woking this way: it boots from the Cd using a 
floppy image which has a CD driver and I read the program from that CD.

I could read the program from anywhere, but it needs to be 15Mbytes, 
what is the best way that will work on any machine?

Alain

--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FDISSK bug?

[Alain Mouette]

Hi all,

A user reported to me that for some HardDisks FreeDOS's FDISK is not 
able to set the ACTIVE bit for the boot partition...

Has anyone encountered this problem? is there a fix?

I am using fdisk131.zip (fdisk.exe is 39153 bytes)

Thanks for any info,
Alain

--
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web.   Learn how to 
best implement a security strategy that keeps consumers' information secure 
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl 
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] sata II

[Alain Mouette]

It is working for the newest stable kernel :)

Alain

Em 21-10-2010 01:34, kurt godel escreveu:
 Come to think of it, when I made a jumbo rescue disk including freedos,
 I did have to use
 the sata type drivers for the optical(CD), but not for the hard
 drive;freedos could not see
 the sata in that case. Richard Klein

--
Nokia and ATT present the 2010 Calling All Innovators-North America contest
Create new apps  games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] doing graphics

[Alain Mouette]

Em 24-08-2010 03:28, dos386 escreveu:

 I would like to know what is the C equivalent of SCREEN 12.

 There is none.

Yes there is... 12 is the parameter to a BIOS call setting video mode. 
In fact, IIRC it is a set of 4 BIOS calls to be done in a row.

There are a few documented examples to change number of lines in DOS 
using BIOS direct access.

Alain

--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] doing graphics

[Alain Mouette]

Em 20-08-2010 01:15, Christian Masloch escreveu:
 Has anyone used any of them in DOS?
 Yes. That is, I heard of people using them successfully. But I believe
 Yes is an adequate answer to your question.

As a matter of fact, that is not a very usefull answer... I would like 
to know from anyone using which one, how to use it, if it works on all 
machines, that kind of stuff :)

Alain

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] doing graphics

[Alain Mouette]

Em 19-08-2010 16:15, Robert Riebisch escreveu:
 Alain Mouette wrote:
 I would like very much to have a libray for that :)

 Q10. What libraries are available for WATCOM C/C++?
 http://www.azillionmonkeys.com/qed/watfaq.shtml#7

Has anyone used any of them in DOS?

Thanks for the link,
Alain

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] doing graphics

[Alain Mouette]

Em 17-08-2010 16:04, Christian Masloch escreveu:
 And check your compiler's docs for what kind of graphics are supported...

 I.e. check your libraries. Or get some graphics libraries for DOS or DPMI.

EVERY modern computer suports VESA in 800x600 (I have lots of them 
running) and 1024x768 (not tested, but is the same driver)

I would like very much to have a libray for that :)

Alain

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Dualboot with Knoppix?

[Alain Mouette]

Knopix is a bit old, but I usualy dualboot with Ubuntu. This is the easy 
path:

* FreeDOS should be in the first primary partition (sda1)
* the partition should be set active.
* Use grub, Ubuntu configures it automaticaly, but calls it windows

FreeDOS will not boot from extended partitions, and there are 
*sometimes* problems with other primary partitions (but I have done it)

Alain

Em 11-08-2010 19:20, david lowe escreveu:
 Has any FreeDOS user ever dualbooted with Knoppix (DSL)?

   From: freedos-user-requ...@lists.sourceforge.net
   Subject: Freedos-user Digest, Vol 382, Issue 1
   To: freedos-user@lists.sourceforge.net
   Date: Sun, 8 Aug 2010 13:01:57 +
  
   Send Freedos-user mailing list submissions to
   freedos-user@lists.sourceforge.net
  
   To subscribe or unsubscribe via the World Wide Web, visit
   https://lists.sourceforge.net/lists/listinfo/freedos-user
   or, via email, send a message with subject or body 'help' to
   freedos-user-requ...@lists.sourceforge.net
  
   You can reach the person managing the list at
   freedos-user-ow...@lists.sourceforge.net
  
   When replying, please edit your Subject line so it is more specific
   than Re: Contents of Freedos-user digest...
  
  
   Today's Topics:
  
   1. Re: Recommondation of TCP/IP stack, DHCP client (Someone)
   2. Re: Recommondation of TCP/IP stack, DHCP client (Mike Eriksen)
   3. Re: Recommondation of TCP/IP stack, DHCP client (Ulrich Hansen)
   4. Re: Recommondation of TCP/IP stack, DHCP client (4625)
   5. Re: Recommondation of TCP/IP stack, DHCP client (4625)
   6. Re: Recommondation of TCP/IP stack, DHCP client (Ulrich Hansen)
   7. Re: Recommondation of TCP/IP stack, DHCP client (4625)
   8. Re: Recommondation of TCP/IP stack, DHCP client (Ulrich Hansen)
  
  
   --
  
   Message: 1
   Date: Fri, 06 Aug 2010 19:53:35 -0700
   From: Someone plu...@robinson-west.com
   Subject: Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP
   client
   To: freedos-user@lists.sourceforge.net
   Message-ID: 1281149616.24338.100.ca...@goose.robinson-west.com
   Content-Type: text/plain
  
  
   On Fri, 2010-08-06 at 23:10 -0300, Alain Mouette wrote:
I completly disagree.
   
Just today I installed FreeDOS on a brand new Asus board with SATA2 a
gigabit ethernet chip.
   
Simple: go to www.netbootdisk.com and create a floppy. After it boots
and detects the NIC, copy it's driver including packet driver. Easy...
   
The truth is that if you have an application that is worth using with
FreeDOS, drivers exist :)
   
And it is damn fast
   
Alain
  
   Command line Linux tuned properly is also fast where Linux supports more
   network cards than Freedos does. Another problem, how did you find out
   that there is a driver for your particular card? For Linux users, the
   kernel supports a lot of network cards straight off.
  
   Does Freedos support common nics such as:
  
   Netgear Fa311/Fa312?
  
   Thuderlan dual port 10/100 nics?
  
   AOpen nics?
  
   Tulip nics?
  
   Other nics?
  
   I stand by my statement that TCP/IP and DOS are probably not the best
   combination. DOS does not protect the hardware from programs that
   execute, because it can't. DOS cannot stop viruses/worms very easily
   because it doesn't shield the hardware in the first place. This is
   all the more reason to avoid connecting to global networks from a
   DOS based environment.
  
   How about DOSbox, Virtualbox, and VMWARE nics? Can Freedos use any
   virtual NICS?
  
  
  
  
   --
  
   Message: 2
   Date: Sat, 7 Aug 2010 12:32:20 +0200
   From: Mike Eriksen thinstation.m...@gmail.com
   Subject: Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP
   client
   To: freedos-user@lists.sourceforge.net
   Message-ID:
   aanlktimx31etkdoc4_4srppfww_ycdpr1t59mg__-...@mail.gmail.com
   Content-Type: text/plain; charset=ISO-8859-1
  
   On Sat, Aug 7, 2010 at 3:22 AM, Someone plu...@robinson-west.com wrote:
I question whether TCP/IP is the best way to go in a DOS environment.
  
   That depend on your needs. Been a member of the Thinstation Linux thin
   client team, I have all the lightweight Linux I could wish. My
   original need came from the need to BIOS upgrade a floppyless Ubuntu
   box. I ended up by adding the DOS flash program and the BIOS image to
   a Balder image, make an ISO of it and problem solved. Not very
   elegant. So I decided to explore if I could make a boot floppy with
   USB support so I could put the flash program and BIOS image on a
   writable device and not have to create a new ISO every time (not that
   it happens often, but now it got a pet project).
  
   Having reached this, I wanted more: the ability to download the flash
   program and the image directly with wget or even a text browser. This
   is a bit hard to accomplish without TCP/IP :-) I've put the network
   stack, applications

Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP client

[Alain Mouette]

As I said: www.netbootdisk.com detects and installs the correct driver.

Alain

Em 06-08-2010 23:53, Someone escreveu:
 On Fri, 2010-08-06 at 23:10 -0300, Alain Mouette wrote:
 I completly disagree.

 Just today I installed FreeDOS on a brand new Asus board with SATA2 a
 gigabit ethernet chip.

 Simple: go to www.netbootdisk.com and create a floppy. After it boots
 and detects the NIC, copy it's driver including packet driver. Easy...

 The truth is that if you have an application that is worth using with
 FreeDOS, drivers exist :)

 And it is damn fast

 Alain

 Command line Linux tuned properly is also fast where Linux supports more
 network cards than Freedos does.  Another problem, how did you find out
 that there is a driver for your particular card?  For Linux users, the
 kernel supports a lot of network cards straight off.

 Does Freedos support common nics such as:

 Netgear Fa311/Fa312?

 Thuderlan dual port 10/100 nics?

 AOpen nics?

 Tulip nics?

 Other nics?

 I stand by my statement that TCP/IP and DOS are probably not the best
 combination.  DOS does not protect the hardware from programs that
 execute, because it can't.  DOS cannot stop viruses/worms very easily
 because it doesn't shield the hardware in the first place.  This is
 all the more reason to avoid connecting to global networks from a
 DOS based environment.

 How about DOSbox, Virtualbox, and VMWARE nics?  Can Freedos use any
 virtual NICS?


 --
 This SF.net email is sponsored by

 Make an app they can't live without
 Enter the BlackBerry Developer Challenge
 http://p.sf.net/sfu/RIM-dev2dev
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP client

[Alain Mouette]

A sI said, I just installed a FreeDOS machine with those realtec drivers 
las week,

Using www.netbootdisk.com

Alain

Em 07-08-2010 17:16, Ulrich Hansen escreveu:
 Am 07.08.2010 03:22, schrieb Someone:
 Command line linux is much easier to network than freedos and there is a
 lot of utility to it.

 You are right. There is no doubt that GNU/Linux is much better
 equipped for networking than (Free)DOS. GNU/Linux also runs on old
 hardware, although it can be difficult (and painfully slow) to
 install. Modern installers need a lot of resources. I run Debian (Dual
 boot with FreeDOS) on some 486SX with 20 MB RAM so I know something
 about that.

 Companies aren't releasing dos drivers

 This is not necessarily true. Two weeks ago we had a discussion about
 drivers for the RTL8101E/RTL8102E PCI Express Fast Ethernet controller
 in a quite modern Acer Aspire One netbook. As we found out, Realtek
 still released ODI (Netware) and NDIS (MS Client for DOS) drivers for
 that NIC, so it can be used with shims as packet drivers for
 networking in FreeDOS.

 So even when some companies do not release packet drivers for DOS, the
 NIC might be still usable.

 I question whether TCP/IP is the best way to go in a DOS environment.

 You are right. Security is an issue. ftpsrv32.exe for instance - one
 of the few FTP servers that exist for DOS - doesn't ask for a password
 and opens the whole DOS system for guests. And if you are using WLAN
 in DOS, you are limited to 802.11b cards with WEP encryption, which is
 insecure per definition.

 On the other hand, most TCP/IP networking software in DOS cannot run
 as TSR. It runs fullscreen in the foreground, which is hard to ignore.
 So there are no ports unintentionally open. And if you are running a
 server in DOS you are at least not running anything else.  ;-)

 For security reasons, most of us probably don't want
 our DOS environments to connect directly to the Net, but for
 gaming purposes, local area networking can be quite fun.

 Gaming is one possible purpose of networking DOS machines. Another
 reason may be the need to run old DOS software that has to have
 network access.

 But I think the most important reason people have to network (Free)DOS
 is simply to be able to exchange data.

 Modern computers don't have floppies, parallel or serial ports. Old
 computers don't have USB or SD-cards. Some old computers have CD-Rom
 but burning CDs for data exchange can be annoying, as Mike Eriksen
 pointed out.

 TCP/IP for DOS has been around since the eighties, so it is the common
 ground for old and new hardware, for DOS and a more modern OS.

 Just as example: How do I myself exchange data between FreeDOS on my
 old 486SX laptops and my modern Thinkpad running Ubuntu Lucid? By
 starting a ftp server in freedos and logging in with filezilla. How
 else could I do this? By loading MS Client and creating a shared
 directory.

 How about DOSbox, Virtualbox, and VMWARE nics?  Can Freedos use any
 virtual NICS?

 I installed FreeDOS in Virtualbox last week. Virtualbox uses a AMD
 PCnet-Fast III card. A free packet driver pcntpk.com for this card
 is available at:
 http://www.crynwr.com/drivers/amdpd.zip

 For MS Client you can get the NDIS driver pcntnd.dos at:
 ftp://ftp.dlink.com/NIC/de520/Driver/uncompressed/MSLANMAN.DOS/DRIVERS/ETHERNET/PCNTND/

 In Virtualbox the only way to exchange data between the FreeDOS guest
 and the host (Ubuntu in my case) is to create a network: I use the
 vbox network adapter in bridged mode. In the FreeDOS guest I run a DOS
 server in my LAN (behind a router of course) and connect to it from
 the Ubuntu host with filezilla. I also connected the FreeDOS guest
 with a scond Virtualbox guest running Windows XP via MS Client in DOS.

 So yes, you are right: TCP/IP and DOS are probably not the best
 combination.
 And no, you are not right: Networking DOS via TCP/IP is still needed
 for many reasons.

 --
 This SF.net email is sponsored by

 Make an app they can't live without
 Enter the BlackBerry Developer Challenge
 http://p.sf.net/sfu/RIM-dev2dev
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Recommondation of TCP/IP stack, DHCP client

[Alain Mouette]

I completly disagree.

Just today I installed FreeDOS on a brand new Asus board with SATA2 a 
gigabit ethernet chip.

Simple: go to www.netbootdisk.com and create a floppy. After it boots 
and detects the NIC, copy it's driver including packet driver. Easy...

The truth is that if you have an application that is worth using with 
FreeDOS, drivers exist :)

And it is damn fast

Alain

Em 06-08-2010 22:22, Someone escreveu:
 I'd say that Freedos is okay for networking if you have a card that is
 supported by open source drivers, but that seems to be a very short list
 of cards at this time.  I guess the question to ask of anyone seeking to
 network Freedos is, is a dos environment enough for what you are after?
 Command line linux is much easier to network than freedos and there is a
 lot of utility to it.  I don't foresee a strong effort to get free
 network driver support to track with today's gigabit and 10 gigabit
 built-in and PCI cards.  Companies aren't releasing dos drivers for the
 most part anymore because Microsoft isn't supporting DOS.  This is a
 shame, Microsoft shouldn't have to support an OS for that OS to be
 popular.

 I question whether TCP/IP is the best way to go in a DOS environment.
 Local area only networking with special filtering gateways to deal with
 remote data and remote access makes more sense security wise than
 hooking DOS directly to the Net via TCP/IP.  What is your application?
 Are the DOS based clients seen as single user terminals hooked to a
 central network server that handles authentication, routing, providing
 network services, etcetera?  Are DOS based clients going to access each
 other for services?

 Novell's Netware, up until the company gave up and went to a TCP/IP
 based system, was a local area network system.  There are many
 disadvantages to running the same protocol that the Internet runs for
 local area networking.  First problem that strikes immediately is
 addressing.  Where IPV6 is supposed to help, most people don't have
 IPv6 equipment where IPv6 is unheard of in DOS environments.  Even
 so, IPv6 is just a band-aid measure if globally unique IP addresses
 continue to be given out thoughtlessly.

 Services like DNS, dhcp, etcetera don't seem to be designed to
 distinguish between a local verses a remote source.  Routing is
 overly complicated if a private network is TCP/IP based.  Say I
 assume that the .home or the .pri domain are not used on the Net.
 Maybe I think that .cox isn't used.  There is no way to set DNS
 up to distinguish a local use of .foo when there is the
 possibility of a remote usage of foo.  Where there is name
 collision, how do you sort that out?  If you know you are looking
 for local resolution of a name and there is some way to indicate
 that in a standard manner, problem solved.  Reality is, .foo which
 is not in use in Internet names today could be used tomorrow.
 Other problems come into play when you search by host name and
 failing to add the private domain name leads to an erroneous
 name resolution.  There seems to be no standard for naming private
 TCP/IP based networks that are occasionally Net connected.  Some people
 say use your global domain name on your private hosts.  Other people
 say, buy two domain names and use one of them for the private hosts.
 Still others say, use a .cox, .pri, .home, or some .foo that is not
 in use on the Internet.  All of these options have serious drawbacks.

 Using your global domain name on private hosts that may never touch
 the Net, you can't use those host names twice.  Using a second
 globally registered domain for private hosts reduces the global
 name space.  Trying to guess that domain foo will never be used
 on the Internet, there are no standard choices which means that
 the domain you choose could be adopted at any time.  IPv6 doesn't
 help, most people can't implement IPv6 and even if you can, IPv6
 only increases the number of addresses without providing a way
 to let people reuse names/overlap names.  The strings people come
 up with to name IP addresses can only be so long before it becomes
 easier to simply type in the number.  I'm afraid that the naming
 convention in use 10 years from now will be a gross patch on top
 of what we do now.

 DOS environments are incapable of protecting the hardware as the kernel
 is NOT a layer around the hardware.  QDOS stood for quick and dirty
 operating system and people should realize that DOS was never intended
 for a networked environment.  DOS combined with an IPX/SPX network is
 interesting, but Netware is totally proprietary.

 Look at mailing addresses in the U.S.  There are city level unique zip
 codes, at least 10^5 or 100k possibilities.  That is assuming that all
 zip codes are maximum 5 digits long (which probably isn't true).  Look
 at the street level though and chances are you can find an Elm street
 for example in 100's of places.  The combination of street name, street
 address, and zip code will always be 

Re: [Freedos-user] How to use dd included in freedos 1.0 to save/restore the MBR

[Alain Mouette]

fdisk does that, type: fdisk /?

Alain

Em 21-07-2010 07:17, Thomas Jung escreveu:
 Hello,

 how can I use the dd command from/within
 freedos to save or restore thr MBR?

 How do I have to name the devices?

 Think it can't be like the linux/unix syntax:

 dd if=/dev/sda of=/def/fd0/mbr.dat bs=512 count=1

 btw: I know this list contains the word emulators and
 think dd don't work in a VM, but I have installed freedos
 in the first primary partition on my harddisk and hope
 here are some nerds and/or developers who knows that.

 T.

--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] How to Disk-Controller Firmware From FreeDOS?

[Alain Mouette]

inserting the file you want in the image is an option, if it fits...

The normal way is to create a floppy with a CD driver, test it, use it 
a boot image and write the files as normal CD content. After boot the cd 
driver will have been loaded and the CD content will be available as D: 
(or whatever x:)

Alain

Em 19-07-2010 18:01, Jonathan B. Horen escreveu:
 Of all the crazy things in the world...

 I've got a Silicon Mechanics storage unit, with nineteen 2TB WD drives
 that need to have their firmware updated, and I've got the update: yup,
 an MSDOS executable file. The storage unit, itself, runs a modified
 version of Linux, with the 2.6.27 kernel, from Open-E.

 I thought about booting the SM unit from FreeDOS on a USB thumb drive,
 but the 3ware RAID card is in the way :(

 So, I burned the FreeDOS/1.0 image onto a CDROM on a spare cluster node
 (after first pulling the node's hard drive and replacing it with one of
 the storage unit's RAID drives) -- worked fine. However, I found that
 FreeDOS/1.0 doesn't support USB (other than as boot devices) :(

 How to access and run the disk-firmware update executable?

 I thought about patching the FreeDOS/1.0 image (that is, including the
 firmware-update executable so that it will be available after booting),
 but I have no idea how to do it.

 Advice? Suggestions? Instructions?

 I'm listening...

 --
 JONATHAN B. HOREN
 Systems Administrator
 UAF Life Science Informatics
 Center for Research Services
 (907) 474-2742
 jbho...@alaska.edu mailto:jbho...@alaska.edu
 http://biotech.inbre.alaska.edu



 --
 This SF.net email is sponsored by Sprint
 What will you do first with EVO, the first 4G phone?
 Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first



 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user

--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Desperately need help with insalling VMware 7 help would be GREAT

[Alain Mouette]

Em 13-07-2010 21:43, dos386 escreveu:

 FYI, I'm the only person in the universe who installed FreeDOS __NATIVELY__ 
 :-)

Nope...

I have a few, and I have clients that use FreDOS natively 24/7 for 
security systems :)

I offer them support 24/7 and I sleep very very well :) :)

Alain

--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Installing FreeDOS without the boot loader?

[Alain Mouette]

What you probably did was to boot with the Win98 partition as active.

You have to change the active partition before booting FreeDOS for 
instalation. This will define the correct C: for the instalation, even 
if it shows invalid because it is not formated.

Alain

Em 15-06-2010 07:21, kellybe...@gwi.net escreveu:
 I think the problem was caused by metakern in FreeDos.  Its possible that I 
 accidently installed the FreeDOS onto the same partition as Windows 98 rather 
 than the partition that I created for it, and therefore metakern created the 
 freedos boot loader in the partition's boot record.  Since I've since 
 reimaged the Win98, I don't know for sure but I don't know of any other 
 explanation for it.

 I've used the same Grub configuration you pointed out and it does work well 
 for this purpose.  I am just trying to understand what FreeDOS did the last 
 time I installed it.   The easier thing for me to do, I think, would be to 
 just boot into the live CD, run it from the command line, confirm each 
 partition, and then proceed with the installation.

 Original Message-
 From:Alain Mouetteala...@pobox.com
 To:  kellybe...@gwi.net
 Subject: Re: [Freedos-user] Installing FreeDOS without the boot 
 loader?
 Date:Monday, June 14, 2010 9:57 PM
 
 I think that you are a bit confused. Instalin freedos in another primary
 partition dos nor afect the Win98 partition in any maner except by
 instalation errors.
 
 The reason why it keeps booting win98 it because that partition is
 *active* change that with fdisk (or whatever) and FreeDOS boots.
 
 Have you tried my grub config? it has a command do change exactly that.
 
 Alain
 
 Em 14-06-2010 22:01, kellybe...@gwi.net escreveu:
   Thank you Eric and Alain for your response.  I've had pretty good 
 luck in the past with booting FreeDOS with Grub.  My question involves more 
 of the process during which FreeDOS is installed.
 
   Until recently, I never had any problems installing FreeDOS.  
 However, recently I tried installing it on a machine that had Windows 98 
 (hda1) and Debian Linux (hda2).  I created a primary HDA4 partition and 
 formatted it as a FAT partition.  I installed FreeDOS to this partition, but 
 after that point, everytime I booted into Windows 98, I initially received a 
 FreeDOS boot menu after Grub booted me into the Win98 partition.  I located a 
 file in the root directory of Windows 98, and when I tried altering that 
 file, it made the Win98 partition unbootable.  I have since reimaged the 
 Windows 98 partition back to its prior state using dd, but I'd like to try 
 FreeDOS one more time.  It seems that FreeDOS created a boot manager in the 
 boot record of the Windows 98 partition, and I'd like to avoid  that from 
 happening, if at all possible.
 
 
   Original Message-
   From:Eric Auere.a...@jpberlin.de
   To:  freedos-user@lists.sourceforge.net
   Subject: Re: [Freedos-user] Installing FreeDOS without 
 the boot loader?
   Reply-To:freedos-user@lists.sourceforge.net
   Date:Monday, June 14, 2010 4:37 PM
   
   
   Hi Alain, Eric,
   
  FreeDOS does not need anything from the Win98 partition to 
 boot.
 The requisites are:
   
  1) it must boot from a primary partition
  2) the partition needs to be active.
   
   Not really... Because you use GRUB, it is enough if you have
   a valid boot sector in a FILE. Our SYS can make such files,
   without actually SYSing your partition. So Windows stays as
   it is, and you give the file to GRUB as the chainloader. You
   just state the filename instead of the +1 to make the DOS
   menu item, which for the rest is a copy of the Windows one.
   
   Example GRUB menu.lst snippet - GRUB 2 might differ a bit:
   
   # on /dev/sda1
   title   FreeDOS
   root(hd0,0)
   # savedefault
   chainloader /freedos.bot
   
   # on /dev/sda1
   title   Windows
   root(hd0,0)
   # savedefault
   chainloader +1
   
   To make this work, you generate a freedos.bot file in the
   root directory of the C: drive of Windows, using our SYS:
   
   sys c: c:\freedos.bot bootonly
   
   The bootonly stops SYS from copying kernel.sys and
   command.com of FreeDOS to C: - instead, you can copy
   our kernel.sys to the root directory of C: manually.
   
   Do NOT copy command.com to that place! You might mix
   it with the Windows one otherwise. Instead, put it
   

Re: [Freedos-user] Installing FreeDOS without the boot loader?

[Alain Mouette]

Hi

FreeDOS does not need anything from the Win98 partition to boot. The 
requisites are:
1) it must boot from a primary partition
2) the partition needs to be active.

Windows98 have the same requisites, that is the problem. But it can be 
solved by Grub.. This is how I did it:

# This entry for FreeDOS on /dev/sda1
title   FreeDOS
root(hd0,0)
savedefault
makeactive
chainloader +1


# This entry for Windows98 on /dev/sda2
title   Windows 95/98/Me
root(hd0,1)
savedefault
makeactive
chainloader +1

Notice the makeactive command that changes the active partition 
on-the-fly. But you will still need both to be primary partitions, only 
a few programs can achieve this, sorry but I don't remember which, 
probably PartedMagic http://partedmagic.com/ is ok. (it can move 
partitions too)

Alain


Em 13-06-2010 20:33, Eric escreveu:
 Is it possible to install FreeDOS 1.0 on a Windows 95/98 machine without
 it installing the boot loader into the Windows 98 partition?

 I have an old laptop with Windows 98 and Linux.  I use Grub to
 multiboot, so I don't need the FreeDOS boot loader, and don't want to
 interfere with the Win98 partition.

 I realize (1) Win98 has its own DOS, I just want to play with FreeDOS,
 and (2) I could just sys the FreeDOS partition, but I'd rather use the
 FreeDOS installer if possible.

 Thanks.

--
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Installing FreeDOS without the boot loader?

[Alain Mouette]

This explanation by Eric Auer may be a little confusing, but note one 
thing: This is for having *both FreeDOS and Win98 in the same partition* 
but I am not sure if that is what was asked.

In any case, I found very interesting this dual method :)

Alain

Em 14-06-2010 17:37, Eric Auer escreveu:
 Hi Alain, Eric,

 FreeDOS does not need anything from the Win98 partition to boot.
 The requisites are:

 1) it must boot from a primary partition
 2) the partition needs to be active.

 Not really... Because you use GRUB, it is enough if you have
 a valid boot sector in a FILE. Our SYS can make such files,
 without actually SYSing your partition. So Windows stays as
 it is, and you give the file to GRUB as the chainloader. You
 just state the filename instead of the +1 to make the DOS
 menu item, which for the rest is a copy of the Windows one.

 Example GRUB menu.lst snippet - GRUB 2 might differ a bit:

 # on /dev/sda1
 title   FreeDOS
 root(hd0,0)
 # savedefault
 chainloader /freedos.bot

 # on /dev/sda1
 title   Windows
 root(hd0,0)
 # savedefault
 chainloader +1

 To make this work, you generate a freedos.bot file in the
 root directory of the C: drive of Windows, using our SYS:

 sys c: c:\freedos.bot bootonly

 The bootonly stops SYS from copying kernel.sys and
 command.com of FreeDOS to C: - instead, you can copy
 our kernel.sys to the root directory of C: manually.

 Do NOT copy command.com to that place! You might mix
 it with the Windows one otherwise. Instead, put it
 in a separate directory, for example c:\freedos\ :-)



 Note that SYS cannot (as far as I remember) make good
 boot sectors for non-primary partitions. However, if
 you use e.g. my Linux oriented sys-freedos.pl, you
 can add manual correction to boot even non-primary.

 Because this micro howto explains how to make FreeDOS
 share the primary C: partition with Windows, you do not
 need to worry about non-primary. SYS works fine with a
 partition where Windows 98 can boot from. Note that XP
 is a different story - NTFS partitions are not for DOS.

 Now you are almost ready to boot FreeDOS via GRUB. You
 will probably want that Windows and DOS do _not_ share
 the same config.sys, and luckily FreeDOS makes it easy
 for you: Simply create a file fdconfig.sys in the root
 directory of C: and put your DOS configuration there.
 FreeDOS will only read config.sys if it cannot find a
 fdconfig.sys file... You can even keep your autoexec
 bat separate as well. For that, your fdconfig.sys must
 have a shell line similar to this:

 SHELL=C:\freedos\command.com C:\freedos /E:1024 /P=C:\freedos\start.
 bat

 The start bat file in the freedos directory is now
 used in the same way as you would normally use the
 autoexec batch file. With those tricks, you keep all
 the FreeDOS configuration and boot files separately
 from the Windows ones. You only add three files to the
 root directory (kernel.sys, fdconfig.sys, freedos.bot)
 which are not in the way for Windows, and put all other
 FreeDOS files in your freedos directory.

 When you install more parts of FreeDOS, you often have
 a directory structure where the main directory is for
 example c:\fdos and programs are in c:\fdos\bin...

 For a somewhat newer floppy image (actually up to three
 depending on how much you want) with updated FreeDOS
 software, check http://sites.google.com/site/rugxulo/
 (you can also download zips instead of images if you
 simply want the files and do not use actual floppies)

 Notice the makeactive command that changes the active partition
 on-the-fly. But you will still need both to be primary partitions, only
 a few programs can achieve this, sorry but I don't remember which,
 probably PartedMagichttp://partedmagic.com/  is ok. (it can move
 partitions too)

 Sounds complicated ;-)

 Cheers, Eric


--
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Running FreeDOS in an emulator

[Alain Mouette]

I have already used FreeDOS in VirtualPC, it works just as expected.

Network is more tricky, you have to find the correct packet driver.

Alain

Em 10-06-2010 12:20, Bruce M. Axtens escreveu:
 Dear List

 Can anyone give me a hand with running FreeDOS under an emulation. I've
 got both VirtualPC and Sun VirtualBox and I can't seem to get it right
 with the settings for DHCP. What network hardware and software settings
 should I be using? I'm running under Windows Server 2008 but using it as
 a single user O/S (it's a long story.)

 Kind regards,
 Bruce.

--
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Running FreeDOS in an emulator

[Alain Mouette]

Em 10-06-2010 16:41, Robert Riebisch escreveu:
 Bruce M. Axtens wrote:

 Can anyone give me a hand with running FreeDOS under an emulation. I've
 got both VirtualPC and Sun VirtualBox and I can't seem to get it right
 with the settings for DHCP. What network hardware and software settings
 should I be using? I'm running under Windows Server 2008 but using it as
 a single user O/S (it's a long story.)

 For Virtual PC you need this DOS network driver:
 http://developer.intel.com/design/network/drivers/nd2_300.htm

This is NOT a Packet-Driver, it works only for M$-client. If that is 
what you want, you can try www.netbootdisk.com

For FreeDOS utilities you will need a Packet Driver

Alain

--
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Zorland/Zortech C compiler?

[Alain Mouette]

Em 28-05-2010 08:46, Jim Lemon escreveu:
 I have been using the Borland C compiler for some years, but ran into a
 problem with version 1.0 of FreeDOS. Since I upgraded from 0.9something,
 the IDE can no longer find libraries or object files that are not in the
 current directory, nor can I manually compile and link. I have managed
 to work around this by transferring a minimal subset of the Borland C
 installation to an old laptop that is still running 0.9something, but
 this is hardly an ideal solution. Do you have any information that might
 allow me to get Borland C to work under FreeDOS 1.0 and beyond? Thanks.

I use Borland C 3.1 regularly on FreeDOS... have you tryed to configure 
the the lib directories in the IDE?

Alain

--

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] any port of top command from linux/*nix available?

[Alain Mouette]

Why would there be a top commando for FreeDOS? as it runs one program at 
a time...

But there is a way to see what is in memory:

MEM /U

Alain

Em 21-05-2010 20:29, Geraldo Netto escreveu:
 Hi guys,


 i'd like to know if any of you know if
 there is any port of top command?
 i know there is djgpp, but my
 first/fast search didn't find anything useful...

 any help appreciated :)

 See Ya,

 Geraldo

--

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Liam Proven comment

[Alain Mouette]

Em 20-05-2010 01:28, jasse...@itelefonica.com.br escreveu:
 Liam Provenlpro...@gmail.com  wrote:

 Don't try to create 3 primary partitions - in DOS
 terms, that is an illegal layout.

   Interestingly, illegal in MSDOS and PCDOS, but
 both FreeDOS and DRDOS accept this layout (I tested).
   Anyway, shouldn't FDISK make the right layout
 when requested to create multiple partitions?

No it has never been ilegal, and it allways worked just fine. I use 
these since forever... what happend is that most tools did not have a 
way of making them, but if you know how to make them it allways worked 
since MSDOS-3.

The rules of letter attibuting are very strange:
1) the first (sometives the active) partition of each drive
2) all extended partitions from each drive at a time. There were issues 
as to sequences in recurrent extended partitions.
3) all remaining primary partitions of each drive.

There is one restriction: most RD-DOS versions can only boot from the 
first partition, which should of course be primary and active. This is 
just a bug.

Alain

--

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Liam Proven comment

[Alain Mouette]

Em 20-05-2010 15:44, Liam Proven escreveu:

 You have been lucky. I have seen many incorrectly-partitioned systems
 with multiple primaries where some drives were not visible, on various
 versions of MS-DOS and up to Windows 95.

Not Lucky, just hard work. Partitions were invented without entented 
partitions, so it worked from the first...

 It's not a good idea; unpredictable things can happen, such as writing
 to the wrong C drive and causing corruption.

I didn't say that it is easy ;)

 The rules of letter attibuting are very strange:
 1) the first (sometives the active) partition of each drive
 2) all extended partitions from each drive at a time. There were issues
 as to sequences in recurrent extended partitions.
 3) all remaining primary partitions of each drive.

 Wrong way round.

 It is:
   - enumerate all primaries, drive by physical drive

Not at all.

   - then enumerate all logical drives on each physical drive, stepping
 through the drives as each is exhausted

Ok

 It is logical but confusing. Win7 no longer does this at all - the
 boot drive is always C;

That is a definition: boot is allways C:

 if there was an existing DOS-level C, it seems to disappear.

There are lots of bugs in this area.

FYI: I started using PC-DOS 1.1... so I have a long history of dos and 
don'ts...

Alain

--

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user