Re: [Freedos-devel] FreeDOS 1.4

Tue, 19 Nov 2024 06:48:26 -0800

 
 Hi Jerome,
referring to networking and fdnpkg:
 
As already told, in virtual box networking works automatically after installation, but fdnpkg install pkg stops after downloading 100 % just before starting with extraction.
You got some screenshots from me.
 
qemu:
Win-version of qemu:
I did not get it work. Maybe it is a driver problem. NE8139 caused a freeze.
 
Linux version of qemu:
The vm is not known and shown and network does not work.
So I added a "lh C:\REAL8139\rtspkt.com 0x60" one line before:
"call %DOSDIR%\BIN\fdnet.bat" in fdauto.bat
and it worked fine with fdnpkg.
 
Willi
 
Sent: Saturday, November 16, 2024 at 9:55 PM
From: "Jerome Shidel via Freedos-devel" <freedos-devel@lists.sourceforge.net>
To: "FreeDOS Developers" <freedos-devel@lists.sourceforge.net>
Cc: jer...@shidel.net
Subject: Re: [Freedos-devel] FreeDOS 1.4
 
 
On Nov 16, 2024, at 1:08 PM, Fritz Mueller via Freedos-devel <freedos-devel@lists.sourceforge.net> wrote:
 
OK,
here are some things that I noticed:
 
fdauto.bat:
in about line 44, I already found it in FDT2408 (maybe earlier too):
":NoCodePagerem keyboard settings"   (followed by)
MKEYB GR   
I found NO such goto label. Only "NoCodePage". Assume it is a typo (rem keyboard settings)
 
This is most likely caused by the “new auto and config files”.
 
The installer splices in those settings from other files. It could be a typo in one of many places, or simply a missing CR in one of those areas. 
 
Send me a copy of the installed version of FDAUTO which I could examine to locate the issue.
 
 
MKEYB GR:
On my old laptop there is no support for different characters, e.g. backslash, pipe etc. Reason: version 0.52 of mkeyb requires the option /e for keyboards with
more keys.
 
Not sure what you are asking for here. 
 
Are you asking for the primary German keyboard layout to be changed?
 
 
country.sys:
Hope FDT2412 and "upcoming version" will work now with german settings.
 
There was the update to the Country.sys package. So, ?
 
 
 
fdnpkg with virtualbox:
Works fine on an old real machine after I added the network driver.
On virtual box it actually has two different problems:
a)The first was that fdnpkg can be used, you can run checkupdates and install etc., it starts with downloading the zip files till 100 percent - and then it hangs.
It looks as if the unpacker or the installation routine has a problem.
 
Most likely this is a regression issue with VirtualBox. 
 
Version 7.x has severe problems on this Mac Pro when trying to use FreeDOS. No client configurations seemed to help at all. While the install process worked fine and everything used by the installer worked. Most other programs would crash.
 
No Idea why. I tried numerous config settings nothing helped. I ended up rolling back to VirtualBox 6.x and problems vanished.
 
b) NOW there are other messages:
Loading http://www.ibiblio.org...blabla.../latest/sound...
Error. Invalid index file! Repository skipped.
An error occured while trying to load repository from tmp file...
Error code: 0     (eehmmm?)
and so on with next repository.
 
Since switching over to the built-in indexing, there appears to be a slight issue regarding the creation of CRC32 data that is included in the index file. Probably either a minor config related problem or type somewhere. Somewhere, it was looking for the CRC32 and not crc32 binary. 
 
For now, I simply created a CRC32 symlink to crc32 and told it to rebuild the index. It should fix that problem. At some point when I have the time, I’ll dig into actually fixing the real issue.
 
Should work now.
 
 
 
fdnpkg with qemu (with Windows Qemu manager 7.0)

I ran a FULL installation in QEMU and got the message: NO PACKET DRIVER FOUND.
 
Is it trying to start networking? 
 
Or, it this version of QEMU no being detected as QEMU?
 
In other words, do you see a message from FDNET about not being supported on real hardware?
 
 
The installation with Qemu manager offers several network drivers:
 
Realtek 8139, NE2000PCI, Intel 82551, Intel 82557b, Intel 82559e, Intel E1000, PCNetLanCard, Virtio.
 
Anyhow I was unable to activate the network automatically. Which card do I have to choose for automatic installation?
 
Qemu manager and keyboard:
There are some strange behaviours in Qemu, especially with "edit".
I had problems with "ALT-F" and then "X" for exit, arrow up and down (they sometimes caused repeating a character) etc.
 
 
Two proposal for upcoming 1.4 FD installation CD:
 
On modern systems it is unusual that the BootCD boots twice (because fdisk requires a reboot). A short message in the installation routine that it has to boot
twice would be very helpful for newbies, otherwise they may think that something goes wrong.
 
The installation CD offers some keyboard layouts without codepage settings etc. The result is not the optimum. Would it be possible to add the settings for those
countries, e.g.:
 
Israel:
fdconfig.sys:
COUNTRY=972,862,C:\FREEDOS\BIN\country.sys
fdauto.bat:
set LANG=IL
LH DISPLAY CON=(EGA,,1)
MODE CON CP PREP=((862) %DOSDIR:\CPI\EGA17.CPX)
MODE CON CP SEL=862
MODE CON CP REFRESH
keyb il,862,C:\freedos\bin\keybrd3.sys
(mkeyb HE works with right CTRL button, this causes problems in virtualbox)
Comment: ALT+right SHIFT=HE chars, ALT+left SHIFT=latin chars
In "edit" ALT+right /left SHIFT has to be pressed twice!
In "mined" ALT+right / left SHIFT has to be pressed once!
 
I don’t think that is actually possible. Keyboard settings are not the same thing as CODEPAGE and COUNTRY settings. 
 
At some point it would be nice to include a few extra batch helpers, once installed a user could maybe run SETLANG.BAT to better configure keyboard and display settings. 
 
 

_______________________________________________ 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























					Reply via email to