Re: [Freedos-devel] No simple cpu identification program returning an error code as an answer?
Hi, On Fri, Aug 26, 2022 at 1:27 PM Paul Dufresne via Freedos-devel wrote: > > Following the modification of my idea proposed by Tom: run edit32 on 386+ > else run edit... BTW thanks Tom! I believe CC386 had a 386+ text editor also using D-Flat. > I have been looking a bit for a simple program that would identify > approximate CPU and return it as an error code that batch file could used. > I did not found that (especially with free license)... so that I am thinking > about writing one. > Just asking if that exist already here. Eric Auer wrote this one years ago: * https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/system/cpulevel/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Ré : suggested qemu command line to boot FreeDOS
Searching a bit more, I now come with: "qemu-system-i386 -name FreeDOS -machine pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -enable-kvm -cpu 486 -m 64 -overcommit mem-lock=off -no-user-config -nodefaults -rtc base=utc,driftfix=slew -no-hpet -boot menu=on,strict=on -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on -drive format=raw,file=fdt2208.img,format=raw -cdrom T2208LIVE.iso -audiodev pa,id=mysnd -device sb16,audiodev=mysnd -device adlib,audiodev=mysnd -machine pcspk-audiodev=mysnd -vga cirrus -display sdl -usbdevice mouse" which should enable adlib and sb16 emulation (I think my previous message did not)___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] suggested qemu command line to boot FreeDOS
I begin with suggested line in: http://www.freedos.org/books/get-started/june14-manual-install.html after creating the hard disk image with: "qemu-img create fdt2208.img 600M" I am now using: "qemu-system-i386 -name FreeDOS -machine pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -enable-kvm -cpu 486 -m 64 -overcommit mem-lock=off -no-user-config -nodefaults -rtc base=utc,driftfix=slew -no-hpet -boot menu=on,strict=on -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on -drive format=raw,file=fdt2208.img,format=raw -cdrom T2208LIVE.iso -audiodev alsa,id=mysnd -machine pcspk-audiodev=mysnd -vga cirrus -display sdl -usbdevice mouse" To be honest I don't understand all the options. "-cpu 486" is probably slower than "-cpu host" but should give more similar results on different computers on which it is run. The change is mostly a more recent version of defining sound devices (well, pa was maybe more recent... and unsure if pa would work), and also specifying raw format to avoid restriction on block 0. On some other system, I removed "-display sdl" as it was necessary because qemu was not compiled with SDL option (OpenSUSE Tumbleweed).___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?
On 8/25/2022 4:44 AM, Carsten Strotmann wrote:
Hi,
On 25 Aug 2022, at 9:41, Paul Dufresne via Freedos-devel wrote:
While thinking about 64k limit for edit... I come to think about 16 bits and 32
bits programs...
the 64kb limit is an artificial limit in the source code of the "edit" tool:
https://gitlab.com/FreeDOS/base/edit-freedos/-/blob/master/SOURCE/EDIT/EDIT.C
/* check file size */
if (sb.st_size > 64000UL)
{
ermsg = DFmalloc(strlen(FileName)+100); /* alloc fixed 0.7a */
strcpy(ermsg, "File too large for this version of Edit:\n");
strcat(ermsg, FileName);
ErrorMessage(ermsg);
free(ermsg);
return;
}
The program "edit.exe" is compiled in the "large" memory model, it *should* be
able to use the whole available DOS memory, at least more than 64kb.
Maybe it's time to remove that limit from the tool.
That is likely not that easy. Even in the LARGE memory module, single
objects are likely limited to 64KB (minus some overhead), so it isn't as
easy as just removing what you call "artificial limit"...
Ralf
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?
On 8/25/2022 12:41 AM, Paul Dufresne via Freedos-devel wrote: While thinking about 64k limit for edit... I come to think about 16 bits and 32 bits programs... Why there is no two separate versions of FreeDOS, one for 16 bits CPUs (8086) and one for 32 bits CPU (386+)? It seems there is a lot of programs that cannot run on 8086... and others that could take advantage of 32 bits compilation. Does it should not suggest to have two separate versions foir this relatively different needs? Just because a program is 16bit vs 32bit doesn't make things like EDIT automatically able to work with files larger than 64KB. It's a matter of the library used to create EDIT (I think it's based on the OSS version of TurboVision). To overcome this, you are pretty much going to have to re-write the program from scratch. Knock yourself out... Ralf ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] No simple cpu identification program returning an error code as an answer?
Have you tried pcem? https://pcem-emulator.co.uk/ Emulates cpus, video cards and more !! El vie, 26 ago 2022 a las 21:01, Paul Dufresne via Freedos-devel (< freedos-devel@lists.sourceforge.net>) escribió: > Thanks Jim about VINFO /m to detect CPU! > I did not knew it, or at least I had totally forgotten it. > > The sad part of it, is that it is so fancy that one cannot use virtual > machines to test different CPUs, because it detects the virtual machine > rather than the virtual CPU. > > So that Eduardo's one might be more what I want to use... I'll have to try. > > > > > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] No simple cpu identification program returning an error code as an answer?
Thanks Jim about VINFO /m to detect CPU! I did not knew it, or at least I had totally forgotten it. The sad part of it, is that it is so fancy that one cannot use virtual machines to test different CPUs, because it detects the virtual machine rather than the virtual CPU. So that Eduardo's one might be more what I want to use... I'll have to try.___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] No simple cpu identification program returning an error code as an answer?
On Fri, Aug 26, 2022 at 1:27 PM Paul Dufresne via Freedos-devel wrote: > > Following the modification of my idea proposed by Tom: run edit32 on > 386+ else run edit... BTW thanks Tom! I have been looking a bit for > a simple program that would identify approximate CPU and return it > as an error code that batch file could used. I did not found that > (especially with free license)... so that I am thinking about writing > one. Just asking if that exist already here. > You can use VINFO, part of Jerome's V8 Power Tools, which is installed as part of FreeDOS. >/M Return Machine Type (This may break on future platforms) >Returns these exit codes: >0 - Unknown, Normal or Native 8086 Hardware. >1 - 80186 >2 - 80286 >3 - 80386 >4 - 80486 >5 - 80586 >6 - 80686 or better > 101 - DOSBox. > 102 - QEMU. > 103 - VirtualBox. > 104 - VMware. > 200 - General, other emulator detected. For example, if I boot FreeDOS in VirtualBox and run the following TEST.BAT file, I get 103, indicating VirtualBox: @echo off vinfo /m echo %ERRORLEVEL% If I boot FreeDOS in QEMU and run the same TEST.BAT file, I get 102, indicating QEMU. Jim ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] No simple cpu identification program returning an error code as an answer?
Hi Paul, I've just put this together with the cpu identification code I use in vmsmount. Tested only in a 386, I don't have an 8086 emulator at hand. https://github.com/eduardocasino/cpucheck.git Cheers, Eduardo El vie, 26 ago 2022 a las 20:26, Paul Dufresne via Freedos-devel (< freedos-devel@lists.sourceforge.net>) escribió: > Following the modification of my idea proposed by Tom: run edit32 on 386+ > else run edit... BTW thanks Tom! > I have been looking a bit for a simple program that would identify > approximate CPU and return it as an error code that batch file could used. > I did not found that (especially with free license)... so that I am > thinking about writing one. > Just asking if that exist already here. > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] No simple cpu identification program returning an error code as an answer?
Following the modification of my idea proposed by Tom: run edit32 on 386+ else run edit... BTW thanks Tom! I have been looking a bit for a simple program that would identify approximate CPU and return it as an error code that batch file could used. I did not found that (especially with free license)... so that I am thinking about writing one. Just asking if that exist already here.___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?
On Fri, 26 Aug 2022 00:21:52 +0200 tom ehlert wrote: > I think even newbies should be given the chance to select from > > > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/group-edit.html It depends what you mean by "newbies". But if you mean people that just use computers and do not care at all about how or why they work, giving a choice of editors is an idea that assumes way more competence then the average computer user has. These people are typically lost with any program that isn't point and click. The easiest console text editor ever is norton editor and it's clones. It allows point and click provided the mouse driver is loaded. If there is no point and click at least the menu bar at the top provides a clue that there must be some way to get there. "^Q" "^S" at the bottom of the screen doesn't cut it. It just crams more information on the screen for those who know what they are doing. It's a common UNIX trope that "joe", "pico" or "nano" and friends are easy to use text editors. Compared to vi and that other text editor that's only missing a boot loader to be an OS, they certainly are. But I can tell you from experience that there are many people who are completely lost with nano. They have no clue what a keyboard shortcut is beyond at best (if you're lucky) "CTRL+C" "CTRL+V". They have no clue that '^' means the CTRL key. They're never ever going to RTFM because they've never had to so far. They're not going to think about typing "How to quit nano" in Google. You'd be surprised how many people are unable to do this. And they're going to abandon after 5 minutes of fiddling. If the editor is not running in a window inside a desktop environment where they can just close the window, they're going to hit the power switch (which fortunately is not a problem in DOS) rather than spend ten minutes trying key combinations to quit the editor. I've seen this scenario unfold a few times to my amazement. Despite it's flaws, it's a great thing that FreeDOS Edit is the default text editor in FreeDOS. Many are never to bother with anything else. Giving a choice of default text editor is a russian roulette footgun for newbies. -- WWW: https://metalpunks.info GPG: C90CAB7122AC1231 pgpi_A69inezu.pgp Description: OpenPGP digital signature ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?
Hi tom, > just remember that we had even the holy > https://en.wikipedia.org/wiki/Editor_war Sure, I know about the Emacs vs vi war. I tried Emacs more than vi, because I found Org mode very interesting for managing my notes and such stuff. It's only few years ago, but I can't remember any of Emacs' keystrokes. But I still remember vi's ":q!" or ":wq" command. (Not to start the war again here:) If I had to decide between the two, _I_ would go with vi now. Background: Very often, I'm not on my own machine and I'm not allowed to install another text editor or just run a portable version. So I stick to standard Windows Notepad. On my own machines I run Notepad2e. > how would we be able to indoctrinate newbies into one single editor > religion? Why should we? > I think even newbies should be given the chance to select from > > > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/group-edit.html > > and multiple other sources to change their own religion? Sure. Where did I say anything else? > disclaimer: I'm probably no expert in DOS editors (anymore). _I_ never was. ;-) I used many and all had their pros and cons. That's how life is. > of course, if as a hobby you want to have a feel for 1980 XT developement > pain you > should use edlin. > > ok, nobody used edlin ever. but professional editors could be > pricey... > > but still nobody used edlin. ever. I would prefer debug's "e" command for that. ;-) Cheers, Robert -- BTTR Software https://www.bttr-software.de/ DOS ain't dead https://www.bttr-software.de/forum/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Status of OpenSSL in FreeDOS?
Hi! I began investigating an issue with curl related to https urls complaining about not having enough randomness: https://gitlab.com/FreeDOS/net/curl/-/issues/1 I suspect that this is a problem related to OpenSSL... and might affect the web browsers too, but I did not even tried. I don't know if theses issues were known... not using much networking in the past. As you can see with curl 7.77 (latest being 7.84) the randomness issue disappears but then show a problem with accepting certificates. Which make me ask: What is the status of https with FreeDOS? We don't package OpenSSL library... but it is coming from DJGPP project... as far as I know. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
