Re: [Freedos-user] cannot boot installation media (test Bodhi Linux over Ventoy)

[Paul Dufresne via Freedos-user]

I realized after post that the link to TinyCore I had given is mark as not 
secure under Firefox. (not distributed over https)
(I don't believe it to be much dangerous) but wanted to give an alternative.
So I tested (on Ventoy USB key): 
https://psychz.dl.sourceforge.net/project/bodhilinux/5.1.0/bodhi-5.1.0-legacy.iso?viasf=1
It is 747 Mo however... and when I boot it, screen get borked, then I see a TPM 
error, then bork again, then
black, then a bad web browser page appears with local help, that works for 
FreeDOS but would say we are
offline on Youtube.

But as it is just to make sure you can boot something... it should do.



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

Re: [Freedos-user] cannot boot installation media

[Paul Dufresne via Freedos-user]

I suggest:

https://ventoy.net/en/index.html

(one of the advantage of Ventoy, is that in lower left, it shows if it booted 
in Clasic mode, or in UEFI mode)

Use it to make your USB key "Ventoy"

Try it by copying 
http://www.tinycorelinux.net/15.x/x86/release/TinyCore-current.iso (only 23 Mb) 
onto it.

Now I suggest you stop trying to install with the USB image, and rather copy 
the iso image inside of:



https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.3/official/FD13-LiveCD.zip



Copy the iso file also on the Ventoyify USB key.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] networking over 86box

[Paul Dufresne via Freedos-user]

 Le Wed, 24 Apr 2024 16:05:10 -0400 Brandon Taylor via Freedos-user  a 
écrit 
 > My apologies for the confusion. I know FreeDOS has internet capability, but 
 > not on 86Box, since FreeDOS for some reason treats 86Box as if it were a 
 > real computer.
 > 
 > GetOutlook for Android
 > From: Robert Riebisch via Freedos-user freedos-user@lists.sourceforge.net>
 >  Sent: Wednesday, April 24, 2024 2:04:17 PM
 >  To: freedos-user@lists.sourceforge.net freedos-user@lists.sourceforge.net>
 >  Cc: Robert Riebisch r...@bttr-software.de>
 >  Subject: Re: [Freedos-user] Dial-up emulation?  
 > Hi Brandon,
 >  
 >  > Since FreeDOS doesn't support physical network hardware (even if it's
 >  > emulated in a program like PCem or 86Box), I figure there's no way
 >  > FreeDOS is gonna be able to connect to the Internet, right? Well...
   
Frankly, using networking over 86box seems harder than on QEMU... where I have 
posted some weeks ago
the line I use to have the networking emulated.

You would need to read: 
https://86box.readthedocs.io/en/latest/hardware/network.html
that shows that the default is to drop all network information.

Slirp seems easier to select but not really what you want (because it seems to 
request a program to connect to internet)

pCap seems  what you would want... but then need some additional program than 
86box.


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

[Freedos-user] Ré : Way or utility in Freedos to have two applications running

[Paul Dufresne via Freedos-user]

 Le mer., 10 avr. 2024 06:33:38 -0400 Ramon Riera Marès via Freedos-user  a 
écrit 

> First of all, thanks to all the Freedos developers and collaborators.  I want 
> to know if there is any way or utility in Freedos to have
>  two applications running, for example an outliner and a text editor, and be 
> able to switch from one to the other without having to
> exit the current application.  Thanks and regards.  Ramon Riera.

It is possible, but very hard to write, because DOS is not reentrant:
https://en.wikipedia.org/wiki/Reentrancy_(computing)

DOS have a call to quit a program, but leaving it in memory Terminate Stay 
Resident (TSR).
But such programs must respect special rules to avoid DOS to crash.

There was a program, DESKVIEW, that was making an OS that was reentrant... as 
far as I understand,
that was running over a DOS. Making it easy to have more than one program 
running at a time.
See https://en.wikipedia.org/wiki/DESQview

I don't know how hard it would be to make FreeDOS reentrant... or what was the 
recent infos as
I am mostly basing the info I give here to what I learns in the nineties.


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

Re: [Freedos-user] FreeDOS install

[Paul Dufresne via Freedos-user]

https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/FDT2404-LiveCD.zip
worked for me (in QEMU).
I have chosen 'Install to hard disk' from the main menu.

Do you install in english?

Have you verified the file with 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/verify.txt
 ?
You could use https://www.winmd5.com/ ... 

Maybe try with VirtualBox: 
https://download.virtualbox.org/virtualbox/7.0.14/VirtualBox-7.0.14-161095-Win.exe


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

Re: [Freedos-user] How to try FDT2404 (Latest test version) on QEMU the hard way + kvm fixed

[Paul Dufresne via Freedos-user]

It turn out that using kvm was giving me the illusion of using kvm... but I 
missed the warning saying
that kvm was not loaded, and that it was falling back on tcg  don't know 
really what it is.
The reason was that "Intel virtualization technology" option in "BIOS" was 
disabled.
After enabling it, now qemu-system-i386 -enable-kvm works... I hope for real.
So qemu-system-i386 -enable-kvm make it more obvious that you need to fix 
something than by using kvm.

Also... it seems that setup need the cdrom (dvd) to be working... as it seems 
to install from it.

My guess was that because I was using -machine pc-i440fx-4.2 I was forcing the 
use of cdrom...
Somehow, the cdrom drive was empty, but setup was finding the emulated hard 
disk containing the content of the cdrom...
and used that instead of the cdrom... at least this is my hypothesis why it 
worked, and not anymore now that I don't use -macine.

So now I come back to use 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/FDT2404-LiveCD.zip
instead of 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/FDT2404-FullUSB.zip

I installed with (admittedly more complex than needed):

qemu-system-i386 -enable-kvm -m 32 -cpu 486 -device 
ide-hd,drive=myhd,bootindex=2 -drive 
file=2404.qcow2,format=qcow2,if=none,id=myhd,media=disk -device 
ide-cd,drive=mydvd,bootindex=1 -drive 
file=T2404LIVE.iso,format=raw,id=mydvd,if=none,media=cdrom 

And as this use a menu to choose what to boot with, there is no real need to 
exchange bootindex values.

But to have sound and networking, I just used (added previous message 
parameters to previous line):
qemu-system-i386 -enable-kvm -m 32 -cpu 486 -device 
ide-hd,drive=myhd,bootindex=2 -drive 
file=2404.qcow2,format=qcow2,if=none,id=myhd,media=disk -device 
ide-cd,drive=mydvd,bootindex=1 -drive 
file=T2404LIVE.iso,format=raw,id=mydvd,if=none,media=cdrom -audiodev 
pa,id=mysnd -device sb16,audiodev=mysnd -device adlib,audiodev=mysnd -machine 
pcspk-audiodev=mysnd -vga cirrus -display sdl -net nic,model=pcnet -net user

You can get control back from emulated machine with Ctrl-Alt-G (as shown in 
upper window) and allows you to close the window.

Hope it can help someone while not confusing too many!


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

Re: [Freedos-user] How to try FDT2404 (Latest test version) on QEMU

[Paul Dufresne via Freedos-user]

 Le ven., 05 avr. 2024 11:38:28 -0400 Jerome Shidel via Freedos-user  wrote 


 > Hi Paul,
 > Just a side note about installing using the FullUSB.
 > 
 > One of my DOS test machines is an Acer One netbook with a 1Ghz Atom 
 > processor and an ancient 30Gb SSD. This machine has no CD/DVD drive. It does 
 > boot from the FullUSB when written to a flash drive. It takes about 5 
 > minutes from start to finish (boot, partition, reboot, install, reboot) to 
 > do a Full install without sources. 
 > 
My about 40 mins [did not really check the clock]  in an emulated (kvm) was 
Full install with sources.

Also... using FullUSB just because not liking [understand less] the iso format.
I take/took for granted, that USB key format is the same as an hard disk... so 
used the USB key image on an emulated hard disk.
But I realize that I could use the USB key image on an emulated USB key:
https://qemu-project.gitlab.io/qemu/system/devices/usb.html

 > Although it can only use one at a time, modern versions of FDIMPLES can use 
 > different local package repositories. 
 > 
 > You could have different repos on different drives. Or, even multiple ones 
 > on the same drive in different paths.
 > 
 > When FDIMPLES starts, it checks the current drive for a repository in one of 
 > the standard paths. If it does not find one, it searches existing drives C: 
 > through Z: for a repository. 
 > 
 > You can also tell it to check a specific drive (and/or alternate path) for a 
 > repo at startup. 
 > 
 > For example,
 > 
 > C:\>fdimples e:
 > C:\>fdimples d:\repo-1
 > 
 > etc.  
 > 

So, I guess this tend to suggest the follwing approach for most people: (almost 
obvious, but was not really told to me before)

Have C: be the target hard disk, have D: be the installation disk...

on installation, boot D:  , do a minimal installation, then on usage boot C: 
but with D: present, 
do fdimples D: to add needed packages.

People that need packages only present on Bonus disk should add the E: drive 
with the Bonus image, and use
fdimples e:
to add packages from the bonus disk.


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

Re: [Freedos-user] How to try FDT2404 (Latest test version) on QEMU

[Paul Dufresne via Freedos-user]

 Le ven., 05 avr. 2024 09:52:10 -0400 Jim Hall via Freedos-user  wrote: 

 > Then I create a virtual disk where I can install FreeDOS T2404. I'll
 > set this up as 500MB, which is plenty big for what I do:
 > 
 > $ qemu-img create -f qcow2 2404.qcow2 500M
I was prefering raw, because I was using:
https://www.seei.biz/how-to-mount-raw-images-img-images-on-linux/
to mount raw disk, and exchange data between the host and the emulated machine.

But I discovered qemu-nbd... that allows the same with qcow2 image too.
So I guess I will adopt qcow2.
Now, as I understand, the size of the file for qcow2, is way less than the size 
specified...
because allocation is done only when needed... so I would suggest to oversize 
the value...
maybe 3G?

 > And then I boot the FreeDOS 1.3 LiveCD using QEMU. To install, I don't
 > need much, so I set up FreeDOS to use 32MB memory. I use -enable-kvm
 > with QEMU 8.1.3 on Fedora Linux 39.
On Ubuntu 23.10, with QEMU 
paul@starman:~/FDT2404$ kvm -enable-kvm -m 32 -hda T2404FULL.img
WARNING: Image format was not specified for 'T2404FULL.img' and probing guessed 
raw.
 Automatically detecting the format is dangerous for raw images, write 
operations on block 0 will be restricted.
 Specify the 'raw' format explicitly to remove the restrictions.
Could not access KVM kernel module: No such file or directory
kvm: failed to initialize kvm: No such file or directory

but the following works:
kvm -m 32 -hda T2404FULL.img

paul@starman:~/FDT2404$ qemu-system-i386 --version
QEMU emulator version 8.0.4 (Debian 1:8.0.4+dfsg-1ubuntu3.23.10.3)
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers

https://www.qemu.org/docs/master/system/invocation.html
says: "Older options like -hda are essentially macros which expand into -drive 
options for various drive interfaces. The original forms bake in a lot of 
assumptions from the days when QEMU was emulating a legacy PC, they are not 
recommended for modern configurations."

 > $ qemu-system-i386 -enable-kvm -m 32 -cdrom T2404LIVE.iso -hda
 > 2404.qcow2 -boot order=d
This works with iso file, and d means to boot cdrom... but this means d cannot 
be used to boot with second hard drive ... which is needed when I
choose to use FullUSB image. So I tend to prefer the "new way":

"Instead of -hda, -hdb, -hdc, -hdd, you can use:
qemu-system-x86_64 -drive file=file,index=0,media=disk
qemu-system-x86_64 -drive file=file,index=1,media=disk
qemu-system-x86_64 -drive file=file,index=2,media=disk
qemu-system-x86_64 -drive file=file,index=3,media=disk "

"qemu-system-x86_64 -drive if=ide,index=1,media=cdrom"

"index=index
This option defines where the drive is connected by using an index in the 
list of available connectors of a given interface type.
 compare with bootindex=index later in this message.

media=media
This option defines the type of the media: disk or cdrom."

So rather than -boot order=d I would prefer to use:
https://www.qemu.org/docs/master/system/bootindex.html

I was saying than rather to use mount -o loop,offset= line to mount RAW images, 
it is probably better to use:
https://gist.github.com/shamil/62935d9b456a6f9877b5
that works with qcow2.
That was not working on VanillaOS... but seems to work on Ubuntu 23.10.
(bit unclear when you need to use sudo on these lines)...
https://www.baeldung.com/linux/mount-qcow2-image might be clearer.

So... I was using the same arguments you use... but try to change to more 
modern parameters, because of deprecation warnings/messages.


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

[Freedos-user] Ré : How to try FDT2404 (Latest test version) on QEMU

[Paul Dufresne via Freedos-user]

--- Le jeu., 04 avr. 2024 23:45:33 -0400 Paul Dufresne via Freedos-user  a 
écrit 
 > Information given at boot seems to say E: is the INSTALLDISK... but it is 
 > really D: ... I don't know why. 
Oh, I know... I use to use a .iso file, but this time I use a .img file... so 
DESTDISK is C: , INSTALLDISK is D:
and the E: cdrom drive is empty.

Also, I did began the installation like I said, bug change back to using the 
kvm command line.
Because kvm is so much faster than qemu-system-i386... but even with kvm... 
installation took about
40 mins... which is longer than most Linux distro installations.

I think in older version of QEMU, we would have used -enable-kvm ... but now 
there is a kvm
command line that replace qemu-system-i386 or qemu-system-x86_64 ...

So I guess it would make sense to download the bonus disk... and use that as a 
virtual DVD.

So let me rewrite the instructions: (I think I am also correcting some errors 
in previous email)

QEMU is a program found on Linux distributions, to emulate a computer.
kvm is a special version of qemu, much faster, but need some stuff from the 
kernel to work.

Download and extract 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/FDT2404-FullUSB.zip
 in FDT2404USB directory.
Download and extract 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/FDT2404-BonusCD.zip
 in a temporary directory.
Move T2404BNS.iso to the FDT2404USB

cd FDT2404USB
qemu-img create fdos.img 1000M
DESTDISK=fdos.img
INSTALLDISK=T2404FULL.img
BONUS=T2404BNS.iso

At install time, I present first INSTALLDISK, then DESTDISK:
kvm -cpu 486 -name FreeDOS -machine pc-i440fx-4.2 -m 64 -drive 
format=raw,file=$INSTALLDISK -drive format=raw,file=$DESTDISK -audiodev 
pa,id=mysnd -device sb16,audiodev=mysnd -device adlib,audiodev=mysnd -machine 
pcspk-audiodev=mysnd -vga cirrus -display sdl -net nic,model=pcnet -net user

After installation, I present first DESTDISK containing the installed FreeDOS, 
and then the BONUS disk as a DVD (cdrom):
kvm -cpu 486 -name FreeDOS -machine pc-i440fx-4.2 -m 64 -drive 
format=raw,file=$DESTDISK -cdrom $BONUS -audiodev pa,id=mysnd -device 
sb16,audiodev=mysnd -device adlib,audiodev=mysnd -machine pcspk-audiodev=mysnd 
-vga cirrus -display sdl -net nic,model=pcnet -net user 

If kvm is not available use qemu-system-i386 instead.
And if qemu-system-i386, use qemu-system-x86_64 instead.
I believe qemu-system-i386 is faster for DOS than qemu-system-x86_64. 

You can now use fdimples command to add new programs from the bonus DVD.

I hope this make it more usefull instructions!


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

[Freedos-user] How to try FDT2404 (Latest test version) on QEMU

[Paul Dufresne via Freedos-user]

Hi! Especially to Lunduke fans having their "second part" of DOS week... about 
one year and a half after first part.
So from April 3 to April 10 2024.
I am not a paid subscriber to lunduke.locals.com and just observing it from far.

I decided to retry FreeDOS after not using it for too many months.

And as I do in this time... I search back the messages I have previously left 
on the list to help me know how to launch qemu...
as I don't think the wiki have an article about it...
But it has been a long time... and I am seeding a new message for the next 
time(s).

So FDT2404 is out: "
###
FreeDOS 2404-Test ("FreeDOS T2404")
###

Warning: This is a FreeDOS development build and is for testing purposes.
It may exhibit behavior vary different from a release build and may not be
suitable for regular use. For general use, please consider using the latest
release build available at http://freedos.org
"

And can be found at:
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/readme.txt

This time, I  have chosen to use 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/FDT2404-FullUSB.zip
rather than the usual 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/FDT2404-LiveCD.zip
Mostly, I find a disk image, a more simple and logical format that a CDROM or 
DVD image format (iso file).

So with an iso file I would use -cdrom image.iso... but the FullUSB.zip 
contains an .img file, that I will use the same
qemu parameter as the hard drive destination image: -drive 
format=raw,file=$DISK where DISK=T2404FULL.img

Steps goes about like this:
Download and extract 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/FDT2404-FullUSB.zip
 in FDT2404 directory.
cd FDT2404
qemu-img create fdos.img 1000M
DESTDISK=fdos.img
INSTALLDISK=FDT2404FULL.img

At install time, I present first INSTALLDISK, then DESTDISK:
qemu-system-i386 -cpu 486 -name FreeDOS -machine pc-i440fx-4.2 -m 64 -drive 
format=raw,file=$INSTALLDISK -drive format=raw,file=$DESTDISK -audiodev 
pa,id=mysnd -device sb16,audiodev=mysnd -device adlib,audiodev=mysnd -machine 
pcspk-audiodev=mysnd -vga cirrus -display sdl -net nic,model=pcnet -net user

After installation, I present first DESTDISK containing the installed FreeDOS, 
and then INSTALLDISK (not so much needed anymore):
qemu-system-i386 -cpu 486 -name FreeDOS -machine pc-i440fx-4.2 -m 64 -drive 
format=raw,file=$DESTDISK -drive format=raw,file=$INSTALLDISK -audiodev 
pa,id=mysnd -device sb16,audiodev=mysnd -device adlib,audiodev=mysnd -machine 
pcspk-audiodev=mysnd -vga cirrus -display sdl -net nic,model=pcnet -net user

Information given at boot seems to say E: is the INSTALLDISK... but it is 
really D: ... I don't know why.

Games seems to work often better than it did in my memory.
Was it on VirtualBox that color palette was wrong?

Also... Magic Mirror game seems to start... and I did not remember to have seen 
it working before.

For me DHCP seems not really working... but I run this on Vanilla  OS ... with 
apx run $command  and so I think maybe it does not work because the virtual 
machine
is running inside the Ubuntu sub-machine (an other virtual machine as far as I 
know).

So it seems to be the gist of what I wanted to say.


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

Re: [Freedos-user] gminer.exe game needs an emulation friendly wait_vsync()

[Paul Dufresne via Freedos-user]

Seems sound work in QEMU if display=sdl but not if display=gtk:
https://gitlab.com/freedos1/gold-mine-run/-/issues/2#note_1590502684



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

Re: [Freedos-user] gminer.exe game needs an emulation friendly wait_vsync()

[Paul Dufresne via Freedos-user]

Finally, after trying many things that did not work, I just added a 
"delay(14);" to wait_vsync function.
You should be able to get the exe from:
https://gitlab.com/freedos1/gold-mine-run



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

Re: [Freedos-user] gminer.exe game needs an emulation friendly wait_vsync()

[Paul Dufresne via Freedos-user]

Problem is that wait_vblank is used to add delays for the game:
https://gitlab.com/freedos1/gold-mine-run/-/issues/1


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

Re: [Freedos-user] gminer.exe game needs an emulation friendly wait_vsync()

[Paul Dufresne via Freedos-user]

I discovered that if I comment out the two while (in vga.c):

void wait_vsync()

{

    //while (inportb(0x3da) & 8);

    //while (!(inportb(0x3da) & 8));

}



Then the game under dosbox run just like under VirtualBox.



I have tried all the available options for emulated graphics "card" under 
VirtualBox... no change.

So... I guess what I/we need, is a more emulation friendly wait_vsync() 
function.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Ré : New game for DOS using DJGPP - Open Source

[Paul Dufresne via Freedos-user]

Ok, I'll stop nagging after this message for a while.

I added to the Makefile:
timer.o:
$(CC) $(CFLAGS) -mgeneral-regs-only -mno-red-zone $< -o $@

And now it compile.

But when run:
Page fault CR2=0042 in RMCB at eip 6; flags=3016
... error=0004

which I believe was what I was receiving when adding iret at the end.






 Le lun., 02 oct. 2023 13:06:35 -0400 Paul Dufresne via Freedos-user  a 
écrit 

 > I have been able to rebuild the game using prebult cross-compiler from 
 > build-djgpp project.
 > 
 > When I add __asm__("iret");
 > program crash as soon as I launch it.
 > Sorry not having the error now.
 > 
 > I am trying to:
 > __attribute__((interrupt))
 > void timer_handler(void *frame)
 > {
 >  ticks++;
 > ...
 > 
 > but getting:
 > i586-pc-msdosdjgpp-gcc -I. 
 > -I/home/paul/Téléchargements/libmikmod-3.3.11.1/include -c -Wall -Werror 
 > -pedantic -O3 -fomit-frame-pointer -ffast-math -march=i386 vga.c -o vga.o
 > timer.c: In function 'timer_handler':
 > timer.c:17:1: sorry, unimplemented: 80387 instructions aren't allowed in an 
 > interrupt service routine
 >  17 | {
 >  | ^
 > make[1]: *** [Makefile:29: timer.o] Error 1
 > make[1]: *** Waiting for unfinished jobs
 > make[1]: Leaving directory '/home/paul/my_gminer/gold-mine-run/src'
 > make: *** [Makefile:2: all] Error 2
 > paul@fedora:~/my_gminer/gold-mine-run2$ 
 > 
 > 
 > Following:
 > https://stackoverflow.com/questions/55437894/how-to-correctly-compile-interrupt-service-routine-using-gcc
 > I have tried to add: -mno-mmx -mno-sse -mno-sse2 -mno-sse3 -mno-3dnow 
 > -mno-red-zone at the end of CFLAGS
 > but it does not appears that my changes change the way the file is 
 > compiled...
 > 
 > I think I am very bad at editing Makefiles!
 > 
 > 
 > 
 > 
 > 
 > ___
 > 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] Ré : New game for DOS using DJGPP - Open Source

[Paul Dufresne via Freedos-user]

I have been able to rebuild the game using prebult cross-compiler from 
build-djgpp project.

When I add __asm__("iret");
program crash as soon as I launch it.
Sorry not having the error now.

I am trying to:
__attribute__((interrupt))
void timer_handler(void *frame)
{
ticks++;
...

but getting:
i586-pc-msdosdjgpp-gcc -I. 
-I/home/paul/Téléchargements/libmikmod-3.3.11.1/include -c -Wall -Werror 
-pedantic -O3 -fomit-frame-pointer -ffast-math -march=i386 vga.c -o vga.o
timer.c: In function 'timer_handler':
timer.c:17:1: sorry, unimplemented: 80387 instructions aren't allowed in an 
interrupt service routine
   17 | {
  | ^
make[1]: *** [Makefile:29: timer.o] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving directory '/home/paul/my_gminer/gold-mine-run/src'
make: *** [Makefile:2: all] Error 2
paul@fedora:~/my_gminer/gold-mine-run2$ 


Following:
https://stackoverflow.com/questions/55437894/how-to-correctly-compile-interrupt-service-routine-using-gcc
I have tried to add: -mno-mmx -mno-sse -mno-sse2 -mno-sse3 -mno-3dnow 
-mno-red-zone at the end of CFLAGS
but it does not appears that my changes change the way the file is compiled...

I think I am very bad at editing Makefiles!





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

Re: [Freedos-user] Ré : New game for DOS using DJGPP - Open Source

[Paul Dufresne via Freedos-user]

about:

https://git.usebox.net/gold-mine-run/tree/src/timer.c



Should the interrupt_handler for 0x1c interrupt, end with an iret?___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Ré : New game for DOS using DJGPP - Open Source

[Paul Dufresne via Freedos-user]

Under VirtualBox, sound works (always... sound never worked for  me under QEMU).

But always too fast, even if I slow CPU to 1%.



I created a gminer.iso file with:

mkisofs -o gminer.iso gminer

where gminer is the directory where gminer.zip was extracted.



Timer code is at:

https://git.usebox.net/gold-mine-run/tree/src/timer.c



Using interrupt 0x1c under DPMI should be fine:

https://www.phatcode.net/res/262/files/dpmi09.html#2.4.2



I find it a bit weird what it does to divide 1 by 5494 to get the usual 
tick rate of 18.2 ticks per second...

as it should be done by 'hardware' I am not expecting to be done in the 
interrupt handler.

Not so sure how well it is supposed to happens under a virtual environment... 
probably fine I suppose... guess most games use this.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Ré : New game for DOS using DJGPP - Open Source

[Paul Dufresne via Freedos-user]

Gold Miner game...



Note: I was trying under FDT2308... where you was trying under FDT2310 (need to 
check this new release!).



I just tried under MS-DOS 5 (under QEMU with sb16)... like you described... 
works sometimes... but always extremely too fast.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Ré : New game for DOS using DJGPP - Open Source

[Paul Dufresne via Freedos-user]

Seems for me, it never run if with sound under QEMU ( -device sb16 ).

Esc stop it with an error code.

But it run (extremely too fast!) with gminer -ns

-ns means no sound



Works well under dosbox however...

I think I had tested it only under DosBOX... sorry for that!



Don't know for other DOS.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Ré : New game for DOS using DJGPP - Open Source

[Paul Dufresne via Freedos-user]

 Le sam., 09 sept. 2023 03:46:59 -0400 Juan  a écrit 
 > Hi, 
 >  
 > I used DJGPP back in the 90s, and was a life changing experience for me: 
 > my first contact with GCC and free software. 
 >  
 > I never managed to finish any games back then, but I have released one 
 > recently, and the source code is available in case anyone is interested: 
 >  
 > https://git.usebox.net/gold-mine-run/about/ 
 >  
 > There are also binaries available here: 
 >  
 > https://www.usebox.net/jjm/gold-mine-run/ 
 >  
 > Thank you DJ Delorie for DJGPP! 
 >  
 > Kind regards, 
 >  
 > Juan 
 
At first I had ignore your post because I thought you did not publish source 
code of this game, but
finally found it (under MIT license) at:
https://git.usebox.net/gold-mine-run/tree/
(was not finding it under https://www.usebox.net/jjm/open-source/ )
[and now reading again your message I see you say source code is available]

I took really just a few seconds at the source code, and came to the 'possibly 
wrong' conclusion it did not use
a known VGA game library, and I find it interesting.

I played it a few minutes and find it interesting.  [sorry for lack of 
vocabulary]
I believe it could be interesting to package it for FreeDOS:
https://gitlab.com/FreeDOS/games
http://freedos.org/

In theory, I manage DJGPP packages for FreeDOS, but did practically did not 
touch it for about one year...
not sure they have kept my permissions ;-)

I am copying to FreeDOS-user mailing list to diffuse the information there.
I think a few people will be interested.



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

Re: [Freedos-user] FreeDOS and the Gemini protocol

[Paul Dufresne via Freedos-user]

 Le sam., 26 août 2023 03:52:41 -0400 Bryan Kilgallin via Freedos-user  a 
écrit 
 > I have installed amfora in a Ubuntu PC. And I briefly looked in the 
 > CAPCOM aggregator. 
 >  
 > But I feel lost! Please advise a newbie on browsing Gemini content. 
 > -- 
gemini://geminispace.info/search?freedos
There is a search "button" in top where you can enter term you care about.
Here I have given the term "Freedos" to search.

Frankly, I did not switch as much as I would like to use Gemini.

Maybe want to try an interactive adventure?:
gemini://gemini.circumlunar.space/users/acdw/vault-guard/
I really did not play much... just to mention that Gemini can have some 
interactivity.




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

Re: [Freedos-user] FreeDOS and the Gemini protocol

[Paul Dufresne via Freedos-user]

 Le Sat, 19 Aug 2023 04:52:05 -0400 Michał Dec  a écrit 
 > Hello Paul,
 > 
 > You could've said "Gopher with TLS".
 
Well, I did not known much Gopher (that seems to have come down in popularity 
at the end of the nineties).

I think Gemini is about middle ground  between Gopher and HTML.

Gemini seems to be Unicode (rather than ASCII), have 3 text heading levels 
(seems Gopher had none), have list and preformated text regions (that Gopher 
have, did not have).
The fact also that carrier returns are respected in gemini-text, make it much 
more easier to create/format than HTML (comparing to the web rather than Gopher 
here).

Contrary to HTML also, no stuff in the middle of text: links, change to bold, 
etc. Only links on full lines.

It is probably this simplified HTML, but not to the point of Gopher, that make 
it interesting today.

About TLS, seems most capsules (term for Gemini sites I was searching for in my 
previous message) are using self-signed certificates.
Meaning, you know that the author is the same as last time you visited (unsure 
how well the gemini clients handled certificates history)... just not sure it 
is really who he claims to be. (My knowledge about TLS is relatively limited).
 



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

[Freedos-user] FreeDOS and the Gemini protocol

[Paul Dufresne via Freedos-user]

I recently learn of the Gemini protocol.



What is the Gemini protocol?



"1.1.1 The dense, jargony answer for geeks in a hurry



Gemini is an application-level client-server internet protocol for the 
distribution of arbitrary files, with some special consideration for serving a 
lightweight hypertext format which facilitates linking between hosted files. 
Both the protocol and the format are deliberately limited in capabilities and 
scope, and the protocol is technically conservative, being built on mature, 
standardised, familiar, "off-the-shelf" technologies like URIs, MIME media 
types and TLS. Simplicity and finite scope are very intentional design 
decisions motivated by placing a high priority on user autonomy, user privacy, 
ease of implementation in diverse computing environments, and defensive 
non-extensibility. In short, it is something like a radically stripped down web 
stack. See section 4 of this FAQ document for questions relating to the design 
of Gemini.



1.1.2 The gentler answer for everybody else



Gemini is a group of technologies similar to the ones that lie behind your 
familiar web browser. Using Gemini, you can explore an online collection of 
written documents which can link to other written documents. The main 
difference is that Gemini approaches this task with a strong philosophy of 
"keep it simple" and "less is enough". 

"



"1.5 What kind of timeless user experience?



In a word, reading!



Reading text with a simple, clear, uncluttered layout without any animation or 
embedded videos or sidebars full of distracting, unrelated extras. If you use 
the "Reader Mode" in your web browser a lot and you love it because you think 
that 99% of the time it makes webpages ten times easier to use by throwing out 
all the useless clutter and just giving you what you want, you'll probably be 
excited to hear that everything in Geminispace looks that way all the time by 
default. 

"



"1.6 So it's just words, then? No pictures, no sound?



Not quite. Like HTTP or Gopher, Gemini can serve any filetype at all, including 
images, audio, video and computer programs. There are tens of thousands of 
images in Geminispace, about five thousand PDF documents, and thousands of 
audio files!



But the only thing that a Gemini document can do with those files is link to 
them. You can't embed images or videos inside a page, sticking them in the 
background or between bits of text. Nothing ever plays automatically. All you 
can do is say to your reader, "Hey, here's a link to a picture, or a video, or 
some music". It's up to them whether they click the link or not - in 
Geminispace, the reader is always in control, not the author. "





I am writing this here, because I believe the low-resource needed to run a 
Gemini Browser is appropriate for FreeDOS.

Well, I guess FreeDOS could allow for Gemini server too, but because it would 
be the only application running on FreeDOS, it is probably not much interesting.



I think it could be interesting to consider doing a Gemini set of pages ... 
(they have a fancy name for that in Gemini community, but I don't find it now) 
for the FreeDOS project.



And also consider porting one of the Gemini client to FreeDOS... there is a 
list on the Wikipedia page:

https://en.wikipedia.org/wiki/Gemini_(protocol)



Basically... this message is for considering this "new" technology inside 
FreeDOS project.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Fedora Media Writer (allows to restore USB key to previous state)

[Paul Dufresne via Freedos-user]

I love Ventoy too.

But on some older Core 2 duo, computer won't start with it.



I hesitated to mention yet an other program:

Fedora Media Writer:

«Destructive installer - "overwrites the drive's partition layout though so it 
also provides a way to restore a single-partition layout with a FAT32 
partition"»



https://github.com/FedoraQt/MediaWriter/releases/tag/latest-windows

https://github.com/FedoraQt/MediaWriter/releases/tag/latest-macos

Main page: 

https://github.com/FedoraQt/MediaWriter___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Ré : Networking FreeDOS 1.3 on QEMU

[Paul Dufresne via Freedos-user]

Phil Reynolds said:

>It seems I have broken packages - got networking now but having a lot

>of problems otherwise. Any easy way to square it all up again?



You really did not give much info about problems you have.



I will try a guess:

First you can try: -cpu=host (rather than -cpu 486)

this will execute programs with the CPU in your computer rather than with an 
emulated 486



You could remove:  

-machine pc-i440fx-4.2



If the problem is about your USB mouse not working... remove usb=off



Here are options you can try to remove (because I don't know what they do ;-) ):

-overcommit mem-lock=off -no-user-config -nodefaults -rtc 
base=utc,driftfix=slew -no-hpet

-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny

-msg timestamp=on___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Ré : FDNPKG, FDIMPLES, online repositories and usage questions

[Paul Dufresne via Freedos-user]

In answer to tauro message on sept.12:



I will ignore part of the messages I just don't know the answer.



>With FDNPKG, the default repository is "latest", but I see that
there's also "1.3" and "unstable".

 >If I'm using FreeDOS 1.3, should I use "latest" or "1.3"? What's the
difference? And what about "unstable"?

It used to have only latest until 1.3.

I insisted that we should have a way to explore what was in some previous 
versions when doing some debugging.

It is possible to get packages from the released files for a version.

So what as been kept is to have a repositories with updated files for a 
particular if it has updates, else it is the released version:

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/indexes.html



>If I'm using FreeDOS 1.3, should I use "latest" or "1.3"?

I would suggest to use latest, as there was no change in packaging format for a 
very long time.

But the precarious way would be to use 1.3.

Do as you wish! ;)



>What's the
difference?

To be frank... at this time I don't know if there is a diff between "latest" 
and "1.3".

It seems that for now, latest is not latest released (1.3), but is unstable.



>And what about "unstable"?

That would be the last time that the repositories were rebuild from sources 
(from unstable branches on Gitlab where development is done)

We don't publicize very much, but since august 2022, we build a test version 
each month.



First was T2208 (august 2022).

Last was T2209 (septermber 2022).

And the installers files are at:

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/



These are there to help people test and report problems for what will become 
next released version.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] The one week in DOS challenge is coming in town!

[Paul Dufresne via Freedos-user]

Lunduke.com does videos and articles about ... retro technologies... and news 
(often invented) about technologies.
See Lunduke.com.

And he is now inviting people to do the following challenge:

"Within The Lunduke Journal Community, we have talked about doing some sort of 
community-wide computing challenge.  Something highly arbitrary, but highly fun.

And, starting this coming Wednesday (the 14th), our first challenge officially 
kicks off:

“Live in DOS for a Week”

The idea is simple: try to use DOS (and DOS-based software) for as much of your 
personal computing as possible for 7 days."

So... FreeDOS is only one of the DOS... but he... maybe the one that feel the 
most real thing.

Starting Wednesday... So you can expect some new people trying to have Arachne 
browser working for them under VirtualBox.
(never was able myself! ;) )

So expect weird question like: "Does someone have been able to make OBS Studio 
to run on FreeDOS?"... or other weird question.

Sure the coming week will be hard for everyone! ;)



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

Re: [Freedos-user] Ré : djgpp bash and autoconf for dos, new gcc

[Paul Dufresne via Freedos-user]

The file format used by packages is described at:

http://wiki.freedos.org/wiki/index.php/Package



The packages are mostly developed at:

https://gitlab.com/FreeDOS



But when you download them as zip from Gitlab, they are not in a format 
described in the Package link given.

That's where the perl script I am writing is supposed to help translate the zip 
downloaded from Gitlab to a package understood by FreeDOS.

I did not publish it yet... but expect to publish something in next 24h.



I am not sure... but I would guess fdimples... use the command line fdnpkg:

http://fdnpkg.sourceforge.net/

I think when launched without parameters, it give help... or then with /? ... I 
don't clearly remember.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Ré : Networking FreeDOS 1.3 on QEMU

[Paul Dufresne via Freedos-user]

Recopying part of a message I posted on the Devel mailing list here:

You may try to adapt the following line that I use:

qemu-system-i386 -cpu 486 -name FreeDOS -machine 
pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -enable-kvm -m 64 
-overcommit mem-lock=off -no-user-config -nodefaults -rtc 
base=utc,driftfix=slew -no-hpet -boot menu=on,strict=on -sandbox 
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg 
timestamp=on -drive format=raw,file=fdt2208.img,format=raw -cdrom T2208LIVE.iso 
 -audiodev pa,id=mysnd -device sb16,audiodev=mysnd -device adlib,audiodev=mysnd 
-machine pcspk-audiodev=mysnd  -vga cirrus -display sdl -usbdevice mouse -net 
nic,model=pcnet -net user 

make sure to adjust: fdt2208.img and T2208LIVE.iso to what you have.

This is itself an adaptation from:
http://www.freedos.org/books/get-started/june14-manual-install.html




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

[Freedos-user] Ré : djgpp bash and autoconf for dos, new gcc

[Paul Dufresne via Freedos-user]

Hi... was aware of the files on Delorie website.



Was more asking for Jerome to create the directory on Gitlab, so that I can 
make a package with your suggested file.



I am unsure if autoconf, and automake are used enough to justify having 
packages for them too.

For people wanting to understand how it works, I like the diagram on:

https://devmanual.gentoo.org/general-concepts/autotools/index.html



Like they show in the diagram... most project will have already made configure 
script and Makefile.in.

So that it mostly usefull for people doing projects to be used on Unix like OS.

So I tend to think it is not necessary to have autoconf and automake packages 
for FreeDOS.



But I do not totally exclude the idea.



Still working on a Perl script to generate FreeDOS packages from zip files 
dowloaded from Gitlab FreeDOS's projects.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Ré : Windows 3.11 issues about FreeDOS

[Paul Dufresne via Freedos-user]

For first problem, you could look at:

http://home.mnet-online.de/willybilly/fdhelp-internet/en/hhstndrd/base/callver.htm



Invalid opcode, means your CPU have encountered an unknown instruction.

So it depends on your CPU versus what the program request.

In QEMU, -cpu pentium-2 ... or other can be used to change the emulated CPU.

On real hardware... more harder to change CPU.



Although I found the following link:

https://groups.google.com/g/alt.os.free-dos/c/JDN8xIJ_ikg___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Keyboard issue - wondering about typematic rate for keyboard repeats in different VMs and emulators

[Paul Dufresne via Freedos-user]

Eric proposed:
"For this, you start DEBUG, then type:
a cs:100
mov ax,0305
mov bx,
int 16
int 20

g
q
"

As Ah=3 int 16h is marked as PCJr only:
INT 16 - KEYBOARD - SET DELAYS (PCjr ONLY)
 REG AH = 3
 AL = 0: RESET TYPEMATIC
 AL = 1: INCREASE INITIAL DELAY
 AL = 2: INCREASE CONTINUING DELAY
 AL = 3: INCREASE BOTH DELAYS
 AL = 4: TURN OFF TYPEMATIC
in https://groups.google.com/g/net.micro.pc/c/yg4oazZOA7g/m/uwO-gYOTi2gJ
I hesitate to go there... but did not get the full RBIL.

https://info.wsisiz.edu.pl/~bse26236/batutil/help/MODESTRS.HTM

but I am a bit unsure these options are supported by FreeDOS because:
http://wiki.freedos.org/wiki/index.php/Mode
does not mention them.

Last I was thinking many keyboards are now USB rather than PS/2...
and I think the 8042 chip handle typematic on DOS...
so I was first thinking about BIOS emulation of PS/2 keyboard and mouse in BIOS 
options...
but your keyboard would just not work if these options were causing problem I 
think.





 Activé ven., 10 juin 2022 14:48:48 -0400 Eric Auer  
écrit 

 > 
 > Tom,
 > 
 > >> In DOS I was able to press and hold a key and the key would repeat.
 > >> Great for arrow and page keys.  For some reason this stopped workin
 > > 
 > > wow. one of these Asshole from Hell questions:
 > > 
 > > no information what DOS we are talkink about.
 > > 
 > > no information whatsoever about CONFIG.SYS/AUTOEXEC.BAT.
 > 
 > I somehow liked Dennis' way of asking for more context and details 
 > better :-p However, I also have a technical question about Daniel's 
 > technical question :-)
 > 
 > Daniel, you could do the following to test whether explicitly setting 
 > keyboard repeat (typematic rate, see RBIL = Ralf Browns Interrupt List) 
 > to maximum speed and the delay to minimum has any effect on your real or 
 > virtual hardware. 
 > Note that you have to press return twice between "int 20" and "g".
 > 
 > For the lowest possible speed and the longest delay before repeating 
 > starts, you write "031f" instead of "" in the "mov bx,..." line.
 > 
 > Interestingly, it seems to make no difference in DOSEMU2 which of the 
 > two values I use for BX. It probably just uses the keyboard repeat 
 > settings from Linux, without letting me a custom different rate just for 
 > the DOSEMU2 window.
 > 
 > So I would be keen to know which of the other DOS systems people here 
 > are using do or do not support changing the typematic rate aka keyboard 
 > repeat rate. In particular, I guess that real hardware often supports 
 > this, while running DOS on a virtual computer in a window could be less 
 > likely to offer support for this setting?
 > 
 > Thanks for testing! Regards, 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

[Freedos-user] Ré : "The very weird Hewlett Packard FreeDOS option"

[Paul Dufresne via Freedos-user]

I guess it make sense if you imagine the development of the project as a series 
of team working on the project,

where the current team must accept the project exactly as received by previous 
team.



Like the first team done a FreeDOS image file, and push it to second team.



Second team develop a Linux hardware solution that does not depends too much on 
hardware by disabling KMS and DRM to load image from first team, and then push 
it to a third team that must do with a linux GUI limited version.



Third team get a virtual marchine software to run the inital freedos image on 
the limited Linux of the second team... and push it to

a fourth team that must add pdf documentation.



More or less... it make some kind of sense.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Ré : Installing freedos to virtualbox them copying dice contents to an actual computer

[Paul Dufresne via Freedos-user]

 Activé mar., 29 mars 2022 14:38:06 -0400 John Vella 
 écrit 



Hi,

So, I've got the 486 computer working and am ready to install freedos and 
wordperfect.



I'm thinking there are a couple of advantages to installing onto a virtualbox 
machine, then formatting the physical hard drive and copying the contents over. 








[Post thinking]
I did not follow your previous situation.
The obvious problem is the media... 486 unlikely to have CD... USB keys?
Is wordperfect on floppies? Then transfering them to floppy images would be 
better to keep them long.
[just don't know... End post thinking]

It sound a bit harder to me than just installing on the 486.

You would have to choose a raw format for the virtual hard drive.
Surely doable in QEmu... I am a bit less sure for others.
I would not format the hard drive because the virtual disk would be partitioned 
and formated.
Then for copying I would try to use dd command in a very light 32 bit Linux... 
but I am unsure how you want to do it.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Re : DBCS question about dosbox-x

[Paul Dufresne via Freedos-user]

 Le ven., 02 juil. 2021 08:49:44 -0400 Eric Auer  écrit 




>Hi! I read on 

> https://dosbox-x.com/release-0.83.15.html 
 
>that DOSBOX-X now supports DBCS for CJK (Chinese, Japanese 
and Korean) languages. Do you happen to know how they do 
that? 




Well, more info about mentioned DOS/V is at:

https://en.wikipedia.org/wiki/DOS/V___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Re : Upgrading the BIOS with FreeDOS

[Paul Dufresne via Freedos-user]

 Le lun., 28 juin 2021 14:46:02 -0400 Ralf Quint  
écrit 
>> That's a bad example I guess... it does indeed run under  DOSEMU2 
>> ... but make DOSEMU2 crash:
>> ERROR: general protection at 0x7f1952c6d798: 2e while  collecting 
>> information.

>That is to be expected. As there isn't really a Dell BIOS to  update under 
>DOSEMU, that should be common sense. You are trying  to gain write access 
>to a piece of memory that is simply protected  by the OS (and/or DOSEMU)...
 > 
 > Ralf
 > 
The problem is that DOSEMU2 give a general protection error...
I was expecting just the program to end in an exception... not the full DOSEMU2.




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

[Freedos-user] Re : Re : Upgrading the BIOS with FreeDOS

[Paul Dufresne via Freedos-user]

Ok, now that I revisted:

https://support.hp.com/ca-en/drivers/selfservice/closure/hp-pavilion-g6-notebook-pc-series/5082228/model/5141422?ssfFlag=true=

I am think it was HP site that was mentioning FreeDOS compatible exe, but when 
ran on FreeDOS would say:

"This program cannot be run is DOS mode"

But now, they do not mention FreeDOS or DOS... so I guess it is ok now.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Re : Upgrading the BIOS with FreeDOS

[Paul Dufresne via Freedos-user]

>https://www.dell.com/support/home/en-ca/drivers/driversdetails?driverid=tjgkp=w764=optiplex-3020m-desktop

>

>the page says: "This file format consists of a BIOS executable file. The 
>Universal 
(Windows/MS DOS) format can be used to install from any Windows or MS 
DOS >environment." but it is a PE file:


>paul@kasparno:~/Téléchargements$ file ~/Téléchargements/OptiPlex_3020M_A15.exe

>/home/paul/Téléchargements/OptiPlex_3020M_A15.exe: PE32 executable (GUI) Intel 
>80386, for MS Windows







That's a bad example I guess... it does indeed run under DOSEMU2 ... but make 
DOSEMU2 crash:

ERROR: general protection at 0x7f1952c6d798: 2e while collecting information.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Upgrading the BIOS with FreeDOS

[Paul Dufresne via Freedos-user]

I have an example (from Dell):



https://www.dell.com/support/home/en-ca/drivers/driversdetails?driverid=tjgkp=w764=optiplex-3020m-desktop



the page says: "This file format consists of a BIOS executable file. The 
Universal 
(Windows/MS DOS) format can be used to install from any Windows or MS 
DOS environment." but it is a PE file:


paul@kasparno:~/Téléchargements$ file ~/Téléchargements/OptiPlex_3020M_A15.exe

/home/paul/Téléchargements/OptiPlex_3020M_A15.exe: PE32 executable (GUI) Intel 
80386, for MS Windows___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Upgrading the BIOS with FreeDOS

[Paul Dufresne via Freedos-user]

(while reading question 1 of the survey...)



More than once, I saw a motherboard manufucturer (I think it is ASUS) claiming 
to have FreeDOS exe to upgrade the BIOS

but found the programs were Windows exe and would not run on FreeDOS.



It is becoming less a problem because UEFI firmware (EzFlash) can now read 
files on the EFI boot partition, and read a

"BIOS" update file there and apply it.



I should have reported to the company... but thought they would not care for 
the older product I was using.

I am taking 5-10 mins to search for an example... but I don't find one.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Reminder about the FreeDOS YouTube channel

[Paul Dufresne via Freedos-user]

 Le mar., 15 juin 2021 07:36:06 -0400 Eric Auer  
écrit 

>Hi Jerome,
...
>How about Bochs? DOSEMU2? DOSBOX? Why would
>you assume that people with VM have different
>needs than people with plain hardware?
Have you tried to run the installer under DOSEMU2?

When it partition the Linux directory, it give some error (I don't remember).

And when it come to format the Linux directory, it loops 3 error messages never 
stopping.

So yes, DOSEMU2 do have some special needs...___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] using suspect partition ... with 1014-15-63 instead of 1015-15-63 booting 1.3-rc4/FD13-LiveCD

[Paul Dufresne via Freedos-user]

While booting 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.3/previews/1.3-rc4/FD13-LiveCD.zip

on VirtualBox I get:

- InitDiskWarning: using suspect partition Pri:1 FS: 06: with calculated values 
1014-15-63 instead of 1015-15-63



Is it expected? Why?___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Re : game compatibility CD/DVD drivers: comparing UDVD2 to OAKCDROM and DOSBOX

[Paul Dufresne via Freedos-user]

I don't know if this is really a protection mechanism.

BTW: about Bar code for music CD: 
https://barcodeinfo.org/barcodes-for-music-cds/

I was just not aware myself about this.



First time I tried 1.3 RC4 live on VirtualBox today, after installation (had 
chosen, base with sources), config=2,

fdimples was not finding the CD media. I thought how weird no one had reported 
it... retry 2 or 3 times... was not

able to reproduce yet.



but even if the CD works, there is an error:

BAD Controller at I-O address D000h, chip I.D. 808667111h

[to me there seems to be an unexpected 1 at the end, not a typo]

[used right-ctrl P to pause to have time to read it]



Other have reported a relatively similar message on QEMU:

BAD Controller at I-O address C040h, Chip I.D. 80867010h.

from: https://sourceforge.net/p/freedos/mailman/message/36465212/



https://www.grc.com/dev/sr6/UDMA_Drivers/README.TXT

says: "Some BIOS programs do not 'configure' a mainboard controller if no user
   drives are found! An unconfigured controller causes UIDE to display
   "BAD controller", then it goes on looking for others to use."

so maybe it is relatively normal.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] How to list "active" drives?

[Paul Dufresne via Freedos-user]

I am reading back the list... and I am at the critique of 1.3rc3.



I think I saw some post about problems of identifying which drives are "active" 
(have a driver that drive them).

Somehow it was mentions about file manager (GUI one) that helps with that, but 
seems that it feels not being DOS anymore...



Anyway, I remember sometimes typing:

d:

e:

f:

etc... in order to find out which one have something...



I guess there should be an utility to automate this process.

I don't think there is one yet.



Not sure how to write it. I did not thought much about the how.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] GUI libs: Turbovision and FLTK (nanox), Dillo browser

[Paul Dufresne via Freedos-user]

I decided to make a small research, and found these libraries suggested to 
someone:



Turbovision: "TVision was developed by Borland (now Imprise) in 1992 (v1.03) as 
a tool
for your TurboC and TurboPascal compilers."



"Turbo Vision (TVision for short) is a TUI (Text User Interface) that
implements the well known CUA widgets. With TVision you can create an intuitive 
text mode application, intuitive means it will have CUA like
interface (check boxes, radio buttons, push buttons, input lines, pull-down
menues, status bars, etc.)"



"The original code is copyrighted by Borland but is freely available from the 
net. Try here.This port is distributed under the GPL license and the Sigala's 
port under a BSD like license."

taken from: http://tvision.sourceforge.net/

found from: https://en.wikipedia.org/wiki/Turbo_Vision



Also, nanox-lib:

"Nano-X as it is named today, is an Open Source project that develops a 
graphical windowing system for small and embedded devices. Nano-X does 
not require any operating system or other graphics system support, as it
 writes directly to the display hardware. Nano-X is designed to be 
portable, and can run in a wide variety of hardware and software 
environments."



"Nano-X has been ported to DOS using DJGPP. All development based on this 
library has been done using the DJGPP compiler."



"Based on the DOS port of the Nano-X library and FLTK the browser Dillo has 
been ported to DOS and is available from this site."



Quotes taken from: https://sourceforge.net/p/fltk-dos/wiki/NanoX_Introduction/



A comment on that page says: "Although a work in progress, NXLIB also is making 
progress running unmodified QT and GTK+ programs."



Also, unsure how much it is linked to previous info:

https://sourceforge.net/projects/fltk-dos/ "This site features a port of the 
FLTK GUI to DOS and Apps using it."



The link that triggered the other was: 
https://retrocomputing.stackexchange.com/questions/14375/c-c-ui-library-similar-to-visual-basic-for-dos___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Installation Problem Hdd

[Paul Dufresne via Freedos-user]

On 20-04-23 08 h 03, Ludovico Giorio wrote:
I checked, and the installer can only see my usb, not the hdd inside 
the laptop.


Message is:
"SETUP wasn't able to locate any disks to install FreeDOS 1.1 from."

What am I doing wrong?

I enabled legacy support in Bios.
I formatted my hdd in Fat.


You are a bit unclear about "legacy support" in BIOS.


Well, I am probably not the most qualified to answer but... as I see no 
one else answering...



If you have the choice between AHCI and IDE you should (as far as I 
remember) use IDE.


AHCI being better in general, but not supported by FreeDOS (at least 
this old version).



Else I would probably try to boot with a Linux image to make sure the 
disk is visible (well connected).




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

[Freedos-user] Re : Quick FreeDOS 1.3 Live CD Poll

[Paul Dufresne via Freedos-user]

There is a bug in  your question!

The question given is: should it be permitted access to any internal hard 
drive(s)?

But the suggested answer is: Yes. Prevent access to internal hard drive.



Please fix your question before I answer: Allow access to internal hard drive.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Re : Re : FreeDos on USB mounted compact flash card

[Paul Dufresne via Freedos-user]

I think I would more recommend Unetbootin than what was in my previous message 
to burn an ISO image on an USB key (or similar):https://unetbootin.github.io/___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Re : FreeDos on USB mounted compact flash card

[Paul Dufresne via Freedos-user]

I don't know.

Do you have a key to press that let you select on which device to start?

Does it shows your device (appears on the list when the flash card is inserted, 
and not appearing when the flash card is not inserted)?

You wrote Refus (I guess this is rufus).
Rufus is doing much transformations on the content before writing it.
It used to have a "dd mode" to write the content unchanged, but I believe it is 
gone in new versions (v.3?).

I used to like https://www.balena.io/etcher/ but since it is under "balena" it 
mostly stopped working for "us".

So, I am doing a Internet search and come to: 
https://www.passmoz.com/burn-iso-image-to-usb-in-3-ways.htmlI have no clue at 
all if it is ok.


But sure, it is more likely to work than Rufus that try so much to do the right 
thing, that it is often not.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] How to set up fdconfig.sys and autoexec files for a driver?

[Paul Dufresne via Freedos-user]

Hi!

Read a bit about your problem.



First, the readme file for the driver says:



Place ESSCFG.INI into root directory of C: drive. The other files go into a 
sub-directory SOLO1.



Add this to CONFIG.SYS:

DEVICEHIGH=C:\SOLO1\ESSOLO.SYS



Add to AUTOEXEC.BAT:

LH C:\SOLO1\ESSOLO.COM

SET BLASTER=A220 D1 I5 T4

C:\SOLO1\ESSVOL.EXE /v:10 /l:0 /w:10 /m:0 /c:10 /s:10 /a:0 /p:0




You said something, like the driver write:

Audio drive not found

I guess you meant

Audio driver not found



MY GUESS IS THAT YOU WRONGLY FOLLOW THE INSTRUCTIONS.

YOU HAVE TO WRITE DEVICEHIGH=C:\SOLO1\ESSOLO.SYS IN FDCONFIG.SYS, NOT 
CONFIG.SYS... I think.



Now, if you say "PCISLEEP L" say it is using interrupt 10 (you said port but 
this have to be interrupt), then to me you need to replace:

SET BLASTER=A220 D1 I5 T4

by

SET BLASTER=A220 D1 I10 T4



Don't know if pcisleep L

can confirm the device use address 220h

But it seems unlikely to be changed... I think



Also, I guess you can "CD \SOLO1" then "essolo.com" to see what it does when 
run manually.

I think this is the program that was/is saying "audio driver not found".___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] No packages to install: check SATA configuration in BIOS: best IDE (Not RAID or AHCI)

[Paul Dufresne via Freedos-user]

I finally was able to install FreeDOS-1.3rc2 (heu... yes it is not released yet 
... had to generate it for many hours).

I used FD13LGCY.iso (LEGACY)... as CD1 and CD2 seems gone in RC2.

Well, it does not seems this was using CWSDPMI, or trying to generate a big ram 
disk.

So no page fault error.



But it was still unable to find the packages.



I realized that UDVD2.SYS driver (CDROM, DVD driver necessary for SHSUCDX to 
work) was not loading with message like:

Nothing found, UDVD2.SYS not loaded.



It turned out that this was due to my SATA configuration in BIOS (DVD 
reader/burner is connected with SATA on my computer) was:

Sata Controller 1: RAID

Tried AHCI (not working... is it AHCI that you need to "decrypt" BIOS tables?).

Tried IDE: Bingo! Was seeing my DVD after reboot.



Although I had chosen "Install all packages with sources", it is unclear 
sources was installed.

At first I have searched some games on installed hard disk but found none.

Until I realized that I had to use FDIMPLES to install packages present on hard 
disk, but not really installed.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FD13-LiveCD1 cannot be used, because missing swap file cannot be used on a CD

[Paul Dufresne via Freedos-user]

And now I just saw that after boot, on the R:\ drive I have

1 dir(s) 2,147,123,200 bytes free



And I am asking myself if the ram drive is not taking almost all the memory, 
and that's why it would try to swap things out, to allocate memory.



That said, I have 4 Gb in that computer:

paul@linux-msd9:~> cat /proc/meminfo 

MemTotal:    4036856 kB

MemFree: 2449888 kB

MemAvailable:    3163924 kB

So at first, it should leave 2Gb free memory to work... but maybe somehow 
FreeDOS is limited to 2Gb?



I tried to do mem in FreeDOS but the command was not available yet.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FD13-LiveCD1 cannot be used, because missing swap file cannot be used on a CD

[Paul Dufresne via Freedos-user]

I have just observed that after I ran on A:

fdramdrv.bat

then 7zdec cease to page fault.

But I don't seems to have enough space on A: or R: to extrace a:fdlive.7z___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FD13-LiveCD1 cannot be used, because missing swap file cannot be used on a CD

[Paul Dufresne via Freedos-user]

I tried on an other computer today with same DVD (with FD13-LiveCD1.iso burned 
on it).

Same results as before.
In fact, just launching 7zdec.exe without arguments results in the swap file 
not present on C: and the previous page fault.

I had tried to:
A:
cwsdpmi -u   (unload)
cwsdpmi -s-  (run without swap file)
but I think I cannot unload original cwsdpmi because it was not launched with 
-p [I think]
At least, it did not change the page fault occuring.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FD13-LiveCD2 works live, but only core files, and find no package files when trying to install to hard disk

[Paul Dufresne via Freedos-user]

I have tried the previous FD13-LiveCD2 in an other computer today.

With a 1 TB hard disk (SATA).

I used Fdisk31 (or 13?) because setup seems to say it has formated the disk but 
just

rebooting and doing the same preparation after reboot.

With Fdisk31 I was able to change disk rather than have one of the 2 96Mb (in 
ram?) disks.

fdisk.exe seems to not offer to change drive?



It worked... at least it installed main FreeDOS and their source code.

I still had the feeling  I had chosen to install all packages... Games, 
Editors, Development, etc.

But only found the main binaries once instlaled... on the C:\Freedos directory 
(packages was mostly empty).

Maybe I did read too fast... unsure.___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FD13-LiveCD2 works live, but only core files, and find no package files when trying to install to hard disk

[Paul Dufresne via Freedos-user]

Hi, I have tried to burn FD13-LiveCD2 on a DVD.
 

The live mode works fine.



When doing FDIMPLES (I understand FD is FreeDos but the rest?),

it only shows installed files (I hesit to call that packages, it seems to be 
only CORE files, like TREE, Debug, mouse, etc.)



Was somehow expecting to see editors, compilers, source code, etc.

I am unsure what to expect from a 500 Mb iso file... is it supposed to contains 
editors, compilers, etc?



When doing setup to install, seems to go fine until it tried to copy the 
files...

error was "no package files found" or something very similar.



I saw someone describing same missing installation files in -devel mailing list.

But I guess it was taken to be because of QEMU, or virtual thing.

I am running on real Quad Core computer on a real hard disk (although a SATA 
one... now that I think of it, hope it is FreeDOS supported).



Also, I did not even cared to find a packet driver.

Read a bit the MTCP Readme file that was suggesting I find one... there not 
seems to be a directory of packet driver to ... try?



So if the idea is the installer is supposed to download packages files from 
Internet... even for "CORE" files like command.com...

would be a very bad idea in my opinion.



So where are the package installation files?___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FD13-LiveCD1 cannot be used, because missing swap file cannot be used on a CD

[Paul Dufresne via Freedos-user]

Hi, I have tried to burn FD13-LiveCD1 two times, first time I thought the 
problem maybe was my DVD not good.

Both cannot be used... results in (real Quad-Core CPU computer):

Extracting FDLIVE.7Z
Warning: cannot open swap file c:\cwsdpmi.swp
Page fault cr2==0040 at iep=3c5; flags=3202
[registers dumped]

R:

I have done:
A:
copy fdlive.7z cwsdpmi.swp
hoping to create a swap file but got:

Unable to write to file 'cwsdpmi.swp'

Yeah, obviously, I cannot write on a CD.

Seems a serious problem.




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