Re: [Freedos-user] MSdos 7.1 question

[tom ehlert via Freedos-user]

> 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.
FAT files definitively can't be bigger then 4GB (ignoring FAT+) because the 
'file size field' has only 32 bits.


I am *mostly* sure that 
file size was limited to 2GB in MSDOS < 6.2
file could grow to 4GB if you indicated 'I am aware of signed/unsigned 
problems'
  at file creation/opening time

I am *mostly* sure that 
   FreeDOS just has a 4GB limit.

it's not that complicate to test this - and ascertain or deny this.

as a side note: disks bigger then 1GB just weren't available at MSDOS times.
so this was never a theme.



Tom
 



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

Re: [Freedos-user] languages

[tom ehlert via Freedos-user]

Hi,

> It's been a while since i use freedos on asus eeepc with portuguese from
> portugal and if i recall i can't write the * with shift and *+" key and
> since there is no numeric keypad.

a) what keyboard driver are you using?
b) IIRC (20 years later) there was 'portuguese' and 'portuguse brazil'.
   which one?

>  "i can't write the * with shift and *+" key"
c) about the worst bug complaint ever. you don't deserve a better keyboard 
driver ;(

Tom






> I haven't tested on a vm...

> On Fri, Sep 29, 2023 at 9:03 AM Eric Auer via Freedos-user <
> freedos-user@lists.sourceforge.net> wrote:

>>
>> Hi!
>>
>> > FreeDos need's update in the keyboard and languages, there is support for
>> > that in open-source environments, but I don't know how to implement them.
>> > For example I'm using a portuguese keyboard and it doesn't support it, so
>> > Iam in trouble's
>>
>> Actually FreeDOS has no problems with Portuguese keyboards. Even
>> the tiny MKEYB driver supports them. If you run MKEYB /? you will
>> see that MKEYB /L shows a list of supported keyboards, which does
>> include Portuguese. So you could run MKEYB PO to activate keyboard
>> support in Portuguese style, or you could add a line saying MKEYB
>> PO to your autoexec.bat or fdauto.bat, depending on which of the
>> two you are using. Our other keyboard drivers also support your
>> layout, you just have to read the documentation to find out how
>> to activate it, as they are a bit more complicated to set up :-)
>>
>> Best regards, Eric
>>
>>
>>
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>





Mit freundlichen Grüßen / with kind regards
Tom Ehlert
+49-15151898538



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

Re: [Freedos-user] languages

[tom ehlert via Freedos-user]

Hi,

> i' m from Portugal and i'm aware of the portuguese layout for 43 years.
> When i press that key produces a A with a ring on top.

it helps if you say "the key right of 'P' should produce '+' and '*' in shifted 
state.

and indeed mkEYB has this wrong (for whatever reason).

i just filed this as an issue on the GITHUB project page.
Tom



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

Re: [Freedos-user] Basic freedos question before I try this?

[tom ehlert via Freedos-user]

> I have it myself already, unless there has been a update, but wanted to ask.

please explain this. 

Tom



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

Re: [Freedos-user] Accessing usb stick from freedos.

[tom ehlert via Freedos-user]

> Newer version of Windows seem to have problems with accessing 
> drives/partitions over 32GB as well. 

I would be seriously surprised. Windows refuses to *format* drives above 32GB 
as FAT32, but simply
works with it up to maximum capacity of (2^32 * sectorsize) which is usually 
2TB.

FreeDOS doesn't support sectorsizes other then 512, so anything up to 2TB 
should be supported. 


Tom



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

Re: [Freedos-user] Accessing usb stick from freedos.

[tom ehlert via Freedos-user]

>> The alleged 4 GB file size doesn't work on some OSes (FreeDOS, Windows
>> NT?), only on old Win9x. So you're only guaranteed 2 GB individual
>> file sizes, universally.
> Wrong. You can use files of up to 4GB size on any Windows version that 
> supports FAT32. So does any reasonable version of Linux. Yes, some OS might 
> limit you to 2GB, as they are using a signed 32bit integer, but that is far 
> from being "universally".

the problem here is probably that early OS versions had checks that the file 
pointer was never moved below zero.

i.e. 
  move to 1.5 GB
  read stuff.
  move to 3.7  GB (which is 2.2 GB which is negative 1.8 GB)
  // what is the OS supposed to do?


the 'solution' was (IIRC) to require applications in the OPEN call to 
indicate "yes, I understand 32 bits"

FreeDOS does this by default.



Tom




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

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

[tom ehlert via Freedos-user]

Hallo Herr Aitor Santamaría via Freedos-user,


> What is LIDOS?
> (Couldn't find any reference on the Internet)

it might help to use the intended spelling "Lidux"

Tom


> Aitor


> On Fri, 20 Nov 2015 at 17:08, Alain Mouette  wrote:

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



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

Re: [Freedos-user] AUTO SHIFT keyboard on DOS??

[tom ehlert via Freedos-user]

Hallo Herr Thomas Cornelius Desi via Freedos-user,

am Donnerstag, 8. Februar 2024 um 13:18 schrieben Sie:

> Hi,

> is it possible in DOS (using BIOS?) to implement a tsr or so which allows the 
> following:

> holding a key longer to return a SHIFT-key on screen?

> Example: 

> press key »a«  and HOLD the key for e.g. 500 milliseconds,  
=>> print shift-a = »A« on screen.

> Anyone around who has an idea or knowledge if this is possible or has been 
> done or any hints where to look?

this would go to the keyboard driver as only it knows to differentiate between


A-pressed A-pressed --> A

A-pressed A-released A-pressed --> a

only problem would be that your typin speed is now limited to 1 haracter per 
e.g. 500 milliseconds.
not very practical.

Tom



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

Re: [Freedos-user] AUTO SHIFT keyboard on DOS??

[tom ehlert via Freedos-user]

Hallo Herr tsiegel--- via Freedos-user,

am Donnerstag, 8. Februar 2024 um 23:41 schrieben Sie:


> On 2/8/2024 3:34 PM, tom ehlert via Freedos-user wrote:

>> only problem would be that your typin speed is now limited to 1 haracter per 
>> e.g. 500 milliseconds.
>> not very practical.

> Not at all.  A keyboard driver is going to know when a key is released, as 
> well as when it's pressed.  Nothing preventing it from operating normally 
> when it's released fast enough, and only shifting the character if it isn't 
> released in the alotted time. It doesn't restrict typing speed in the least 
> (with the exception of course of making the capital letters.).

rethinking this, you are right.

if the scancode is interpreted/send to the BIOS as soon as some other scancode 
is detected
(either other key depressed or key-released) typing speed would not be limited.

only "do you agree Y/N" would be limited if you HOLD the Y key. probably not a 
problem.

> I've never tested it, but if you have key repeat turned off, then it's likely 
> the character doesn't appear until you release the key anyhow, so ... 

yes, this feature would require BIOS key repeat and replace it with "automatic 
shift".
I don't see a big problem here as long as this is choosable. 

big problem here is that noone will implement it. 

even bigger one that DOS/WINDOWS/Linux/MacOS would be different. I SHOULD HAVE 
WRITTEN THIS IN ALL CAPS.

Tom
   



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

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

[tom ehlert via Freedos-user]

> Indeed, I'm using an old-school program called Qmodem.

>  My question now is – would I be able to use the Internet using the emulated 
> modem?
yes (if you had any idea what you are doing). But definitively not with QMODEM.

Tom


> Brandon Taylor
> 
> From: Jim Hall via Freedos-user 
> Sent: Tuesday, April 23, 2024 10:12 PM
> To: Discussion and general questions about FreeDOS. 
> 
> Cc: Jim Hall 
> Subject: Re: [Freedos-user] Dial-up emulation?



> On Tue, Apr 23, 2024, 9:38 PM Brandon Taylor via Freedos-user 
> mailto:freedos-user@lists.sourceforge.net>>
>  wrote:
> 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...

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


> Well, it's not that "FreeDOS" would support the Hayes modern, but that 
> terminal/dialer software would then be able to. FreeDOS is not like Linux, 
> which uses a Hardware Abstraction Layer (HAL) to support the hardware 
> directly. FreeDOS, like any DOS, does normal DOS things and leaves certain 
> hardware access (like playing sounds through a sound card, or accessing a 
> network to browse the web or check email, or dialing out through a modem) to 
> other software.

> So if you had a terminal/dialer program like Procomm or Telix, then yes, I 
> expect you'd be able to dial out through this emulated Hayes modem from 
> FreeDOS.





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

Re: [Freedos-user] cannot boot installation media

[tom ehlert via Freedos-user]

> Eh... I tried every single BIOS setting 

at least on my Dell notebook there is no such *setting*.

instead I have to hit F12 while booting, this then sends me to a "select boot 
device",
where I can tell it to boot from USB

Tom



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

Re: [Freedos-user] cannot boot installation media

[tom ehlert via Freedos-user]

Hallo Herr Davi Ramos via Freedos-user,

am Sonntag, 28. April 2024 um 05:28 schrieben Sie:

> So, as I said in another message, I have a computer where I wish to install
> FreeDOS. It is a *Compaq Presario 427, Intel Pentium N3700, 4GB RAM, SSD
> 240GB, and a 14" screen.*

> Unfortunately, I cannot get it to boot the installation media
> .
> I have tried numerous USB flash drives as well as an SD card.

100 messages later we still don't know what "I cannot get it to boot" exactly 
means, as in

a) the stick is not detected
b) the stick is detected but ignored
c) refuses to boot the freedos strtup files
d) what does the screen look like in your failed boot attempts,
or does it continue to boot from hard disk?

if the stick isn't detected at all it doesn't matter if you put windows, linux 
or freedos 
on the stick or if your BIOS is running in UEFY or LEGACY mode


Tom





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

Re: [Freedos-user] the msdos 4.0 sources has some multitasking code

[tom ehlert via Freedos-user]

> I think, applying Hanlon's Razor here, that this was a chance
> discovery by someone else, and led to the release. Microsoft is not
> willing to go to even the minimal effort of searching its own archives
> for the other versions to release them, but if someone else finds the
> code, it will permit the release under a permissive licence.

there is no need for Microsoft to search its own archives.
MSDOS 6.22 source leaked to the internet some 22 years ago, and a plenty of 
people have it.

I don't understand how this would permit the "release under a permissive 
licence".

Tom



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

Re: [Freedos-user] Coding in BASIC for Freedos?

[tom ehlert via Freedos-user]

Hi Jim,

> On Sun, Mar 17, 2024 at 6:26 AM Liam Proven via Freedos-user
>  wrote:
> [..]
>> There are good reasons that DOS went away some 35 years ago. It has
>> its uses but not being able to flip to another window or another
>> screen to consult documentation, or try something out, or look it up
>> online, is a *massive* handicap.

+1

> That's a very interesting way of "advocating" FreeDOS, and "helping"
> folks who are new to FreeDOS.
I think Liam's post was not about "advocating" FreeDOS, but about "helping"
a nooby user.



> Here we have a person who discovered FreeDOS, who wants to experiment
> with FreeDOS by writing programs with it, and was looking for pointers
> to get started. 
Nope. AFAICT it's a person wanting to learn programming; no mentioning of 
FreeDOS.

And learning FreeDOS and learning programming at the same time is taking Two 
steps at once.
Usually not a smart idea.


> It's a very odd reaction to immediately tell that
> person to go find another operating system. That's not very welcoming.

> If someone discovers FreeDOS and wants to explore FreeDOS, we should
> help them find a way to "Yes" and not to "No."
it should be a serious reply.
in this case I'd vote "probaly not unless the original BASIC is a DOS based 
BASIC".
even then use a 32 Bit version of Windows(if the intended use case is learning 
to program). 


> And if something goes really wrong (like you did
> something weird in a new program you wrote, and it crashes and locks
> up the system) you just reboot.

I simply guarantee that you won't be able to write a program that crashes any 
version of modern Windows Dosbox.
I fail to see the advantage.

Tom  



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

Re: [Freedos-user] Portuguese keyboard layout

[tom ehlert via Freedos-user]

> Same problem, don't think that there is a solution.


The current MKEYB should have this problem resolved.

https://github.com/davidebreso/mkeyb/releases/tag/v0.52

Tom



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

Re: [Freedos-user] Portuguese keyboard layout

[tom ehlert via Freedos-user]

Manuel,

> Tom, thank you for the update, however the problem persists with version
> 0.52.

iT looks like Daide forgot To update this mkeyb.exe.

howeer from The source directory or 
https://github.com/davidebreso/mkeyb/blob/main/mkeyb.exe
 
does produce '*' and '+'.

Tom 



> Regards,
> Manuel

> On Tue, Mar 19, 2024 at 5:12 PM tom ehlert via Freedos-user <
> freedos-user@lists.sourceforge.net> wrote:

>>
>> > Same problem, don't think that there is a solution.
>>
>>
>> The current MKEYB should have this problem resolved.
>>
>> https://github.com/davidebreso/mkeyb/releases/tag/v0.52
>>
>> Tom
>>
>>
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>





Mit freundlichen Grüßen / with kind regards
Tom Ehlert
+49-15151898538



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

Re: [Freedos-user] DOS Actively Used Scenarios

[tom ehlert via Freedos-user]

> 1. The computer powers on and does a Power On Self Test ("POST") to
> verify that the hardware is working, then loads the kernel (FreeDOS)

Nope. The computer (the BIOS) reads the first sector from the firat hard disk,
and jumps to it. Usually, but not necessarily, this happens to have some code,
and a "partition table", which is a list of disk partitions where filesystems 
start. 

this code searches the partiton table for a partition marked "active", reads the
first sector of it, and jumps to it. 

Usually, but not necessarily, this code understand the file system of *this* 
partition.
FAT16/32 for FreeDOS, maybe EXT4 for linux, NTFS for Windows.

it then searches for the OS File(s) (which in case of freedos are named 
KERNEL.SYS, but could 
be some bootmanager (like GRUB) that helps load several different partitions 
from different locations
on the disk). 

> 2. The FreeDOS kernel reads \FDCONFIG.SYS (or \CONFIG.SYS) to read its
> configuration - this might include SHELL to tell the kernel which user
> shell to use

...

Tom



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