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

2024-04-24 Thread 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

2024-03-16 Thread 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 
@call c:\util\audiopci\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

2024-02-28 Thread 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

2023-11-04 Thread 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

2023-11-03 Thread 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?

2023-11-01 Thread 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?

2023-11-01 Thread 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

2023-11-01 Thread 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?

2023-11-01 Thread 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?

2023-10-31 Thread 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?

2023-10-31 Thread 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)

2023-10-04 Thread 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

2023-09-25 Thread 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

2023-09-24 Thread 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

2023-09-24 Thread 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

2023-09-24 Thread 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

2023-08-19 Thread 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