Re: [Freedos-devel] splash screen

2017-11-22 Thread Jerome Shidel
> On Nov 22, 2017, at 10:04 AM, Jim Hall wrote: > [...] > Not really. We had a similar discussion about a much earlier FreeDOS > release, and it doesn't make sense to have a graphical splash screen > for FreeDOS. Since FreeDOS runs in "text mode" and isn't a GUI on its > own, it would be confusi

[Freedos-devel] bcc (was: Compiling with gcc)

2017-11-22 Thread Andreas K. Foerster
Am Mittwoch, dem 22. Nov 2017 schrieb Tom Ehlert: > as a side note: if gcc has no far pointers, its usability as a 16 bit > compiler is serious limited. Sorry, the topic shifted. I'm not talking about gcc, but about bcc (Bruce's C-Compiler). I haven't checked out the 16-bit part of gcc yet. Note

Re: [Freedos-devel] splash screen

2017-11-22 Thread Jim Hall
On Wed, Nov 22, 2017 at 8:27 AM, Jerome Shidel wrote: > I gave thought to this when creating FDI. >[..] > You could easily add a splash screen to your own custom USB installer. > > I have no idea wether or not Jim would want a splash screen added for the > next OS release. > Not really. We had a

Re: [Freedos-devel] Compiling with gcc

2017-11-22 Thread Tom Ehlert
Hallo Herr Andreas K. Foerster, am 22. November 2017 um 15:25 schrieben Sie: > Am Mittwoch, dem 22. Nov 2017 schrieb Tom Ehlert: >> > Are there any documented limits for environment variables in DOS? >> no. >> >> > My implementation uses a static buffer. So the content changes with >> > every c

Re: [Freedos-devel] Compiling with gcc

2017-11-22 Thread Tom Ehlert
> I didn’t read most of the messages in this thread. So, forgive me > if I have completely missed something important. > Why allocate any memory for reading the environment variables? > Why not just examine them in place? They are just Null terminated strings. they are just zero terminated stri

Re: [Freedos-devel] Compiling with gcc

2017-11-22 Thread Jerome Shidel
I didn’t read most of the messages in this thread. So, forgive me if I have completely missed something important. Why allocate any memory for reading the environment variables? Why not just examine them in place? They are just Null terminated strings. --

Re: [Freedos-devel] splash screen

2017-11-22 Thread Jerome Shidel
I gave thought to this when creating FDI. I figured that the standard release could have one. But, it was not needed and would use more precious disk space on the boot floppy. However, an OEM vendor that shipped on of those FreeDOS systems may desire to display their logo or something. So, th

Re: [Freedos-devel] Compiling with gcc

2017-11-22 Thread Andreas K. Foerster
Am Mittwoch, dem 22. Nov 2017 schrieb Tom Ehlert: > > Are there any documented limits for environment variables in DOS? > no. > > > My implementation uses a static buffer. So the content changes with > > every call to getenv. This is explicitly allowed by the standard. > > > I don't want to make

Re: [Freedos-devel] splash screen

2017-11-22 Thread Andreas K. Foerster
Am Mittwoch, dem 22. Nov 2017 schrieb Tom Ehlert: > > Currently I'm experimenting with graphics modes and I thought, > > it would be a good idea if your installer starts with a splash screen. > > it is not. > > maybe for a (grafic) game or paint program, where a splash screen is shown > while in

Re: [Freedos-devel] Compiling with gcc

2017-11-22 Thread Tom Ehlert
> Are there any documented limits for environment variables in DOS? no. > My implementation uses a static buffer. So the content changes with > every call to getenv. This is explicitly allowed by the standard. > I don't want to make the buffer too large though, did you ever hear about dynamic ma

Re: [Freedos-devel] splash screen

2017-11-22 Thread Tom Ehlert
> Hello, > Currently I'm experimenting with graphics modes and I thought, > it would be a good idea if your installer starts with a splash screen. it is not. maybe for a (grafic) game or paint program, where a splash screen is shown while in the background magical things are happening. certain