Re: [Freedos-user] ChkDsk / ScanDsk for Fat32
Hi Mateusz, Thanks for the pointer! Unfortunately, that one wants some DPMI memory: "Load error: no DPMI - Get csdpmi*b.zip" That's my current config.sys part on that USB-Sticks, which run that FoxPro program: device=c:\freedos\jemmEx.exe PGE maxext=32000 noems Do I need to add that csdpmi stuff, or is it possible to configure DPMI with the standard Freedos options? Greetings from Bavaria, Germany! Jürgen -Ursprüngliche Nachricht- Von: Mateusz Viste via Freedos-user Gesendet: Freitag, 15. September 2023 21:54 An: freedos-user@lists.sourceforge.net Cc: Mateusz Viste Betreff: Re: [Freedos-user] ChkDsk / ScanDsk for Fat32 On 15/09/2023 19:42, Jürgen Wondzinski via Freedos-user wrote: > Is there a ChkDsk or ScanDsk etc available for FAT32? > The usual chkdsk92.exe doesn't support this. You might want to try DOSFSCK. Mateusz ___ 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
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] ChkDsk / ScanDsk for Fat32
On 25/09/2023 11:20, Jürgen Wondzinski via Freedos-user wrote: Thanks for the pointer! Unfortunately, that one wants some DPMI memory: "Load error: no DPMI - Get csdpmi*b.zip" That's my current config.sys part on that USB-Sticks, which run that FoxPro program: device=c:\freedos\jemmEx.exe PGE maxext=32000 noems Do I need to add that csdpmi stuff, or is it possible to configure DPMI with the standard Freedos options? You only need to install CWSDPMI.EXE in your %PATH%. Mateusz ___ 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
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___ Freedos-user mailing list Freedo
Re: [Freedos-user] Planning the FreeDOS "2024" calendar
Hi, On Sun, Sep 24, 2023 at 1:13 PM Jim Hall via Freedos-user wrote: > > I'm making a FreeDOS "2024" calendar, and looking for suggestions of > what screenshots to include in it. Any ideas? > > Looking for suggestions of what screenshots you think would be great > to have in the calendar. RHIDE, based upon SETedit, still looks quite nice to me. Or GNU Emacs (DJGPP port). You were also always fond of Commander Keen, and I think BioMenace used one of the same engines. (I do have a screenshot of that game's menu screen running under DOSBox-X atop FreeDOS also showing the DOSBox-X menu.) I don't know, boring cmdline stuff isn't quite photogenic! But I'd rather it wasn't all just games either (although Paku Paku is pretty iconic, 160x100 CGA text mode, right?). Maybe a Links2 (graphical) screenshot of the FreeDOS website? > Also: Any important FreeDOS-related or DOS-related or "classic > PC"-related dates that you think should be marked on the calendar? June 29 for the start of FreeDOS? Or maybe Sep. 3 for the big FreeDOS 1.0 release? In terms of DOS history, I mainly think in years. E.g. Free Pascal 3.0.0 (now with cross compiler support for i8086-msdos) was released in 2015. So was DJGPP 2.05. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
