Re: [Freedos-user] Dial-up emulation?

[Michał Dec via Freedos-user]

> 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...


Lol. Lmao, even. I did manage to connect my FreeDOS to the Internet at 
some point but it's not as glamorous as one would think.


> The developers of the 86Box project have recently implemented 
emulation of a Hayes-compatible dial-up modem. So my question is... will 
FreeDOS support the emulated modem?


This isn't FreeDOS' scope. If that modem has DOS drivers, then since it 
falls into FD's scope to be ABI-compatible with Microsoft DOS up to and 
including 6.22, supporting that modem and therefore its drivers is a 
welcome and in fact intended consequence of this rigid scope. So I would 
try to get regular DOS drivers for that modem if I were you. Best of luck.


Best regards,

Michał Dec



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

Re: [Freedos-user] Audio PCI 1370 Sound Card

[Michał Dec via Freedos-user]

Hello,

I used to have a very similar card called SoundBlaster Vibra 128. It 
might have even been a re-brand of your EnSoniq 1370. Before you 
initialize this driver, you should make sure that DMA 1 and IRQ 5 are 
free, so that the TSR can intercept SoundBlaster calls with those 
parameters. Try running HWINFO before initializing the TSR and after. 
Your real soundcard should of course occupy a different IRQ to avoid 
collisions. It can't occupy DMA because PCI devices do not occupy Intel 
8237-style DMA channels.


Best regards,

Michał Dec

W dniu 16.03.2024 o 18:24, Norby Droid via Freedos-user pisze:

does anyone have any experience with this card in FreeDOS?

it will initialize the card and show the info but when I use aptest or 
any program/game with sound it fails?



Aptest reports it cannot find a legacy device.

fdauto:
set sndscape=c:\util\audiopci
set blaster=a220 i5 d1 t2
@call c:\util\audiopci\apinit.com <http://apinit.com>
@call c:\util\audiopci\apload.com <http://apload.com>

output:
audiopci @ port ef00 irq 10
initialization complete

aptest result:
error: no audiopci legacy device was detected

this card works fine in Windows XP.



___
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] "Upgrade" from MS-DOS 6.2.2

[Michał Dec via Freedos-user]

Hello Karen,

Please keep the discussion on-topic. This is a FreeDOS user discussion 
mailing list, not a WEF summit.


Best regards,

Michał

W dniu 27.02.2024 o 21:45, Karen Lewellen via Freedos-user pisze:

If our goals resonate, consider donating.
worth a tax write off in some countries.. 



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

Re: [Freedos-user] MSdos 7.1 question

[Michał Dec via Freedos-user]

Hi,


I'm not entirely sure NT (Win XP etc.) ever supported such a thing atop FAT32 
either (via DOS calls).


Via DOS calls in NT? Not sure. But in ordinary operations, it was as 
normal as pie. I remember pretty well that I had to cut up >4GiB files 
into pieces so that we could transfer them on USB drives back in the day 
to the odd person who used a Mac (no NTFS drivers back then), or to 
someone who still used Windows 98.



Not sure I'd even want exFAT support in FreeDOS, personally. I'd prefer HPFS or 
ext2 instead.


I said it before but I'll re-iterate - any filesystem with proper 
journaling would be a total banger. I still remember how Rayman ate my 
FreeDOS and I still have dosfsck in my fdauto as a preventative measure. 
It's slow as molasses in January however. The same program under Linux 
blows it out of the water.


BR,

Michał

W dniu 04.11.2023 o 01:04, Rugxulo via Freedos-user pisze:

Hi,

On Fri, Nov 3, 2023 at 12:31 PM Ralf Quint via Freedos-user
  wrote:

In which way is "FreeDOS" limited to 2GB sized files? (Sorry, never
bothered wit such large files on DOS (any DOS)? The file size entry in
the FAT32 directory entry is a 4 byte integer. As a filesize can't be
negative, this should be a UINT_32/unsigned long and thus allow for
files up to 4GB.

I'm not exactly sure, but I think 4 GB files were somewhat uncommon
(in DOS programs). And I'm not entirely sure NT (Win XP etc.) ever
supported such a thing atop FAT32 either (via DOS calls).

DJGPP 2.04 "beta" (and 2.05 "current") apps *should* work, but I don't
know for sure (ask Martin Stromberg). I do know that DJGPP's *nix file
utilities like "df" and "du" only use the corresponding FAT32 calls if
the DOS major version is reported as 7.


If the FAT32 enabled file functions of INT 21h do
handle this properly with a unsigned long, any program that does the
same and the programmer of an application didn't get lazy and just
assumes "signed long is big enough for everyone", then this should be a
problem of that application, not FreeDOS.

I believe it's something weird like int 21h, 716Ch is needed to create
the file. (Maybe ecm can chime in, I think we've had this conversation
before.)


If the respective routines in
the FreeDOS kernel do in fact handle the FAT32 file size entry as a
signed long, than this is a bug that needs to be fixed IMHO...

Yes, that's precisely the problem (according to Eric Auer, years ago).


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

FAT32 itself was never patented, it was the long file name format and
handling that was covered by patents, which by now have expired.

As of 2017, yes, supposedly the LFN patents are expired. The main
problem with LFNs (besides the fact that you don't *need* them half
the time) is that the DOS drivers (e.g. DOSLFN) are super slow.


exFAT is  not really an extension like FAT12->FAT16->FAT32 where and doesn't
have such limitations, just doesn't have all that journal stuff that is
included in NTFS, which has become the standard file system ever since
Windows 2000 (and Microsoft intentionally limits the use/format of FAT32
partitions larger than 32GB).

Not sure I'd even want exFAT support in FreeDOS, personally. I'd
prefer HPFS or ext2 instead.


Disk size limit should be 8TB, just like with any other FAT32 implementation.

I still occasionally use a 128 GB USB jump drive with (only) FreeDOS
(FAT32) installed on my old (2010) Dell laptop without any obvious
problems. Granted, that's an older install (older 2041 kernel, older
stable shell 0.84-pre2 XMS_Swap).

In recent months I was writing a lot of Pascal code (ISO 7185 but 99%
TP compatible so that a simple script will let it compile either way).
But none of that needed large files at all. (I also typically test
atop a 200 MB FAT16 RAM disk.)


___
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] MSdos 7.1 question / Sound in DOS and FAT huge file support

[Michał Dec via Freedos-user]

Hi,

Isn't HX that unfinished DOS extender from 15 years ago that wanted to 
make it possible to run Windows-only binaries on DOS, and had some 
success in that field?


BR,

Michał

W dniu 03.11.2023 o 18:14, Joao Silva via Freedos-user pisze:

Hi!
HX DOS Extender work with dos games that require speaker (beep)?

Last time i tryed with a eeepc and nothings.

Thanks

On Thu, Nov 2, 2023 at 5:15 AM Mart Zirnask via Freedos-user 
 wrote:


On 01/11/2023, Eric Auer via Freedos-user
 wrote:
>
> It should be possible to use MPXPLAY to get DOS sound
> with modern hardware: https://mpxplay.sourceforge.net/

I can confirm that MPXPLAY may work out of the box with Intel HDA.
Tested on a Dell Mini 9, which has the Realtek ALC268 card.
Played back mp3 and also a 24bit 48kHz wav file flawlessly on SvarDOS.

(In case there's no sound from speakers, read about the "-scc"  flag
in docs/FAQ.txt. The documentation is comprehensive and great.)

Really happy about all this, since a minor part of my work includes
using at least 24-bit audio. Hoping to cobble together some
mpxplay-based script for wav slicing now -- for Getting To Do More
Real Work In Actual DOS, yay. :)

Will try 32-bit wav with mpxplay soon as well.

Haven't tested sbemu, but here are some more projects for HDA and-or
AC97 support on DOS (haven't tried any of these either):

- HX DOS Extender 2.17+ added HDA support in 2016:

http://www.bttr-software.de/forum/board_entry.php?id=14645=0=time=0



- VSBHDA, a recent dosemu fork:
https://github.com/Baron-von-Riedesel/VSBHDA

- A bare metal wav player (not TSR) and HDA status controller:
https://github.com/Baron-von-Riedesel/HDAutils

- "micro or nano" extender with an example for HDA playback:
https://github.com/Baron-von-Riedesel/DOS32pae

- An AC97 wav player: https://github.com/volkertb/ich2player

- ICH sound driver development: https://github.com/volkertb/ail32-ich

Best,
Mart


___
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] 7zip for dOS?

[Michał Dec via Freedos-user]

You should be alright if you grab a copy of CWSDPMI and add it either to:

- one of the directories in your %PATH%

- or you put it in your current working directory

- or you put it alongside P7ZIP.EXE

CWSDPMI is also packaged by FreeDOS: 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.3/util/cwsdpmi.zip


If you download this zip file, you will find the relevant file under 
BIN\CWSDPMI.EXE inside the archive. I'm not sure if the other files are 
going to be needed, but I would copy them over for good measure. Keep in 
mind this is speculation on my part, about these extra files.


W dniu 01.11.2023 o 22:59, Karen Lewellen via Freedos-user pisze:

Thanks again Eric!
I was likewise confused by some of what is here.
your wisdom about what to run has presented another challenge.
now, this is  the first time in a while a machine has been built for 
me, without my being present for the dos installation itself.

when I run the p7zip command I get a load error no DPMI
 as an aside, I get this when I now run links20f as well.
such did not happen previously, leading me to guess something is not 
loading as it should, or loading that should not.

 How do I correct the DPMI error, and where, autoexec.bat or config.sys?
Thanks again,
Karen



On Wed, 1 Nov 2023, Eric Auer via Freedos-user wrote:



Hi!


 I did download Eric's file, as I do not use freedos.


While you get extra package management features by opening
our zipped app packages with a package manager, unzipping
them with any UNZIP style tool will usually be sufficient.
So you should be fine.

 The information indicates that it might be a port of a windows 
package.

 My search suggested that I should fine an executable called 7za,
 or even just 7z, but it is not  there.
 the p7z file does not work at all.


There are two EXE files in the download:

624292 bx defX 09-Mar-05 00:00 ARCHIVER/P7ZIP/P7ZIP.EXE
542956 bx defX 09-Mar-04 23:48 ARCHIVER/P7ZIP/P7ZIPR.EXE

When you run p7zip -h or p7zipr -h they will show
the help text which makes me assume that they are
two different compiles of a standard 7-zip binary.

I have no idea why they got renamed to p7zip here?

The directory also contains various text documents
and a subdirectory with a HTML manual. In addition,
there are APPINFO, LINKS and SOURCE directories.
The former contains metadata about the package, the
latter contains a zip with the source code and the
LINKS directory contains a batch file which seems
to be meant as a wrapper to be put in your path to
call p7zip.exe without having to add the archiver
p7zip directory to your path. It does not pass the
command line arguments, though, which confuses me.

In short, you should be able to just copy the exe
and maybe the .1 documentation files from the
ARCHIVER/P7ZIP directory into a directory in your
path and keep everything else around at a place of
your choice for some extra documentation. You do
not need to use a package manager then.

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 mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] 7zip for dOS?

[Michał Dec via Freedos-user]

If you download p7zip from 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/unstable/archiver/p7zip.zip, 
you can use the file ARCHIVER\P7ZIP\P7ZIP.EXE


Optimally, you should extract the entire directory ARCHIVER\P7ZIP 
somewhere and write a P7ZIP.BAT file in your %PATH% that calls wherever 
you put P7ZIP.EXE, because, the ARCHIVER\P7ZIP directory contains 
7ZCON.SFX and P7ZIPR.EXE, which are part of the package.


W dniu 01.11.2023 o 21:44, Karen Lewellen pisze:

I did download Eric's file, as I do not use freedos.
The information indicates that it might be a port of a windows package.
My search suggested that I should fine an executable called 7za,
or even just 7z, but it is not  there.
the p7z file does not work at all.



On Wed, 1 Nov 2023, Micha�~B Dec wrote:


Hello Karen,

As I've stated in my previous email:

 * unzip is for decompressing zip files
 * zip is for creating zip files
 * p7zip is for BOTH creating and extracting 7z files (and many more
   actually)

With p7zip, this is not an Alcohol 68% and Alcohol 52% situation, 
like it is with zip and unzip ;)


You can install all 3 from fdimples, which is the package manager for 
FreeDOS. fdimples should be able to use a CDROM, a USB pendrive, or a 
network connection to reach a repository and let you install whatever 
packages are available within.


If you do not want to use fdimples, I'm afraid you'll have to 
download those files that Eric specified on Ibiblio and extract them 
into your FreeDOS partition. The disadvantage here is that you'll 
have to serve yourself to have these tools available in %PATH%, or, 
put up with having to use absolute paths to the executables of these 
programs.


Hope it helps!

Best regards,

Michał Dec

W dniu 01.11.2023 o 20:32, Karen Lewellen via Freedos-user pisze:

 The file referenced by Eric, seems to have archiving tools, but not
 extracting ones.
 Unless I am missing something profoundly obvious?



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

Re: [Freedos-user] MSdos 7.1 question

[Michał Dec via Freedos-user]

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.


Best regards,

Michał Dec

W dniu 01.11.2023 o 21:33, Dale E Sterner via Freedos-user pisze:

You use to promote MSdos 7.1. Have you ever found
a way to get sound on it.
I deleted a command called KILL on it. Do you know
what that command does because I don't?
I love the large file size that it supports. Freedos is
limited to 2 gigs and PCdos stops a 8 gigs.


cheers
DS


On Tue, 31 Oct 2023 19:10:35 -0400 (EDT) Karen Lewellen via Freedos-user
 writes:

Thanks Eric,
you are a prince.
Karen



On Tue, 31 Oct 2023, Eric Auer via Freedos-user wrote:


Hi! According to



https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/te
st/report.html

you can download



http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/unst
able/archiver/p7zip.zip

for 7zip. 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



**>>>>
 From Dale Sterner - MS organic chemistry
http://pubs.acs.org/doi/abs/10.1021/jo00975a052
***>>>>



___
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] 7zip for dOS?

[Michał Dec via Freedos-user]

Hello Karen,

As I've stated in my previous email:

 * unzip is for decompressing zip files
 * zip is for creating zip files
 * p7zip is for BOTH creating and extracting 7z files (and many more
   actually)

With p7zip, this is not an Alcohol 68% and Alcohol 52% situation, like 
it is with zip and unzip ;)


You can install all 3 from fdimples, which is the package manager for 
FreeDOS. fdimples should be able to use a CDROM, a USB pendrive, or a 
network connection to reach a repository and let you install whatever 
packages are available within.


If you do not want to use fdimples, I'm afraid you'll have to download 
those files that Eric specified on Ibiblio and extract them into your 
FreeDOS partition. The disadvantage here is that you'll have to serve 
yourself to have these tools available in %PATH%, or, put up with having 
to use absolute paths to the executables of these programs.


Hope it helps!

Best regards,

Michał Dec

W dniu 01.11.2023 o 20:32, Karen Lewellen via Freedos-user pisze:
The file referenced by Eric, seems to have archiving tools, but not 
extracting ones.

Unless I am missing something profoundly obvious? ___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] 7zip for dOS?

[Michał Dec via Freedos-user]

That and there's also, well, guessing which ~# file is the correct one.

Also if you don't have the install CD, you can try your luck with 
connecting your FreeDOS instance to the Internet. fdimples has no 
problem downloading stuff that's online if you don't have a CD at hand. 
But, luck is the keyword here.


Michał

W dniu 31.10.2023 o 21:30, Ralf Quint via Freedos-user pisze:

On 10/31/2023 1:27 PM, Karen Lewellen via Freedos-user wrote:

I do not have a freedos install cd.
I understand that 7 zip files require the 7zip program...which is why 
I am seeking it somewhere.

are such files  given names like
file.7zip?
the latter does not keep the three character extension rule, which is 
why I am likewise asking.
Karen 


The common file extension for 7Zip files is .7z


Ralf




___
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] 7zip for dOS?

[Michał Dec via Freedos-user]

Regular zip files can be decompressed with unzip. For compression, use zip.

7z files can be decompressed with 7zip.

They're all on the full FreeDOS install CD.

Best regards,

Michał Dec

W dniu 31.10.2023 o 21:20, Karen Lewellen via Freedos-user pisze:

Hi All,
and a reminder how to set them apart from say .zip files?
have such an archive,  needed to get a machine built, and one program 
I am restoring  is available as a 7zip file.

Is there a DOS equal to the pk zip package?
And should such files be named differently than just .zip?
Thanks so much.
With appreciation,
Karen




___
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] Installing on an iMac 2011 (with good reason)

[Michał Dec via Freedos-user]

Hello,

>the machine running hot

Maybe try running FDAPM to reduce CPU usage once you're in the shell? I 
remember installing FreeDOS on a Toshiba A660 with an i7 onboard, but I 
don't recall that kind of issue.


>is this normal behavior for installing FD to an SSD?

No. FreeDOS can be installed on flash memory no problem. I'm using it on 
a CF card and it's doing good.


>general errors with FAT

From my experience if you choose FAT32 filesystem for the job, you need 
to make sure it exists on a disk with a MBR partition table, and the 
designated partition must have a type equal to 0x0C. FreeDOS installer 
usually makes sure that these conditions are met before installation 
although I would not trust it to align the first partition to start at 
the 1st MiB for best mileage. That's why I leave the partitioning and 
formatting to fdisk and mkfs.vfat on Linux. GPT partition table will 
also work, as long as you make a hybrid MBR table and provide a BIOS 
boot partition.


If all of this is not an issue, maybe the drive itself is in bad 
condition? Have you checked SMART metrics?


Best regards,

Michał

W dniu 4.10.2023 o 20:57, ashembers via Freedos-user pisze:

Hello,

I have been trying to install 1.3 on an iMac 2011, which seems dumb on 
the face of it, but I noticed that it has Intel-based sound that looks 
to be SBEM compatible, so I figured that it would actually be a good 
use of aging hardware. There were 2 problems doing this: I saw that 
the cooling fans were running high & the unit was indeed hot - 
regardless of whether I was trying to install or just running FD off 
disc. Also, when I installed, it seemed slow but I read that sometimes 
it can take a while so I left it run all night. It ran into errors 
like these:


Run chkdsk: Bad FAT index: #x
Run chkdsk: Bad FAT value: #x
Run chkdsk: Bad FAT index: #x
Run chkdsk: Bad FAT value: #x
Fatal error: error code #101, unspecified error with "gzip.exe"

I attempted formatting the drive first (running FD as a Live CD) with 
a full format, but that made no difference.


My questions are: is the iMac architecture that lame in this context, 
or is this normal behavior for installing FD to an SSD? I had not 
tried installing to a platter drive yet.


Thanks for your thoughts,
Dan


___
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] Booting Windows 98 from FreeDOS

[Michał Dec via Freedos-user]

Hi Jürgen,

I'm not entirely sure what you're saying is correct.

>You start with a Freedos command.com

That's not true. FreeDOS started without SHELL or SHELLHIGH will demand 
you enter a path to the shell program. Both FreeDOS and Windows versions 
seem to work, although the Windows shell appears to have a limited mileage.


>Therefor first you should change those DOS file locations to the 
correct Freedos ones. (that's that Display, country, *.cpi and keyboard 
lines). Also that c:\windows\command path should probably point to the 
Freedos directory.


How will that get me any closer to running Windows 98 out of FreeDOS? 
Your instructions make sense if I would like to run FreeDOS with FreeDOS.


I've sat down at the computer again, and I've noticed that at least in 
the help messages for both command.com files, /P does not specify which 
autoexec.bat file will be used. Could it be some undocumented FreeDOS quirk?


On my way up to this point, Microsoft parts started complaining that 
HIMEM.SYS isn't loaded, so I added it to the DEVICE lines.


Knowing that my only real hope is to force COMMAND.COM to execute the 
autoexec.bat somehow, I made this:

8?SHELL=C:\WINDOWS\COMMAND.COM C:\WINDOWS /E:1024 /P /K C:\AUTOEXEC.BAT

and then I've added WIN.COM at the end of autoexec.bat.

This keeps getting me a substantial attempt reliably:
1. First, I get "unsupported dos call INT2F/1231". This gets called 3 times.
2. Next, I get this mouthful...:
Registry File was not found. Registry services may be
inoperative for this reason.
XMS cache problem. Registry services may be
inoperative this session.
Invalid Opcode at 02AC 2116 0206 2116 000A  190D  00C4  3A65 
2A38 00

05

Press any key to continue...

And after that, either I press, or wait 15 seconds, and it shuts down 
the computer.


Did I forget to load something? I've also found this post, which 
describes basically the same issue: 
https://freedos-devel.narkive.com/pF6dlqXN/loading-other-o-ses-from-freedos


Best regards,

Michał Dec

W dniu 25.09.2023 o 11:27, Jürgen Wondzinski via Freedos-user pisze:

Hi Michał,
Maybe it get's confused from different DOS versions, like that Command.com 
files. You start with a Freedos command.com, but then load a Microsoft 
command.com subsequently. Therefor first you should change those DOS file 
locations to the correct Freedos ones. (that's that Display, country, *.cpi and 
keyboard lines). Also that c:\windows\command path should probably point to the 
Freedos directory.

Greetings from Bavaria, Germany
Jürgen Wondzinski


-Ursprüngliche Nachricht-----
Von: Michał Dec via Freedos-user  
Gesendet: Sonntag, 24. September 2023 22:50

An: Discussion and general questions about 
FreeDOS.
Cc: Michał Dec
Betreff: [Freedos-user] Booting Windows 98 from FreeDOS

Hello everyone,

I wanted to boot Windows 98 from FreeDOS 1.3, because I would like to keep all 
things together without worrying about partitioning.

So I actually have a block device backup of when Windows 98 was working on this 
computer. I've extracted the contents and focused on what does Windows 98 have 
in its autoexec.bat and config.sys files.

So let's see autoexec.bat from Windows 98:

SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND
SET SOUND=C:\PROGRA~1\CREATIVE\CTSND
SET MIDI=SYNTH:1 MAP:E MODE:0
SET BLASTER=A220 I7 D1 H7 P330 E620 T6
mode con codepage prepare=((852) C:\WINDOWS\COMMAND\ega.cpi) mode con codepage 
select=852 keyb pl,,C:\WINDOWS\COMMAND\keybdr4.sys

Now, the config.sys from Windows 98:

DEVICE=C:\WINDOWS\setver.exe
device=C:\WINDOWS\COMMAND\display.sys con=(ega,,1) 
Country=048,852,C:\WINDOWS\COMMAND\country.sys

Combining this knowledge, I conceived this, but I'm not sure if this is 
correct. That's 7th entry from my FreeDOS fdconfig.sys:

7?DOS=HIGH
7?DOSDATA=HIGH
7?DEVICEHIGH=C:\WINDOWS\SETVER.EXE
7?DEVICEHIGH=C:\WINDOWS\COMMAND\DISPLAY.SYS con=(ega,,1) 
7?Country=048,852,C:\WINDOWS\COMMAND\COUNTRY.SYS
7?SHELLHIGH=C:\WINDOWS\COMMAND.COM C:\WINDOWS /E:1024 /P=C:\AUTOEXEC.BAT 
/K=WIN.COM

Apparently this doesn't work... kinda. It complains about UMBs, then I'm 
dropped into an interactive terminal.

If I try to now run "C:\WINDOWS\COMMAND.COM C:\WINDOWS /E:1024 /P=C:\AUTOEXEC.BAT 
/K=WIN.COM", I get a barebones Windows 98 terminal.
Still not there though.

If instead I would have tried "C:\WINDOWS\COMMAND.COM C:\WINDOWS /E:1024 /P 
C:\AUTOEXEC.BAT /K=WIN.COM", I get stuck at "mode con codepage
prepare=((852) C:\WINDOWS\COMMAND\ega.cpi)".

Any ideas how this can be done and how to progress further?

Best regards,

Michał Dec



___
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] Booting Windows 98 from FreeDOS

[Michał Dec via Freedos-user]

Why? That's the exact order Windows 98 has them and it does it just 
fine. Maybe if I could skip the mode con commands, something would budge.


W dniu 25.09.2023 o 01:11, Ron Mabry via Freedos-user pisze:

Maybe move the commands in autoexec config files

On Sun, Sep 24, 2023, 5:08 PM Ron Mabry  wrote:

Been awhile and I don't have access to a computer but what is
c:\windows /E:1024
Isn't that telling windows now to use that mem as extended mem
? Or what's the meaning of the e switch... again no computer fat
fingers hard to type, no batt.


On Sun, Sep 24, 2023, 2:51 PM Michał Dec via Freedos-user
 wrote:

Hello everyone,

I wanted to boot Windows 98 from FreeDOS 1.3, because I would
like to
keep all things together without worrying about partitioning.

So I actually have a block device backup of when Windows 98
was working
on this computer. I've extracted the contents and focused on
what does
Windows 98 have in its autoexec.bat and config.sys files.

So let's see autoexec.bat from Windows 98:

SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND
SET SOUND=C:\PROGRA~1\CREATIVE\CTSND
SET MIDI=SYNTH:1 MAP:E MODE:0
SET BLASTER=A220 I7 D1 H7 P330 E620 T6
mode con codepage prepare=((852) C:\WINDOWS\COMMAND\ega.cpi)
mode con codepage select=852
keyb pl,,C:\WINDOWS\COMMAND\keybdr4.sys

Now, the config.sys from Windows 98:

DEVICE=C:\WINDOWS\setver.exe
device=C:\WINDOWS\COMMAND\display.sys con=(ega,,1)
Country=048,852,C:\WINDOWS\COMMAND\country.sys

Combining this knowledge, I conceived this, but I'm not sure
if this is
correct. That's 7th entry from my FreeDOS fdconfig.sys:

7?DOS=HIGH
7?DOSDATA=HIGH
7?DEVICEHIGH=C:\WINDOWS\SETVER.EXE
7?DEVICEHIGH=C:\WINDOWS\COMMAND\DISPLAY.SYS con=(ega,,1)
7?Country=048,852,C:\WINDOWS\COMMAND\COUNTRY.SYS
7?SHELLHIGH=C:\WINDOWS\COMMAND.COM <http://COMMAND.COM>
C:\WINDOWS /E:1024 /P=C:\AUTOEXEC.BAT
/K=WIN.COM <http://WIN.COM>

Apparently this doesn't work... kinda. It complains about
UMBs, then I'm
dropped into an interactive terminal.

If I try to now run "C:\WINDOWS\COMMAND.COM
<http://COMMAND.COM> C:\WINDOWS /E:1024
/P=C:\AUTOEXEC.BAT /K=WIN.COM <http://WIN.COM>", I get a
barebones Windows 98 terminal.
Still not there though.

If instead I would have tried "C:\WINDOWS\COMMAND.COM
<http://COMMAND.COM> C:\WINDOWS /E:1024
/P C:\AUTOEXEC.BAT /K=WIN.COM <http://WIN.COM>", I get stuck
at "mode con codepage
prepare=((852) C:\WINDOWS\COMMAND\ega.cpi)".

Any ideas how this can be done and how to progress further?

Best regards,

Michał Dec



___
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] Booting Windows 98 from FreeDOS

[Michał Dec via Freedos-user]

Hi,

/E specifies how many bytes of memory to reserve for the initial 
environment. 1024 is what FreeDOS 1.3 has by default, although without 
network 640 is enough to store enough variables, that fdauto.bat will 
successfull configure CDROM. With less than 640, it will just fail to 
allocate enough memory for this many variables in autoexec stage.


W dniu 25.09.2023 o 01:08, Ron Mabry via Freedos-user pisze:
Been awhile and I don't have access to a computer but what is 
c:\windows /E:1024

Isn't that telling windows now to use that mem as extended mem
? Or what's the meaning of the e switch... again no computer fat 
fingers hard to type, no batt.



On Sun, Sep 24, 2023, 2:51 PM Michał Dec via Freedos-user 
 wrote:


Hello everyone,

I wanted to boot Windows 98 from FreeDOS 1.3, because I would like to
keep all things together without worrying about partitioning.

So I actually have a block device backup of when Windows 98 was
working
on this computer. I've extracted the contents and focused on what
does
Windows 98 have in its autoexec.bat and config.sys files.

So let's see autoexec.bat from Windows 98:

SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND
SET SOUND=C:\PROGRA~1\CREATIVE\CTSND
SET MIDI=SYNTH:1 MAP:E MODE:0
SET BLASTER=A220 I7 D1 H7 P330 E620 T6
mode con codepage prepare=((852) C:\WINDOWS\COMMAND\ega.cpi)
mode con codepage select=852
keyb pl,,C:\WINDOWS\COMMAND\keybdr4.sys

Now, the config.sys from Windows 98:

DEVICE=C:\WINDOWS\setver.exe
device=C:\WINDOWS\COMMAND\display.sys con=(ega,,1)
Country=048,852,C:\WINDOWS\COMMAND\country.sys

Combining this knowledge, I conceived this, but I'm not sure if
this is
correct. That's 7th entry from my FreeDOS fdconfig.sys:

7?DOS=HIGH
7?DOSDATA=HIGH
7?DEVICEHIGH=C:\WINDOWS\SETVER.EXE
7?DEVICEHIGH=C:\WINDOWS\COMMAND\DISPLAY.SYS con=(ega,,1)
7?Country=048,852,C:\WINDOWS\COMMAND\COUNTRY.SYS
7?SHELLHIGH=C:\WINDOWS\COMMAND.COM <http://COMMAND.COM> C:\WINDOWS
/E:1024 /P=C:\AUTOEXEC.BAT
/K=WIN.COM <http://WIN.COM>

Apparently this doesn't work... kinda. It complains about UMBs,
then I'm
dropped into an interactive terminal.

If I try to now run "C:\WINDOWS\COMMAND.COM <http://COMMAND.COM>
C:\WINDOWS /E:1024
/P=C:\AUTOEXEC.BAT /K=WIN.COM <http://WIN.COM>", I get a barebones
Windows 98 terminal.
Still not there though.

If instead I would have tried "C:\WINDOWS\COMMAND.COM
<http://COMMAND.COM> C:\WINDOWS /E:1024
/P C:\AUTOEXEC.BAT /K=WIN.COM <http://WIN.COM>", I get stuck at
"mode con codepage
prepare=((852) C:\WINDOWS\COMMAND\ega.cpi)".

Any ideas how this can be done and how to progress further?

Best regards,

Michał Dec



___
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] Booting Windows 98 from FreeDOS

[Michał Dec via Freedos-user]

Hello everyone,

I wanted to boot Windows 98 from FreeDOS 1.3, because I would like to 
keep all things together without worrying about partitioning.


So I actually have a block device backup of when Windows 98 was working 
on this computer. I've extracted the contents and focused on what does 
Windows 98 have in its autoexec.bat and config.sys files.


So let's see autoexec.bat from Windows 98:

SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND
SET SOUND=C:\PROGRA~1\CREATIVE\CTSND
SET MIDI=SYNTH:1 MAP:E MODE:0
SET BLASTER=A220 I7 D1 H7 P330 E620 T6
mode con codepage prepare=((852) C:\WINDOWS\COMMAND\ega.cpi)
mode con codepage select=852
keyb pl,,C:\WINDOWS\COMMAND\keybdr4.sys

Now, the config.sys from Windows 98:

DEVICE=C:\WINDOWS\setver.exe
device=C:\WINDOWS\COMMAND\display.sys con=(ega,,1)
Country=048,852,C:\WINDOWS\COMMAND\country.sys

Combining this knowledge, I conceived this, but I'm not sure if this is 
correct. That's 7th entry from my FreeDOS fdconfig.sys:


7?DOS=HIGH
7?DOSDATA=HIGH
7?DEVICEHIGH=C:\WINDOWS\SETVER.EXE
7?DEVICEHIGH=C:\WINDOWS\COMMAND\DISPLAY.SYS con=(ega,,1)
7?Country=048,852,C:\WINDOWS\COMMAND\COUNTRY.SYS
7?SHELLHIGH=C:\WINDOWS\COMMAND.COM C:\WINDOWS /E:1024 /P=C:\AUTOEXEC.BAT 
/K=WIN.COM


Apparently this doesn't work... kinda. It complains about UMBs, then I'm 
dropped into an interactive terminal.


If I try to now run "C:\WINDOWS\COMMAND.COM C:\WINDOWS /E:1024 
/P=C:\AUTOEXEC.BAT /K=WIN.COM", I get a barebones Windows 98 terminal. 
Still not there though.


If instead I would have tried "C:\WINDOWS\COMMAND.COM C:\WINDOWS /E:1024 
/P C:\AUTOEXEC.BAT /K=WIN.COM", I get stuck at "mode con codepage 
prepare=((852) C:\WINDOWS\COMMAND\ega.cpi)".


Any ideas how this can be done and how to progress further?

Best regards,

Michał Dec



___
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

[Michał Dec via Freedos-user]

Hello Paul,

You could've said "Gopher with TLS".

Best regards,

Michał

W dniu 19.08.2023 o 09:11, Paul Dufresne via Freedos-user pisze:

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 mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos, laptops, and the internet?

[Michał Dec]

Hi,

FreeDOS can be used to access a network if your network card has a DOS 
driver. Those are usually provided by the manufacturer of said card. 
You'll probably want a "packet driver", but I think someone who has more 
experience with networking under DOS would be able to give you better 
info. I remember quitting the entire ordeal because I had wget and other 
network tools crash all the time, and they exhibited some seriously 
jarring bugs like resolving domains that are supposed to be aliases, and 
not resolvable by any DNS. But that was when I was still using 
JEMMEX/JEMM386 so it's probably my fault.


Best regards,

Michał

W dniu 3.06.2023 o 00:02, Karen Lewellen pisze:

Hi folks,
After having been on this list for years, although I not running 
freedos, I am considering a machine using the system alone.
That machine would be a laptop, likely a p3 much as my desktops are, 
if unwise.
My main serious concern is how freedos would access the Internet from 
such a machine.
Its been a long time, but previously only a handful of cards could   
use Freedos and network, has this changed?
If so, what  laptop specific hardware can freedos access for accessing 
the Internet?

Thanks,
Karen




___
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] Concept behind RUFUS

[Michał Dec]

Hi,

RUFUS is basically dd for Windows babies.

Best regards,

Michał

W dniu 18.03.2023 o 19:10, Aitor Santamaría pisze:

Hello,

To those that have used/experience with RUFUS: what is the concept 
behind it?
I don't get a clear picture of how this software operates, either 
reading the site or the wikipedia:


It makes "bootable USB" and supports "a variety of ISO", so
(a) does it make truly bootable drives, like "SYS D:", where the drive 
gets a OS file (rewritable) distribution, after transferring the files 
to the drive (mimicking a INSTALL)?
(b) copies the ISO into the drive, and somehow mounts the ISO file and 
boots from there, thereby creating a read-only in memory drive?

(c) ...

Thanks in advance,
Aitor



___
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] Mouse not working on real silicon

[Michał Dec]

Hi,

Use a PS\2 mouse.

BR,

W dniu 15.01.2023 o 20:26, Knedlik pisze:

Hello!
I successfully ran FreeDOS on my Ryzen 5 3600X, RTX 2060, 32 gigs RAM from a 
USB, except for the CDROM, which is obvious considering the missing CDROM 
hardware.
Cutemouse tells me it’s loaded, but when I launch an app using a mouse, I can’t 
move it. I made sure to disconnect all USB stuff except for keyboard and mouse 
and of course the USB.
Any ideas?
-Knedlik

___
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

[Michał Dec]

Hello Joseph,

I activate LFN on-demand whenever I want to play QDOSFX or Q2DOSFX, 
because these are the only 2 things in my setup that want it. However, 
they will not throw fits if it's not present, only warn you that some 
content may not work.


Best regards,

Michał

W dniu 7.11.2022 o 14:07, Joseph Norton pisze:


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] How to properly use "search"?

[Michał Dec]

Hello again,

I'm trying to write a menu for playing games. The FreeDOS setup I've 
described earlier in my query on how to unload drivers will be presented 
in some local conventions. It's not just my personal gaming setup, I 
want to bring enjoyment to others. From past experience I know that 
letting random strangers have full reign over this computer is a really 
bad idea. One person vandalized FDAUTO.BAT with self-incriminating 
grafitti and created a bunch of lewd directories in random places. 
Another person nagged me constantly because they wanted to have Perl, 
because they found FDIMPLES and found in the package indices that 
installable Perl is a thing in FreeDOS. I caved in to those complaints 
and this individual waited until the convention is off for the night, 
and toiled away until the break of dawn writing a text-based adventure 
game in Perl. What a mad lad. Nevertheless, it's something I'd like to 
avoid in the future. That's why, I want to write a menu. If you remember 
those bootlegs cartridges for the NES that pack 999 games into 1 
cartridge and you simply select which one you want to play, that's more 
or less what I'm going for.


So, I wanted to implement this completely in Batch so that we don't run 
into the problem of taking memory that really demanding games, like 
Wolf, wish they could have. My idea is that I could put a Batch script 
in every game's directory where we can do simple things like start the 
game or run the setup, or regenerate the config to a known working 
state. In order to find games dynamically, rather than have a list of 
games written down in a file, I wanted to run SEARCH C:\GAMES START.BAT, 
but that started listing absolutely everything on C:\. When I tried 
doing SEARCH C:\GAMES\**\START.BAT, it printed some nonsense. How can I 
properly use the SEARCH command?


Best regards,

Michał



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

Re: [Freedos-user] How to unload a driver?

[Michał Dec]

Hello,

Alrighty, here's the entirety of my setup.

I load drivers for SoundBlaster AWE64 by means of putting CTMM.SYS, 
CTSB16.SYS and CTCU.EXE in DEVICE= parameters in FDCONFIG.SYS. However, 
that leaves me with 570KB free. I know that I can free some of that 
memory if only I can unload the drivers once the card is configured. I 
need to have 600KB free in order to start some very strange games, like 
Wolf. No, not Wolfenstein. Wolf 
https://en.wikipedia.org/wiki/Wolf_(video_game)


Best regards,

Michał

W dniu 4.11.2022 o 20:46, dmccunney pisze:

n Fri, Nov 4, 2022 at 2:38 PM Michał Dec  wrote:

Hello,

I'm loading a bunch of drivers during startup, but I'd like to try and unload 
them after all the setup is done. What \

command is for unloading drivers? I know LH and DEVLOAD are for loading.

I  don't offhand think there is such a command

LH and DEVLOAD have the same purpose:  load drivers and ?TSRs high to
get them out of conventional memory.  But in general, you wanted them
present and available during your session, and didn't want to unload
them.

I do have a Unix machine which has an experimental capability to
unload drivers, but it was experimental.  Nowadays, the efforts are to
have things loaded in user space, and unloadable if you no longer need
what they do.

What drivers are you loading in startup?  A driver, by definition,
provides access to hardware, and if you want to use the3 hardware you
need the driver.

I did have utilities back when that I could use to optimize the
loading of TSRs.  Most took memory when loading and initializing, but
that memory cuold be freed and only a small portion thaat was the
actual TSR needed to remain resident, so I got to play games h the
ortder in which TSRs loaded to leave space for the loading an
initialization of subsequent TSRs.  That technique was not applicable
to drivers.

Tell us what you'reloading in startup? Maybe we can help optimize the process.


Michał



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

[Freedos-user] How to unload a driver?

[Michał Dec]

Hello,

I'm loading a bunch of drivers during startup, but I'd like to try and 
unload them after all the setup is done. What command is for unloading 
drivers? I know LH and DEVLOAD are for loading.


Best regards,

Michał



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

Re: [Freedos-user] Total newby question

[Michał Dec]

Probably yes. Just don't use UEFI. Why didn't you try first?

W dniu 18.02.2022 o 00:27, Joseph Kelchner pisze:


Hello,

I’m wondering if Freedos could be used as my operating system on a 
Windows 10 pro Hyper-V Virtual Machine?


Thanks!

Joe



___
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] FAT32 disk formatter

[Michał Dec]

tl;dr use dosfstools

W dniu 14.02.2022 o 12:25, Liam Proven pisze:

I thought this post had some interesting info...

http://ridgecrop.co.uk/index.htm?fat32format.htm




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

Re: [Freedos-user] Quake2 for FreeDOS

[Michał Dec]

There's already a bit of discussion on the subject of licensing on the 
project's BitBucket 
https://bitbucket.org/neozeed/q2dos/issues/21/license-needed


W dniu 23.01.2022 o 21:20, Liam Proven pisze:

On Sun, 23 Jan 2022 at 12:36, Jerome Shidel  wrote:


First, I took a quick look at the pages and browsed the source and did not see 
any LICENSE or COPYING Policy. Perhaps it is mentioned somewhere, but at a 
glance I did not notice one. Without such a declaration, I think it technically 
is source-available not open-source. But, I’m no lawyer.

The original:
https://github.com/id-Software/Quake-2





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

Re: [Freedos-user] Quake2 for FreeDOS

[Michał Dec]

W dniu 23.01.2022 o 12:34, Jerome Shidel pisze:

Without them, it would not be playable.


This is not a problem in pretty much every Linux or BSD distribution. 
They provide binaries of engines for Quake 1, Quake 2, Quake 3, Doom 1, 
Doom 2, Doom 3, Duke Nukem 3D, RollerCoaster Tycoon, RollerCoaster 
Tycoon 2, and many other games that require proprietary game data except 
the engine is free/libre/opensource software.


As for the LICENSE file, I could reach the authors and work it out with 
them. Chances are they got it from the GPL release.


Best regards,

Michał



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

[Freedos-user] Quake2 for FreeDOS

[Michał Dec]

Hi everyone,

I have accidentally bumped into a killer app for FreeDOS. I can confirm 
that it works on FreeDOS with Voodoo 5500 and SoundBlaster AWE64 Gold 
with just HIMEMX and DOSLFN loaded. It will complain DOSLFN isn't there 
if it ain't there, but it still works. Perhaps Quake2 could become a 
FreeDOS package?


Here are the relevant links:

http://falconfly.3dfx.pl/downloads/Q2DOS_EXE_LATEST.7Z - mirror of the 
download


http://dk.toastednet.org/Q2DOS/ - project homepage

https://bitbucket.org/neozeed/q2dos/downloads/Q2DOS_EXE_LATEST.7Z - 
latest compile


In order to make this work, I:

- copied the gamedata off the CD (baseq2 directory)

- copied glide3x from voodoo/h5 directory (inside the game's own 
directory) into the game's root directory (where q2.exe and gl.exe are 
located)


- ripped the soundtrack into OGG containers encoded in FLAC for extra 
mileage, but it turns out the included OGG library doesn't support FLAC, 
so I'm using wav rips


It works great! Only thing however, is that in 1280x1024 the game hangs 
after a couple minutes of gameplay. Could be that my Voodoo 5500 is 
overheating. Wouldn't surprise me, since it's modded to be entirely 
passively cooled.


Best regards,

Michał



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

Re: [Freedos-user] UDVD2 vs SHSUCDX

[Michał Dec]

Hi Eric,

I have accidentally responded only to Jerome before, saying that I've 
found the cause. Let's take care of your message first.


>Do things work better with no JEMM... loaded?

Yes! Much better! I would have to record those tests, but I can tell you 
that:


Redneck Rampage will glitch out, make my ears bleed and return to DOS, 
and while it's still in DOS, the sound card will continue to play a 
half-buffered sample and continue to destroy my ears


GTA1 will refuse to run in every graphic mode. 8bit palette mode and 
24bit palette mode will just print a stack and some kind of exception. 
3dfx mode will complain it can't allocate 215KB of memory, despite at 
least 500KB being free


This is the state of affair with JEMM386 loaded, so when I run my system 
with Yamaha or AWE, it's with HIMEMX and nothing more on top of that. 
The only game so far that actually prefers there be JEMM386 running is 
"The Lost Vikings" which is unable to count the free memory correctly. 
Probably because my FreeDOS machine has 2GB RAM.


I have figured out that the games are okay. I used Metasoma's "Mirror of 
life" album in Quake 1 which is a pressed CD and it worked wonders. So 
the problem is the CD copies I made for GTA1 and Redneck Rampage. I have 
analyzed my images and software stack and I have a little clue. It seems 
the culprit is CDRDAO, and this is what I found when successfully 
running toc2cue:


toc2cue version 1.2.4 - (C) Andreas Mueller 

Converted toc-file 'Quake2.toc' to cue file 'Quake2.cue'.

Please note that the resulting cue file is only valid if the
toc-file was created with cdrdao using the commands 'read-toc'
or 'read-cd'. For manually created or edited toc-files the
cue file may not be correct. This program just checks for
the most obvious toc-file features that cannot be converted to
a cue file.
*Furthermore, if the toc-file contains audio tracks the byte**
**order of the image file will be wrong which results in static**
**noise when the resulting cue file is used for recording**
**(even with cdrdao itself).*

So, the images I make with CDRDAO might be all wrong.

So, FreeDOS is fine. Sorry for alarming anyone.

Best regards,

Michał

W dniu 22.01.2022 o 23:45, Eric Auer pisze:


Hi!

I used this version of OAK 
https://www.hiren.info/download/dos-files/oakcdrom.sys


and the problem persists. I even tried 3 different sound cards with 
the CDROM in UDMA and PIO modes:

- SoundBlaster AWE64 Gold

- SoundBlaster Vibra 128

- Yamaha YMF724


...

In all 6 tests, the CD input would produce static noise, except with 
Vibra 128. Don't even get me started on this card, it's always been 
an unstable mess in DOS, courtesy of JEMM386.


Do things work better with no JEMM... loaded?
Have you tried using XMGR instead of HIMEM?

Regarding the sound question in general, do
the games use the audio PLAY function of the
drive? If yes, is the wiring okay and are the
games able to properly configure the soundcard
volumen control and mixer to the correct input?

If the games use the function to read the raw
audio sectors instead and then play them as a
part of the game sound itself, the whole flow
of data and sound would be different and the
question would change into whether the games
can properly READ the sound data, while using
the normal game sound driver to then play it.

Any more ideas? It used to work flawlessly in FreeDOS 1.2 with 
SHSUCDX backported from 1.3 RC that was newest like, at least a year 
ago. It turned out back then that SHSUCDX from FD 1.2 does not 
support CD playback at all.


I suggest that you compare the UDVD2 versions
and SHSUCDX versions of FreeDOS 1.2 and 1.3 to
find out whether you need the FD1.2 version of
one (which?) or both drivers for your games.

If you were using a different driver, such as
ATAPICDD or OAKCDROM or AHCICD instead of UDVD2,
or MSCDEX instead of SHSUCDX, you can of course
also compare the effects of those differences.

However, as far as I understand, 1.2 worked
out of the box with old SHSUCDX and old UDVD2
and your OAKCDROM experiment is just to check
whether that works better with new SHSUCDX
than new UDVD2 does, also possibly related
to changed command line options in the new
FreeDOS 1.3 style default boot config files?

Thanks for testing!

Regards, Eric

PS: As usual, the memory drivers can also be
part of the problem. HIMEM (try XMGR), JEMMEX
(try JEMM386 or no JEMM... at all) etc.



___
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] UDVD2 vs SHSUCDX

[Michał Dec]

I've tried to dissect my previous FreeDOS instance where it worked. 
Turns out, it used SHSUCDX 3.07 and UDVD2 4-30-2013, so these are the 
package versions I installed. Unfortunately, it didn't work. It's still 
playing static. I have also disabled the second CDROM sitting on the 
same IDE channel, just for extra safety. Still nothing. I don't know 
what to do anymore. The only option I see is reverting to FreeDOS 1.2 
and importing the relevant sound card drivers there.


However, this setup works flawless in Windows 98. Tried it with "The 
Sting!" which relies on a CD soundtrack. Maybe the options with which 
the drivers are loaded are different?


BR,

Michał

W dniu 18.01.2022 o 17:00, Jerome Shidel pisze:




On Jan 18, 2022, at 10:47 AM, Michał Dec  wrote:

I used this version of OAK 
https://www.hiren.info/download/dos-files/oakcdrom.sys


and the problem persists. I even tried 3 different sound cards with 
the CDROM in UDMA and PIO modes:

- SoundBlaster AWE64 Gold

- SoundBlaster Vibra 128

- Yamaha YMF724

It took me this long, because to avoid messing up my system, I have 
added additional modes the system can start with, besides the basic 5 
present in FreeDOS 1.3 RC5. My extra modes are specific for each 
sound card with extra /K parameter for COMMAND.COM 
<http://COMMAND.COM> so that the drivers are up and ready as soon as 
I receive an interactable console. I also needed to edit the Yamaha 
driver to add support for the southbridge.


In all 6 tests, the CD input would produce static noise, except with 
Vibra 128. Don't even get me started on this card, it's always been 
an unstable mess in DOS, courtesy of JEMM386.


Any more ideas? It used to work flawlessly in FreeDOS 1.2 with 
SHSUCDX backported from 1.3 RC that was newest like, at least a year 
ago. It turned out back then that SHSUCDX from FD 1.2 does not 
support CD playback at all.


There are 3 versions at 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/shsucdx.html


Version 3.08 & 3.08a are the same, with just NLS updated. However, 
there is also 3.07 and 3.05.


You could try the middle one.

So, where did things go wrong? Could it be possible that between 
FreeDOS release candidates, SHSUCDX changed to fix the issue and then 
break it in a new way?


Best regards,

Michał

W dniu 16.01.2022 o 19:39, Louis Santillan pisze:
Not sure about the circumstances of your Rayman crash but I’ve read 
many posts about issues with that game on DOS. Apps that access the 
file system or hardware directly, disk caches can cause certain 
types of file corruption. Whole file system corruption is odd and 
might indicate other issues (CPU, RAM, IDE controller, BIOS, drive).


You haven’t provided any details about your hardware.  That said, 
most drivers had compatibility with multiple drive makers.  And 
usually, you only had to specify the device “/d:xxyyzz”.


There’s a list of popular device drivers here.

https://www.hiren.info/downloads/dos-files

MS used to license OAKCDROM.SYS and CD1.SYS for IDE drives.  You can 
find other cd rom drivers at


https://www.allbootdisks.com/disk_contents/98.html


I’d try to find your vendor’s driver disk in archive.org 
<http://archive.org/> or other vintage computing sites.




On Sun, Jan 16, 2022 at 5:09 AM Michał Dec  wrote:

W dniu 16.01.2022 o 13:58, Eric Auer pisze:
> nothing worse than crashing should happen
> if you give the wrong answers.

After working with Rayman I am simply traumatized by crashing
anything
under DOS, because any and every crash can mean the destruction
of the
filesystem's integrity.

I'll try and get the OAK driver and let you know what happens next.

Best regards,

Michał



___
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___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] UDVD2 vs SHSUCDX

[Michał Dec]

I used this version of OAK 
https://www.hiren.info/download/dos-files/oakcdrom.sys


and the problem persists. I even tried 3 different sound cards with the 
CDROM in UDMA and PIO modes:

- SoundBlaster AWE64 Gold

- SoundBlaster Vibra 128

- Yamaha YMF724

It took me this long, because to avoid messing up my system, I have 
added additional modes the system can start with, besides the basic 5 
present in FreeDOS 1.3 RC5. My extra modes are specific for each sound 
card with extra /K parameter for COMMAND.COM so that the drivers are up 
and ready as soon as I receive an interactable console. I also needed to 
edit the Yamaha driver to add support for the southbridge.


In all 6 tests, the CD input would produce static noise, except with 
Vibra 128. Don't even get me started on this card, it's always been an 
unstable mess in DOS, courtesy of JEMM386.


Any more ideas? It used to work flawlessly in FreeDOS 1.2 with SHSUCDX 
backported from 1.3 RC that was newest like, at least a year ago. It 
turned out back then that SHSUCDX from FD 1.2 does not support CD 
playback at all.


So, where did things go wrong? Could it be possible that between FreeDOS 
release candidates, SHSUCDX changed to fix the issue and then break it 
in a new way?


Best regards,

Michał

W dniu 16.01.2022 o 19:39, Louis Santillan pisze:
Not sure about the circumstances of your Rayman crash but I’ve read 
many posts about issues with that game on DOS. Apps that access the 
file system or hardware directly, disk caches can cause certain types 
of file corruption.  Whole file system corruption is odd and might 
indicate other issues (CPU, RAM, IDE controller, BIOS, drive).


You haven’t provided any details about your hardware.  That said, most 
drivers had compatibility with multiple drive makers.  And usually, 
you only had to specify the device “/d:xxyyzz”.


There’s a list of popular device drivers here.

https://www.hiren.info/downloads/dos-files

MS used to license OAKCDROM.SYS and CD1.SYS for IDE drives.  You can 
find other cd rom drivers at


https://www.allbootdisks.com/disk_contents/98.html


I’d try to find your vendor’s driver disk in archive.org 
<http://archive.org> or other vintage computing sites.




On Sun, Jan 16, 2022 at 5:09 AM Michał Dec  wrote:

W dniu 16.01.2022 o 13:58, Eric Auer pisze:
> nothing worse than crashing should happen
> if you give the wrong answers.

After working with Rayman I am simply traumatized by crashing
anything
under DOS, because any and every crash can mean the destruction of
the
filesystem's integrity.

I'll try and get the OAK driver and let you know what happens next.

Best regards,

Michał



___
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] UDVD2 vs SHSUCDX

[Michał Dec]

W dniu 16.01.2022 o 13:58, Eric Auer pisze:

nothing worse than crashing should happen
if you give the wrong answers.


After working with Rayman I am simply traumatized by crashing anything 
under DOS, because any and every crash can mean the destruction of the 
filesystem's integrity.


I'll try and get the OAK driver and let you know what happens next.

Best regards,

Michał



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

[Freedos-user] UDVD2 vs SHSUCDX

[Michał Dec]

Hi,

I think it was a little controversial to load both of those drivers at 
the same time. Maybe this is causing my problems?


I'm playing GTA1 and Redneck Rampage. These games have CD audio tracks. 
GTA1 plays a static noise and RR detects the CD, but refuses to play 
anything.


How can I temporarily disable either one of those drivers? How can I 
import a much more compatible OAK driver? I tried OAK's installer once 
and it asked me some pretty low-level questions about the IDE interface 
and I chickened out out of fear of breaking the currently connected IDE 
devices.


Best regards,

Michał



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

[Freedos-user] DOSHEXED - memory bug

[Michał Dec]

Hi everyone,

I'm trying to edit different files with DOSHEXED from FreeDOS 1.3RC5 CD 
and it's just disappointing. This editor will complain it's out of 
memory if we're trying to open a file that won't entirely fit into the 
leftover conventional memory (<1MiB). I tried editing LOTUS.DAT (approx 
1.4MB, from Lotus 3: The Ultimate Challenge) and Stargunner's SETUP.EXE. 
Luckily the second one fits, given you don't load too many drivers in 
DOS. Is there any other hex editor for FreeDOS, which works a lot better?


Best regards,

Michał



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

Re: [Freedos-user] Question about FreeDOS 3.0

[Michał Dec]

On Sun, 5 Dec 2021 at 18:12, Travis Siegel  wrote:


Paragon software has a program that will allow you to clone a disk from
a smaller to a larger disk with no problem, even the other way too, as
long as the blank space on the disk allows the material to fit onto the
disk itself.


Yup. Heard of it. Never used it. Meant to be good, I think.

dd is a great alternative since it's free. As in freedom.


GPT can be used on any size of drive but *must*  be used on drives bigger than 
2TB.


Pin by Vanessa Wyrzykowska on Rysować | Bugs bunny, Memes ...___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Question about FreeDOS 3.0

[Michał Dec]

When a laptop manufacturer says the computer supports FreeDOS, it's 
their way of stating 2 facts:


1. Their UEFI has CSM support.

2. They offer selling this laptop without a Windows license.

W dniu 01.12.2021 o 16:31, Mercury Thirteen via Freedos-user pisze:



On Tuesday, November 30th, 2021 at 11:34 PM, dmccunney 
dennis.mccun...@gmail.com wrote:


...

And this is not a machine you want to try to set up FreeDOS to run
from the bare metal on. Too much of the hardware is simply not
supported by any form of DOS. DOS stopped being sold and
supported long before some of it existed, and it uses UEFI, not a
BIOS, so getting DOS to boot on it will be a real challenge.

...


It would be interesting to find someone who purchased it and see 
exactly what software HP bundles with it.


[sarc]
I mean, come /on/, HP. You love to bundle software with /everything/! 
We can't even buy a printer from you without getting 1.7 GiB of extra 
crap on a disc. So what about FreeDOS? Hmm?

[/sarc]

But seriously, though, I wonder if the hardware in this specific 
laptop /is/ actually supported under DOS, and perhaps HP supplies 
drivers for it just like they would supply drivers for Windows or 
whatever other OS they would sell alongside their hardware. Yeah, I 
know that's probably not the case. But that would be nice. That would 
be nice. :)



___
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] Question about FreeDOS 3.0

[Michał Dec]

Yeah. If you absolutely want to develop software for bare-metal FreeDOS, 
you probably want to do it on compatible hardware. That concerns network 
cards, VESA and ISA sound cards mostly. As soon as you set foot on a PCI 
sound card or newer, you're in Windows land. Going back to DOS from this 
point is not impossible, but it is painful.


>$2700 price tag

I'm sorry, I think HP is under a cyber attack. Clearly someone is using 
XSS on their website to get prices of real estate, cryptocurrency or 
Apple products.


Best regards,

Michał

W dniu 01.12.2021 o 05:34, dmccunney pisze:

On Tue, Nov 30, 2021 at 8:01 PM richardkolacz...@hotmail.com
 wrote:

I am new to trying to setup FreeDOS as bare-metal configuration to use instead 
of Windows 10 for programs I am writing.

Why on Earth do you want to do *that*?


I notice that HP computer company has FreeDOS 3.0 as an option for Available 
Operating Systems. Is this anything to do with this forum? Any advantages for 
me to use this instead of RC1.5 version etc.

HP's spec sheet is *wrong.* There *is* no FreeDOS 3.0.  FreeDOS
current release is 1.3.  If you go the HP_'s top level site and search
for FreeDOS 3.0, it will find nothing.

And this is not a machine you want to try to set up FreeDOS to run
from the bare metal on.  Too much of the hardware is simply not
supported by any form of DOS.  DOS stopped being sold and supported
long before some of it existed, and it uses UEFI, not a BIOS, so
getting DOS to boot on it will be a real challenge.

You haven't specified what sort of software you want to develop, but
unless you are dedicated Old Skool, who wants to develop on a pure DOS
PC using only development tools available when DOS was current, you
are better served to get a decent Win10 Pro machine with current
development toolchains, and compile to 808X.binaries than can run
under DOS and run DOS in emulation.

If I wanted to do this sort of thing, I'd start with a Win10 desktop,
not a laptop.  The one I'm using at the moment is a refurb
ex-corporate workstation that came with a quad cone Intel i5 cpu 2
356ghx, with a built in turbo mode up to 3.9 ghz, 16GB of RAM, Intel
HD 4600 graphics, and Win10 Pro on a 256GB SSD,  It cont *one tenth*
of the price for the laptop in the specs.

If you absolutely must run DOS on the bare metal, look at the links
for new gear posted earlier, or look around on someplace like eBay for
old PCVs that were designed to run DOS.

Buy the HP laptop advertised, and you will spend a lot of money on a
machine that cannot be used for what you want to do.
__
Dennis


___
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] Question about FreeDOS 3.0

[Michał Dec]

What. FreeDOS ain't even got 1.3 past release candidate numbers.

Regards,

Michał

W dniu 01.12.2021 o 01:59, richardkolacz...@hotmail.com pisze:
I am new to trying to setup FreeDOS as bare-metal configuration to use 
instead of Windows 10 for programs I am writing.


I notice that HP computer company has FreeDOS 3.0 as an option for 
Available Operating Systems. Is this anything to do with this forum? 
Any advantages for me to use this instead of RC1.5 version etc.


I have attached a screenshot from the HP specifications page for you 
to study - I hope this attachment does not go against any forum rules.


Thanks

Richard



*From:* Rugxulo 
*Sent:* Tuesday, 30 November 2021 11:52 AM
*To:* Discussion and general questions about FreeDOS. 


*Subject:* Re: [Freedos-user] How to redirect STDOUT and STDERR to file
Hi,

On Sun, Nov 28, 2021 at 6:53 AM saito yutaka  wrote:
>
> How to redirect STDOUT and STDERR to file.
> I want to redirect to file as follow.
>
> ---
> c:\>dir aaa > out.txt
> c:\> type out.txt
>  Volume in drive C is FREEDOS2021
>  Volume Serial Number is 3668-1A1E
> File not found.
> ---
>
> But it works as follow.
> It couldn't redirect "File not found" string.
>
> ---
> c:\>dir aaa > out.txt
> File not found.
> c:\> type out.txt
>  Volume in drive C is FREEDOS2021
>  Volume Serial Number is 3668-1A1E
> ---

As mentioned, some things won't work by default.

For most things, if you just want to silence output (usually in a .BAT
file), try this:

REM ... shut up almost all output ...
ctty nul
echo (do whatever)
ctty con
REM ... make sure to re-enable "ctty con" at the end!! ...

To redirect STDERR to file, you need a third-party util (or a better
shell like 4DOS, as already mentioned):

* http://cd.textfiles.com/simtel/simtel0101/simtel/asmutl/stderrf1.zip

There's also DJGPP's REDIR.EXE (386 DPMI) from DJDEV205.ZIP :

* http://www.delorie.com/pub/djgpp/current/v2/djdev205.zip


___
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] Sound in (Free)DOS

[Michał Dec]

How is this compatibility achieved? DDMA?

W dniu 02.10.2021 o 16:35, Lukas Satin pisze:
I had success with ESS Solo-1. Also some C-Media is good I have heard 
or Vortex PCI. It works without EMM386, so you can run Carmageddon 1 
in 3dfx DOS on Compaq Deskpro EN - Pentium III 1 GHz. The only 
downside is that you need to use pciset.exe util and send few 0 a 1 
bytes on PCI bus to configure the PCI soundcard, enable sound blaster 
mode and set it like IRQ=5, DMA=3, ADDRESS=240. It is not typical and 
autodetection of soundcard will not work. But if you run setup.exe of 
some app and set it up manually plus use SET BLASTER in Autoexec.bat, 
then it works fine in pure MS-DOS 7 (Windows 98 SE machine). I was 
able to run 99% of DOS sound apps without ISA.


On Sat, Oct 2, 2021 at 3:10 PM Zbigniew <mailto:zbigniew2...@gmail.com>> wrote:


On Sat, Oct 02, 2021 at 02:58:40PM +0200, Michał Dec wrote:

> This is really grasping at straws here, since this would require
re-writing
> HMI drivers to use said cards. Lots of DOS games either have
them statically
> linked into the exe file, or use them as loadable modules a'la
dynamic
> libraries. I'm not saying it's impossible, just tough. AFAICT
nobody has
> done that to date.

Probably nobody ever will until Elon Musk (or Branson) offers a
"bounty" ;)
-- 
regards,

Zbigniew


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
<mailto:Freedos-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/freedos-user
<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] Sound in (Free)DOS

[Michał Dec]

Hi Zbigniew,

This is really grasping at straws here, since this would require 
re-writing HMI drivers to use said cards. Lots of DOS games either have 
them statically linked into the exe file, or use them as loadable 
modules a'la dynamic libraries. I'm not saying it's impossible, just 
tough. AFAICT nobody has done that to date.


Best regards,

Michał

W dniu 02.10.2021 o 14:31, Zbigniew pisze:

On Sat, Oct 02, 2021 at 03:15:37PM +0300, ?? ?? 
wrote:


I wonder if it is possible to write a driver for modern sound cards?

There was an attempt to bring some order into sound-related things under DOS:

  https://en.wikipedia.org/wiki/VESA_BIOS_Extensions

Regarding driver for modern cards: an example can be MPXPlay, that can
use various modern soundcards ( https://en.wikipedia.org/wiki/Mpxplay ),
apart of older ones.

So definitely it is possible to create today DOS programs that generate sound
that more modern way -- the problem is: those old programs/games require older
way



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

Re: [Freedos-user] Is it possible to have sound on SoundBlaster Live! CT4830 for PCI slot in FreeDOS?

[Michał Dec]

Yes, it's possible. IIRC Live! was the last card to actually be binary 
compatible with legacy SoundBlaster cards if you don't mind the lack of 
ISA. But if I'm wrong somebody correct me please. Still, you should be 
able to get DOS drivers for every Creative Labs PCI card starting from 
rebranded EnSoniq cards up until and including the Audigy 2 ZS. Just try 
to be careful because all those cards require a memory manager and that 
screws up a lot of games really badly.


If you're like me and don't have an ISA slot to install a problem-free 
sound card, you might be more lucky with a Yamaha YMF724 if your 
motherboard supports DDMA. Not even gonna mention SBLink, this quirk is 
present on maybe 5 or 6 motherboards total. On top of that, you'll need 
to hex edit your ISA bridge's PCI vendor:device number into the 
supported device table of the Yamaha driver, if your southbridge is not 
supported by stock drivers.


W dniu 30.09.2021 o 10:56, Karol pisze:
Is it possible to have sound on SoundBlaster Live! CT4830 for PCI slot 
in FreeDOS?


I know there is no problem with old SoundBlaster sound cards with an 
ISA slot. But what is SoundBlaster Live! to PCI slot? Is it possible 
to emulate legacy SoundBlaster sound cards?




___
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] Wrap up of FreeDOS articles

[Michał Dec]

tar with xz rulz

W dniu 14.07.2021 o 15:22, ZB pisze:

On Sat, Jul 03, 2021 at 10:56:57AM -0500, Jim Hall wrote:


Hi everyone!

I hope you enjoyed the month-long article series on Opensource.com,
about FreeDOS. Here are the articles that ran this week, as June
wrapped up:

"How to archive files on FreeDOS" (Zip and Unzip)
https://opensource.com/article/21/6/archive-files-freedos

So this is what now requires an article, after 40 years of DOS history?
"What is ZIP and what is it for"?

History has come full circle, it seems



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

Re: [Freedos-user] Quake / Blood CD driver audio question - PCEM emulator needs new maintainer

[Michał Dec]

Speaking of CDROM2, I should give that another spin. I may have a bug to 
report.


Regards,

Michał

W dniu 20.06.2021 o 18:28, Eric Auer pisze:

Hi! Vladimiro has found an interesting detail
about the "PCEM versus UDVD2 versus audio CD"
problem: Playing a REAL audio CD works, but
playing a CDS IMAGE of one fails in a special
way: My CDROM2 tool will say that the CD has
audio tracks "A0-18" instead of "00-18" and
therefore refuse to play any of them. So the
bug seems to be specific to CDS handling in
PCEM. Mitsumi CD drivers are affected as well,
while Aopen drivers seem to handle digits in
modulo 10 or have some other way to compensate
the weird audio table of contents (TOC) data.

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

Re: [Freedos-user] Quake / Blood CD driver audio question

[Michał Dec]

UDVD2 from FreeDOS 1.2 sucks for CDDA playback. As in, there is no such 
functionality whatsoever.


Consider stealing UDVD2 from FreeDOS 1.3 RC[0-9]*

It works great for me :)

Best regards,

Michał

W dniu 17.06.2021 o 14:12, Eric Auer pisze:

Hi! Vladimiro writes:


following the topic of the udvd2 driver I wanted to add a bug
that I could not test on real hardware, I tried it in with the PcEm
(https://pcem-emulator.co.uk/), udvd2 does not play the audio tracks
of games, I tried it with two games, Quake and Blood. With another
standard cdrom driver it reproduces it.

If somebody has those games: Do the audio tracks
work on real hardware? I think there could be an
incompatibility between the specific emulator and
the driver here, because I remember that UDVD2 is
able to play audio tracks in other contexts.

Thanks for your feedback :-) 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 make better compatibility with DOS games [current status]

[Michał Dec]

>Not sure why Michał mentions Yamaha YMF724

I've lots of issues with this card. Shame on me for not getting a 
motherboard with ISA slots.


>No idea why Michał is so negative about our HIMEM and EMM386 versions 
and even our filesystem checking and repair tools


A lot of games I tried with JEMM386/JEMMEX had some really jarring 
issues. They varied from the game gracefully crashing to outright raping 
my ears or gradually eroding FAT away. FreeDOS' own FAT repair tools 
couldn't help me. Only nuking everything and re-installing and 
re-configuring everything. At this point I've included a special GRUB 
entry that uses a Linux distro coupled with a custom init script to fix 
my FDOS partition. I lost a lot of time and mental wellbeing on these 
issues so it's really no surprise I'd rather live in a world where the 
sources of my problems do not exist, can't hurt me anymore, and can't 
hurt others.


W dniu 01.06.2021 o 15:17, Eric Auer pisze:

Hi Lukas,


Please help with solution, don't waste time with asking why and why

You will have to ask specific questions when you want
specific answers. If you want to visit your uncle, it
does not help to tell your taxi driver "bring me to
my uncle, do not ask me where he lives" either ;-)

You will not have to "hack your way around", you simply
have to patiently describe the problem so we can give
answers which fit the problem, too.

You mentioned that UDVD2 is outdated. Updates are here:
http://mercurycoding.com/downloads.html#DOS

I certainly agree with Michał that FDNET should be there,
as far as network driver licensing permits distribution.
For the rest, we should offer vendor download links.

Not sure why Michał mentions Yamaha YMF724 drivers, do
you have a Sound Blaster 16? Or do you have a sound card
based on Yamaha YMF724? Which sound card do you two have?

As Michał already said: If your game has a problem with
our brand of EMM386, simply try without EMM386. Easier
than hoping for MS EMM386 to work better, which may or
may not be the case :-)

Also, in the unlikely case that your game even has some
problem with our HIMEM, you can use XMGR instead, same
download link mentioned above.

No idea why Michał is so negative about our HIMEM and
EMM386 versions and even our filesystem checking and
repair tools. Actually FreeDOS includes DOSFSCK which
is the same tool which you would also use in Linux :-p
The Linux DOSFSCK version is updated more often, though.

I disagree with Michał about completely avoiding parts
of MS DOS. I kept QBASIC from MS DOS for quite a while,
as far as I remember. Now there is the big FreeBASIC.

Of course this is no option when you have no license for
MS DOS, but even if you have one, MS DOS is extremely old
and for many components, the FreeDOS versions are better.

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 make better compatibility with DOS games [current status]

[Michał Dec]

Thank you! I've been looking for the mixer and found the appropriate 
settings :)


If you want to replace parts of FreeDOS with MS-DOS stuff, it's up to 
you. I just don't see it going places.


W dniu 01.06.2021 o 14:55, Lukas Satin pisze:

CDAudio:
Freedos 1.3 since RC2 features upgraded UDVD2 driver, which fixes 
CDAudio problem. The solution for you is to download UDVD2 driver from 
author's website and replace it with what you have now. That is the 
ultimate solution. One hint: sound card mixer have some utilities and 
they might set zero volume for CD Audio. Get drivers for Yamaha and 
there should be some setup utility or mixer.


Please help with solution, don't waste time with asking why and why 
and why. Because I ask for it. And I ask kindly. I want FreeDOS. 
That's why I'm here. If I have to hack my way around and replace some 
files from original MS-DOS discs I have here on my table. Then yes I 
will do it because I need FAT32 support and I want FreeDOS ecosystem 
with apps.


Thank you,
Lukas

On Tue, Jun 1, 2021 at 2:49 PM Michał Dec <mailto:moog...@gmail.com>> wrote:


>CDAudio is working, but you have to install proper Sound Blaster
drivers

Would be nice if you could be more specific. I can't get it
working on my Yamaha YMF724.

>FDNET has been removed

Good job devs. Remove the kernel next time. That should help make
FreeDOS better.

>*3)* A lot of games will crash because of JEMM386 exception ==>
how to fix?

Run without drivers. It will start FreeDOS in real mode without a
memory manager. Most games will not be very happy with FreeDOS'
own memory managers and will run into strange issues. Use the
memory manager only if you really need it. And you know what? With
"strange issues" in FreeDOS it's a guaranteed domino effect that
may lead to OS annihilation. Let's say, your game crashes and
hangs the entire system due to reasons. You have no way of
recovering other than forcibly restarting the computer. Now good
luck if that game was in the middle of writing anything to the FAT
partition, because if that's so, your FAT partition is now
slightly more screwed up than it used to be. Keep doing it over
and over and eventually the corruption will eat away your FreeDOS
files. Don't count on FreeDOS' own FAT filesystem checking tools.
They're useless. Consider dualbooting Linux with FreeDOS just so
you can have a filesystem repair tool that actually works.

>any mention of copying anything from proprietary DOS

What's the point of running FreeDOS then if you're just gonna end
up gluing together parts of FreeDOS and Microsoft's proprietary
ecosystem? Might as well get the full Monty and install MS-DOS.

W dniu 01.06.2021 o 14:31, Lukas Satin pisze:

Hi, the current status for FreeDOS 1.3 RC4:
A) cannot install from CD on 486 due to low cache or low memory
=> solution is to install on Pentium, then put the drive in 486

B) FDNET has been removed, for networking download FDNET from
FreeDOS 1.2 if you need

C) CDAudio is working, but you have to install proper Sound
Blaster drivers and also open the mixer to unmute CD Audio (set
volume)

*I NEED HELP WITH THIS:*
*1)* If game has problem with DOS4GW.EXE, just replace it by
DOS32A.EXE from C:\FDOS\BIN (copy and rename to DOS4GW.EXE in
game's directory => sometime can even speed up the game)
*
*
*2)* Most of CD games will report CD is missing and are unable to
start ==> this is important => how to fix it? Use MSCDEX?
*
*
*3)* A lot of games will crash because of JEMM386 exception ==>
how to fix? Use MS-DOS 6.22 or Windows 98 MS-DOS 7.1 EMM386? What
do you think? Can you please help what to copy from DOS 7.1 or
DOS 6.22? I have original discs.

*CONCLUSION:*
FreeDOS right now is very powerful and offer a lot of new
software and new networking possibilities.

Can 100% MS-DOS gaming compatibility be made by copying some
files from MS-DOS?

Can you please help me with this one?

I struggle for 2 days already.

Some example of working FDCONFIG.SYS and FDAUTO.BAT with these
files would be very nice!

Thank you!
Lukas


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net  
<mailto:Freedos-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/freedos-user  
<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
<https://lists.sourceforge.net/lists/listinfo/freedos-user>



_

Re: [Freedos-user] FreeDOS make better compatibility with DOS games [current status]

[Michał Dec]

>CDAudio is working, but you have to install proper Sound Blaster drivers

Would be nice if you could be more specific. I can't get it working on 
my Yamaha YMF724.


>FDNET has been removed

Good job devs. Remove the kernel next time. That should help make 
FreeDOS better.


>*3)* A lot of games will crash because of JEMM386 exception ==> how to 
fix?


Run without drivers. It will start FreeDOS in real mode without a memory 
manager. Most games will not be very happy with FreeDOS' own memory 
managers and will run into strange issues. Use the memory manager only 
if you really need it. And you know what? With "strange issues" in 
FreeDOS it's a guaranteed domino effect that may lead to OS 
annihilation. Let's say, your game crashes and hangs the entire system 
due to reasons. You have no way of recovering other than forcibly 
restarting the computer. Now good luck if that game was in the middle of 
writing anything to the FAT partition, because if that's so, your FAT 
partition is now slightly more screwed up than it used to be. Keep doing 
it over and over and eventually the corruption will eat away your 
FreeDOS files. Don't count on FreeDOS' own FAT filesystem checking 
tools. They're useless. Consider dualbooting Linux with FreeDOS just so 
you can have a filesystem repair tool that actually works.


>any mention of copying anything from proprietary DOS

What's the point of running FreeDOS then if you're just gonna end up 
gluing together parts of FreeDOS and Microsoft's proprietary ecosystem? 
Might as well get the full Monty and install MS-DOS.


W dniu 01.06.2021 o 14:31, Lukas Satin pisze:

Hi, the current status for FreeDOS 1.3 RC4:
A) cannot install from CD on 486 due to low cache or low memory => 
solution is to install on Pentium, then put the drive in 486


B) FDNET has been removed, for networking download FDNET from FreeDOS 
1.2 if you need


C) CDAudio is working, but you have to install proper Sound Blaster 
drivers and also open the mixer to unmute CD Audio (set volume)


*I NEED HELP WITH THIS:*
*1)* If game has problem with DOS4GW.EXE, just replace it by 
DOS32A.EXE from C:\FDOS\BIN (copy and rename to DOS4GW.EXE in game's 
directory => sometime can even speed up the game)

*
*
*2)* Most of CD games will report CD is missing and are unable to 
start ==> this is important => how to fix it? Use MSCDEX?

*
*
*3)* A lot of games will crash because of JEMM386 exception ==> how to 
fix? Use MS-DOS 6.22 or Windows 98 MS-DOS 7.1 EMM386? What do you 
think? Can you please help what to copy from DOS 7.1 or DOS 6.22? I 
have original discs.


*CONCLUSION:*
FreeDOS right now is very powerful and offer a lot of new software and 
new networking possibilities.


Can 100% MS-DOS gaming compatibility be made by copying some files 
from MS-DOS?


Can you please help me with this one?

I struggle for 2 days already.

Some example of working FDCONFIG.SYS and FDAUTO.BAT with these files 
would be very nice!


Thank you!
Lukas


___
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] FAT12

[Michał Dec]

FAT12 sucks. The smallest pendrive I saw was 128MB and that was 18 years 
ago which is still 4x the size of FAT12's limit. Here's how you can 
force the installer to use an existing FAT16/FAT32 filesystem. This 
procedure will cause the installer to detect a valid DOS partition and 
skip the partitioning part and proceed to install.


1. Nuke the partition table just to be safe from whatever insanity 
gparted and FreeDOS partitioning tools have brought upon you


2. Partition your drive with fdisk/gdisk because it gives you the best 
features to accomplish this task:


- creating partitions with offset and size granularity down to the 
sector to give yourself plenty of space for GRUB


*- setting partition types (FreeDOS installer will only qualify 
partitions of type 0x0C for installation targets)*


- extra points for using gdisk to make a hybrid GPT+MBR partition scheme 
which supports FreeDOS - it's possible, tested and it works


You should be done by now and ready to install FreeDOS.

gparted is not a tool that I would ever recommend for *preparing* 
FreeDOS target media or *prepare* any storage media whatsoever. Keep in 
mind I emphasized the word prepare because saying gparted is useless 
would be a major lie. It doesn't offer any of the listed features. 
However what gparted is absolutely amazing at is resizing and moving 
partitions without messing them up. Never used a better tool to do that!


W dniu 26.05.2021 o 00:32, Felix Miata pisze:

Daniel Sears composed on 2021-05-25 14:53 (UTC-0700):


I've installed FreeDOS 1.3-RC4 with FD13LITE.img on a 4GB USB drive. This
works and I can boot it just fine, but the primary partition uses FAT12 and
is 97% full. I would like to expand this partition with gparted, but that
no longer supports FAT12. Can I ask what the rationale is for using FAT12?

Originally FAT12 was for the smallest sizes on partitioned media, IIRC, only up 
to
32MB, but maybe it was 16MB or 20MB. That was a very long time ago, and my 
memory
isn't what it used to be. FAT12's type was 0x01, compared to 0x06 for FAT16. 
Given
FAT12 and FAT16 partitions of identical size, the FAT16 could be more efficient,
as under 256MB or so in size, FAT16 used 4 sector clusters, while larger FAT16
used 8 or more, depending on size, with FAT12 using only 8, so less cluster
overhang on FAT16 could result in extra freespace using it instead of FAT12. 
Thus,
if the FAT12 could be changed to FAT16 without a size change, a wee bit of extra
freespace might materialize. Whether a tool exists that could do this I have no 
idea.
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] hardware recommendations

[Michał Dec]

Hey I was wondering if it would make sense to step up FreeDOS to 
actually you know, be bootable under UEFI ;) The CPUs still got support 
for real mode so we should be fine.


W dniu 27.04.2021 o 16:41, Frantisek Rysanek pisze:

On 27 Apr 2021 at 16:01, Eric Auer wrote:


I agree that it will be tricky to ask vendors which styles
their machine supports, but actually my impression is that
support for booting DOS is not that exotic yet.

In my recent experience, and I don't sell office-grade PC hardware so
that experience is limited:

ITX motherboards by Gigabyte, with BayTrail and Apollo Lake ATOM, do
have the "legacy BIOS boot" (and CSM support) available in the BIOS.
You can select whether to have it or not, there are several items in
the BIOS Setup related to that.

ITX motherboards by AsRock, with Gemini Lake ATOM: UEFI only.
Not in the least apologetic about it :-)

The motherboard user's guide, typically available in PDF for download
off the vendor's website, typically has a couple screenshots of the
BIOS SETUP. If there's not a word about a CSM or legacy boot, beware.

There were some earlier examples of motherboards where the CSM
initially wasn't available, and got added in a later version of the
BIOS. But, I wouldn't rely on this anymore - for many vendors it's
UEFI-only from now on.

Where I work, our key supplier is Advantech = industrial-grade PC
hardware. The legacy boot method is typically still supported in
their hardware, ispecially in their "inhouse products", e.g. ATX /
microATX / mini-ITX motherboards. But, this isn't something you'd
want buy for a home PC, at the price. Otherwise it's rock solid PC
hardware, and the BIOS feels very conservative / vanilla.

To be honest, if I wanted to get a modern PC toy box with
SoundBlaster compatibility, I'd probably use some recent ATOM, even
if UEFI-only, install an appropriate version of Linux and run DOS
under QEMU on top of that. And I'd be free to choose the emulated
SoundBlaster if I wanted to.
As for what Linux: whatever you are familiar with. And, QEMU seems to
get better with every version. In the recent years, I'm with Debian,
so I'd probably choose some recent fast-paced Ubuntu, to get a fresh
QEMU out of the box, with frequent updates if desired.

Whenever I deal with something in DOS, the native DOS-based editors
and IDE's nowadays feel so tiny, in the 80x25 terminal (even 80x43).
I prefer to edit text files "out of band" in some Windows or Linux
environment and maybe just run the compiler for that in DOS, if
cross-development on the modern machine is not practical for some
reason.

Frank



___
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] hardware recommendations

[Michał Dec]

https://www.youtube.com/watch?v=kr_Xw3sTgRk

W dniu 27.04.2021 o 15:43, Liam Proven pisze:

Therefore a salesperson will almost
certainly just lie and say "yes" to get the sale.



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

Re: [Freedos-user] game development for FreeDOS

[Michał Dec]

Hi,

Just wanted to chime in with a question of my own.

Are there any resources for taking advantage of Voodoo 5500 or similar 
post-Voodoo 2 GPUs in DOS?


Best regards,

Michał

W dniu 27.04.2021 o 14:57, Eric Auer pisze:

Hi!


I'm looking for ressources regarding game development for FreeDOS.
I couldn't find anything in the wiki, but maybe I didn't use the
correct keywords.

For game development, there is no difference between FreeDOS and
other DOS versions. You can either read the classic resources from
the Nineties or work with modern toolchains such as OpenWatcom,
DJGPP, the Allegro library, old versions of SDL, etc.


I would prefer to use C, C++ or flat assembler.

That should work well :-)


Regarding graphics, is there a way to support larger resolutions
and bit depths than VGA (e.g. SVGA/VESA)?

You typically want to use VESA VBE, for example with linear frame
buffer and a 32-bit compiler. There are tutorials for that out
there, it is not specific to FreeDOS and works with any DOS :-)


Is there any development environment or compiler you would
recommend for gamedev?

As said, you may enjoy libraries such as Allegro.

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

Re: [Freedos-user] DOS Audio

[Michał Dec]

Hi,

You may need to patch the driver from Yamaha. They stopped caring at 
some point, but you can still patch in support for southbridges up to 
ICH6 and VT82C686B.


Best regards,

Michał

W dniu 08.03.2021 o 17:15, Jerome Shidel pisze:

Hi Everybody,

Thanks for all the advice and information.

Just some rough machine history.

I originally bought that Pentium Pro new back in late 95 at a computer 
show. About a decade ago, I migrated that machine from it’s original 
case to a 2U rack mount case to conserve space. The original case was 
enormous and was about 3ft tall. If I recall correctly, it had 14 5.25 
drive bays. 10 external bays and 4 internal with room for 4 more 
internal ones. But, I was very busy back then to play around with that 
machine. So, I didn’t really do anything with it other than boot it a 
couple times. A year or so later, the CPU fan went bad and I changed 
it  Then about 5 years or so back, the CMOS / Clock battery finally 
died (20 years, not bad). However, it would forget all BIOS settings 
after changing them left it booting from floppy or cd/dvd only. Being 
inside an IC soldered to the mother board, I procrastinated fixing it. 
Not trusting my de-soldering skills, I had a friend remove the old 
clock IC. Then, I soldered in a socket and plugged in a new clock. 
Yippy, all is good again with since 2019. Now finally, I’ve gotten 
around to messing with it. Installed FreeDOS 1.3-RC3 straight from the 
LiveCD. Got networking working. Now working on getting sound support.


Wish I could use ISA instead of PCI.

Being in a 2U rack mount chassis, it has a PCI riser for the expansion 
cards. I wish I could put an ISA card in there. I have (in my opinion) 
the best sound card Creative Labs ever released. The Sound Blaster 
AWE64 Gold with daughter board to max’d RAM. When looking at sound 
cards on eBay, I found that card sells from $150-$300 without the 
extra RAM module. No, I’m not selling it. I’m using it in the docking 
station for my 486DX2-66 notebook. :-)


After the great advice you all gave me, I found a NIB (opened to 
verify contents, but card still factory sealed) YMF744 based sound 
card on eBay for $25. So, I ordered it. I don’t recall if the mother 
board for the Pentium Pro has a SB-Link. It is a server board. So, 
probably not. But, it may have DDMA support.  I guess I’ll find out 
when the card arrives and I install it.


The sound card should arrive next week and I’ll slap it in there soon 
after. I’ll post the results.


Thanks again, all the information was a huge help.

:-)

Jerome





___
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] DOS Audio

[Michał Dec]

Hi,

Sorry, but you're outta luck unless you write your own driver. Cards 
from Audigy 2 and above never received this kind of care and support.


Your best bet would be to actually not use a PCI card at all and instead 
use an ISA card. DOS games are designed specifically around ISA cards, 
as consumer grade PCI sound cards were not a thing until 1998.


Still, even if you use a PCI card with a driver that emulates an ISA 
device (this is not how Yamaha YMF724 works), you are still running the 
risk of breaking a lot of games. When I had my Vibra 128, I needed to 
have a memory manager loaded to start the driver. And when there was a 
memory manager, some games refused to start because they had memory issues.


If you get a Yamaha YMF724 like me, you're a little safer. It's a good 
compromise between compatibility and quality - you get a SoundBlaster 
Pro 1.0 and most games will work - all without the need for a memory 
manager. On the downside, your motherboard either needs to support 
Distributed DMA (in southbridge) or it needs to have a SBLink header 
which provides the missing pins that ISA has and PCI doesn't. Another 
downside is that you are at the mercy of the BIOS' whims if you can't 
manage DMA channel assignments. There are a few games like MDK and Micro 
Machines 2 that do not take it very well if your sound card is on DMA 0.


Best regards,

Michał

W dniu 07.03.2021 o 00:10, Jerome Shidel pisze:

Hi,


On Mar 6, 2021, at 6:03 PM, Joao Silva  wrote:


Hello.

Search the net and found a site regarding audigy card link 
 and hope that works for 
you.


I also have one in case and have the CD never used with  freedos.


Thanks. However, I was there earlier today. They are talking about an 
Audigy (1st Gen). They say that those drivers aren’t believed to work 
with an Audigy 2. Mine is an Audigy 4. I didn’t see anywhere that they 
got Audigy 2+ working. But, maybe there is another thread somewhere or 
some has done it with different (or later) drivers.


Thanks though.

:-)

Jerome


___
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 on Intel Atom and a TV

[Michał Dec]

Hi,

FreeDOS should work over whatever video interface your GPU initializes. 
What might not work is that your storage controllers are working in AHCI 
mode instead of IDE. DOS in general predates AHCI by a long shot and 
FreeDOS currently does not support booting from or even supporting 
storage controllers operating in AHCI.


Best regards,

Michał Dec

W dniu 06.03.2021 o 15:41, Pingüino Exe pisze:

Hi
Well, for starters, I don't even know if this is the right place to 
ask but here goes nothing.


I got this tower that works with Intel Atom. To get the image and 
sound I connected it to my tv, a samsung smart TV, vía VGA to HDMI. It 
works wonderfully with Windows 10 (without taking into account how 
slow it is). But when I tried to install FreeDos the image stopped 
transmitting. At first I thought it was because I tried to boot it 
with an usb, but it happened just the same when I tried with the 
standard CD-ROM version and the Legacy one, so I don't know what to do.

I checked some mailing list and it should work just fine
I don't know if, maybe, I did something wrong when burning the cd or I 
need a proper screen or, I just, don't know.


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

Re: [Freedos-user] DMA management?

[Michał Dec]

Hi,

No, the truth about what I'm using is much more spooky.

The mainboard is an Abit VP6. That kind of board has the VIA VT82C686B 
souhtbridge. To even use the Yamaha card, I needed a modified version of 
their DOS driver which activates the SoundBlaster Pro integrated circuit 
over either SBLink or DDMA - whichever the user chooses based on their 
setup. In my case it's DDMA.


The SoftMenu III BIOS does not mention DMA assignments anywhere, but I 
can check for PnP options...


Thank you for your input. I'll give ICU a shot as well.

Best regards,

Michał

W dniu 05.03.2021 o 00:02, Adam Nielsen pisze:

Hi Michal,

Many BIOS setups have a section where you can manually assign resources
to PCI slots, so I'd check there first and see if you can tell it to
assign what you want to the slot your sound card is in.  Make sure you
disable the option that a plug-and-play OS is installed in order for
these options to become available.

Failing that, I believe you will have to install a PnP configuration
manager such as Intel's ICU.  This will run during boot and assign IRQs
and DMA addresses to all PnP devices.  I haven't tested this with PCI
devices (only ISA) but I think it handles PCI too.  It's really meant
for older BIOSes that don't support PnP.

You could also see if you can find DOS drivers for the YMF card.
Creative Labs distributed their own cut down configuration manager
similar to the Intel ICU except it only handled their sound cards, so
Yamaha might have done the same.

Note that PCI doesn't use the ISA DMA signals so I'm assuming you're
using an SB-Link cable and your BIOS lets you change the SB-Link DMA,
otherwise if your card is loading a driver that uses software
emulation for the DMA channel instead, then reconfiguring that driver
would be the solution.

If you're not using the SB-Link cable it's possible that is hard-wired
to DMA1 and that's why it's unavailable for your card, so in that case
the solution would be to either get an SB-Link cable or see if you can
disable SB-Link in the BIOS to free up DMA1.

Cheers,
Adam.

On Thu, 4 Mar 2021 22:39:56 +0100
Michał Dec  wrote:


Hello,

Is there any way to manage DMA channel assignments? My setup relies on
Yamaha YMF724F for sound, due to there being no ISA slots to get a
proper sound card. Unfortunately, there's no way to have the card work
with DMA 1 or 3. It's stuck on DMA 0 and this is wrong in so many
ways... I've researched this issue and turns out that DMA 0 was
historically reserved for DRAM controllers, then it was a daisy-chain
linking 8-bit and 16-bit DMA controllers. Most games I have support
sound cards on DMA 0, but some have a more conservative design and won't
budge. Even editing the config files to seemingly force this change will
yield no result.

Best regards,

Michał



___
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] Invalid opcode - where do I even begin?

[Michał Dec]

Hi,

No, Contra is that side-scroller shooting game for Nintendo 
Entertainment System. It had a DOS port.


Best regards,

Michał

W dniu 04.03.2021 o 23:37, Louis Santillan pisze:
I think those are binary instructions.  Not actual addresses.  You 
could try disassembling here [0] but a quick cut & paste gave an 
instruction sequence that is non-obvious to me.  If Contra is a 
debugger/mod, then that makes a little more sense.  The full message 
might also help clear things up. Also, noting what memory managers, 
drivers, and other software versions are running also helps.


[0] https://defuse.ca/online-x86-assembler.htm#disassembly2 
<https://defuse.ca/online-x86-assembler.htm#disassembly2>


On Thu, Mar 4, 2021 at 12:37 PM Michał Dec <mailto:moog...@gmail.com>> wrote:


Hello,

I've run some software on Pentium 3 Tualatin S on FreeDOS and it's
getting an invalid opcode error. The error precisely says "Invalid
opcode at ..." where ... is a bunch of 16 bit variables. Saying
"at" is
really misleading and doesn't make any sense, since such a high
address
like let's say 628a  3002 206f 2b43 202b 202d 6f43 7970 6972 6867
2074 3931 is well within the realm of ZFS storage, not protected mode
address space :D

If anyone's wondering, the offending software is Contra and Quake
1.08
(software renderer). For what it's worth, the above hex string is
exactly what Quake blurted out.

Where do I even begin with understanding this message? Is this a
series
of opcodes the CPU failed to run, or is this an address, or is it
something else? I could recompile Quake, but Contra will probably
require me to patch the binary with the help of reverse
engineering tools.

Best regards,

Michał



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
<mailto:Freedos-user@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/freedos-user
<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] DMA management?

[Michał Dec]

Hello,

Is there any way to manage DMA channel assignments? My setup relies on 
Yamaha YMF724F for sound, due to there being no ISA slots to get a 
proper sound card. Unfortunately, there's no way to have the card work 
with DMA 1 or 3. It's stuck on DMA 0 and this is wrong in so many 
ways... I've researched this issue and turns out that DMA 0 was 
historically reserved for DRAM controllers, then it was a daisy-chain 
linking 8-bit and 16-bit DMA controllers. Most games I have support 
sound cards on DMA 0, but some have a more conservative design and won't 
budge. Even editing the config files to seemingly force this change will 
yield no result.


Best regards,

Michał



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

[Freedos-user] Invalid opcode - where do I even begin?

[Michał Dec]

Hello,

I've run some software on Pentium 3 Tualatin S on FreeDOS and it's 
getting an invalid opcode error. The error precisely says "Invalid 
opcode at ..." where ... is a bunch of 16 bit variables. Saying "at" is 
really misleading and doesn't make any sense, since such a high address 
like let's say 628a  3002 206f 2b43 202b 202d 6f43 7970 6972 6867 
2074 3931 is well within the realm of ZFS storage, not protected mode 
address space :D


If anyone's wondering, the offending software is Contra and Quake 1.08 
(software renderer). For what it's worth, the above hex string is 
exactly what Quake blurted out.


Where do I even begin with understanding this message? Is this a series 
of opcodes the CPU failed to run, or is this an address, or is it 
something else? I could recompile Quake, but Contra will probably 
require me to patch the binary with the help of reverse engineering tools.


Best regards,

Michał



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

[Freedos-user] FreeDOS and audio CDs

[Michał Dec]

Hello everyone,

I have this peculiar setup:

Lite-On LTR-52327S

Yamaha YMF724F

They're connected together with a CD cable. I've found that software 
that normally plays a CDDA soundtrack when it finds a CD with such 
tracks, just doesn't do it. The software I have:


GTA1

Redneck Rampage

Quake

I can also test with Rayman, but I really fear this game in particular 
as it's known to cause severe filesystem damage when it doesn't get what 
it wants.


The CDROM is initialized with SHSUCDX 3.07 with the FDC0001 driver and 
there's just no audio whatsoever. Redneck Rampage gives me a better idea 
by greying out its integrated 8-track player - a give-away sign that no 
CDDA tracks have been detected at all.


Has anyone run into this issue? I'm running on FreeDOS 1.2.

Best regards,

Michał



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

[Freedos-user] How to reinstall FreeDOS VBR?

[Michał Dec]

Hello,

I had FreeDOS as the only system on my CF card, but I had to scale down 
the FAT32 partition and make space for Gentoo Linux. After installing 
the other system, FreeDOS can't boot. Probably because the volume boot 
record was thrashed during the partition resize. Is there any way to 
reinstall only this component?


Best regards,

Michał Dec



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

Re: [Freedos-user] Moving beyond FAT

[Michał Dec]

Hello Eric,

Depends. If you want to be able to BOOT from ext4, you would
have to boot a virtual MEMDISK boot floppy from GRUB, then
load your new driver to open the ext4 partition ;-)
That sounds a lot like using an initramfs in Linux. Am I getting the 
right idea?

I would NOT attempt to make the kernel or disk tools (format,
chkdsk and similar) directly able to work with ext4.


Disk tools I can understand, that would require a meta-utility that can 
call filesystem-specific tools based on educated guesses and introduce 
universal command line arguments. But kernel? Why? The idea is that ext4 
would be a first-class citizen in kernel space just like FAT16 and FAT32 
are.



Of course you would be welcome to make DJGPP DOS ports of
mkfs.ext4 (mke2fs and fsck.ext4 (e2fsck) and so on.
When and if I get DJGPP working, sure. That's a topic for another 
thread. So far I could only get Perl going :)

Software which has trouble understanding network drives will
have trouble with your driver, too, but I would not worry
about that too much. You do want your driver to support any
long file name interfaces, I think. Having access to ext4
disks with only 8+3 character file names would be a pain ;-)

Also, you want to build some type of access rights and user
identities into the driver, to reduce the risk of breaking
contents. For example the user could have some user and group
identity which is used in the driver. There could be a command
to switch to another user and commands for chmod and similar.

This will of course NOT protect against deliberately breaking
things, because there is no protection against changing your
identity to the superuser and doing a deltree etc. :-p But it
would reduce the risk of accidentally damaging files.


I'm thinking of the following design decisions in that regard:

- FreeDOS would not mention ACLs, FreeDOS users lived happily ever after 
without them and they can live happily ever after while oblivious to 
their existence


- FreeDOS acts as root UID/GID in the context of reading and writing 
from the filesystem except,


- when creating new files and directories on existing ext4 filesystems, 
we must respect the corresponding sticky bit of their parent directory


I think these would be the least invasive should we ever decide to 
inspect a Linux installation under FreeDOS and from ACL perspective an 
installation of FreeDOS on ext4 would look the same as one from FAT. 
These decisions make sense to me since FreeDOS does not feature groups 
and users but it should also not break things for others.



But you say neither dosfstools (dosfsck) nor FreeDOS tools
(Do you use FAT16? Or FAT32?) fail to be able to repair the
damage. Now you have my attention! :-)

Please describe EXACTLY in which way the filesystem contents
are broken (no attached files please!) and in which way the
repairs STILL leave some (which?) damage.


It's FAT32 and at first. Here's what happened in chronological order:

1. I start the offending software.

2. It hangs and cuts off input devices, so I restart.

3. My SoundBlaster drivers (I'm using a Vibra 128) and initialization 
script for it are gone. I know this because trying to run the init 
script yielded IO errors in one of the files.


4. I shutdown FreeDOS and inspect that file on Linux - it does produce 
IO errors, it's completely unreadable.


5. I dismount and fsck.vfat -fa.

6. I try the offending software again. I have to restart because it hangs.

7. I get frustrated and repeat step 6, slightly changing the conditions 
so it hopefully doesn't hang this time. Ah who am I kidding, of course 
it did just that.


8. I realize my FreeDOS can't even shutdown itself by this point. The 
files required to do this are broken. So I try some tool (can't remember 
the name) from FreeDOS to fix this.


I can't remember by which point, but there were hundreds of numbered 
files in the root of my FAT32 filesystem. Probably recovered files, but 
the filenames were lost.



Your assumption seems to be that BTRFS and EXT4 would somehow
be immune to data loss at crashes because they are journaling.
Partly correct. You missed the part where I said FAT breaks so hard it 
makes BTRFS blush - that filesystem is also bad news for data integrity. 
Some design decisions you can't fix with journaling.

But as your software breaks FAT worse than chkdsk can repair,
I would not be too sure about that.

Another idea would be to use FDSHIELD to write-protect the
harddisk. Of course this only makes sense if your application
which does those data-destroying crashes does not need to
write anything to disk.
No, sorry. Rayman and Darkforces for DOS need to be able to write 
savestates to its installation directory once in a while. By the way, 
these are the culprits. The former is a heavy offender and will hold 
your data integrity at gunpoint if you don't even attempt to mount an 
ISO with the original CD's data track on it. If the perp is unsatisfied, 
it will present a "press this 

[Freedos-user] Moving beyond FAT

[Michał Dec]

Hello everyone,

Suppose I wanted to write an ext4 driver for FreeDOS and integrate it 
such that it's possible to use ext4 on a system partition. And let's say 
this plan materialized - would this have any effect on existing DOS 
software? I'll go on why do I even consider this, but I want to know if 
I'm not running the risk of breaking some functionality for let's say 
some cool games or their installers.


The reason I'm asking is because I've encountered software that forces 
me to forcibly reboot my DOS machine and this causes all mounted FAT 
partitions to break down. It happens because the software hanged itself 
and doesn't react to any input. FreeDOS' own filesystem repair tools and 
GNU dosfstools can't even repair all of the damage. So I understand that 
using FAT is harmful as it runs the risk of breaking during an 
unexpected power shortage in such ways that it'd make btrfs blush.


To rectify this, I would need to move to a different filesystem. ext4 
seems obvious for me because it's well documented, rock solid (by now, I 
know it would break in 2009) and it has a journal so we can always 
recover from any power loss induced filesystem damage.


Best regards,

Michał



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

Re: [Freedos-user] Benchmark volunteers wanted

[Michał Dec]

Hello Eric,

I would be very pleased to conduct tests that aren't just about 
permanent storage IO. I'm also curious how does FreeDOS perform.


I have such a platform:
- Abit VP6
- 2x Pentium 3 @ 1.4GHz (Tualatin, SMP compatible, require Lin-Lin 
sockets, usually running at 700MHz)

- 128MB SDRAM (will be expanding to 2GB PC133 this week)
- Voodoo 5500 AGPx4
- Sandisk 32GB CF over IDE 160MB/s read 100MB/s write (limited by 
onboard IDE controller to 100MB/s)


I know the 2nd CPU isn't usable in DOS, but it's there for other systems 
like ReactOS.


So, I would be more than happy to conduct all sorts of benchmarks. Just 
point me in the right direction :)


Best regards,

Michał

W dniu 12.07.2020 o 22:12, Eric Auer pisze:

Hi DOS users :-)

As FreeDOS has the reputation of having slow disk I/O,
I would like to get that quantified a bit... So if you
have not only FreeDOS but also other DOS brands on your
computers and can run the same tests on different DOS
versions on the same hardware, I would like to get in
touch with you :-)

Thank you! 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] SATA...

[Michał Dec]

Or if that fails, disable AHCI in the SATA controller. DOS is fine with 
drives talking in IDE mode.


W dniu 01.06.2020 o 14:58, Eric Auer pisze:

Michael,


My DVD RAM drive is SATA I...
Will Freedos support SATA I in the future?

FreeDOS already supports SATA. Use the UDVD2 driver,
which should be part of the distro already. If you
can not find it, I can give you some link / hint ;-)

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