Activity for Robert Riebisch
-
Robert Riebisch posted a comment on a blog post
Not sure you still need an answer... https://sourceforge.net/projects/srdisk/files/srdisk/2.09c/srdsk209c.zip/download -> whatsnew.doc reads: 2.09c 2005-07-21 Recompiled binaries to get rid of XMS debug output. 2.09b 2005-06-22 Recompiled binaries for smaller size. 2.09 2005-06-05 Release under GNU GPL license. Source code at http://sf.net/projects/srdisk Fix EMS error handling to show the EMS error code. Add instructions for Windows 95 users. 2.08 1996-07-15 So I took https://sourceforge.net/projects/srdisk/files/srdisk/2.09/srsrc209.zip...
-
As reported here, SpamPal at least works on "WINDOWS 7 ( 64 bit)". It also works on Windows XP x86.
-
It's 04-2024 and I installed SpamPal 1.595 (spampal-1.595.zip) today in my old Windows XP virtual machine, where I still use Thunderbird 2.x (!) for receiving mails via POP3. After updating the list of DNSBL providers SpamPal works fine for me.
-
It's a bug, when EDIT.EXE from FreeDOS should behave the same as EDIT.EXE from MS-DOS. Exactly.
-
Every modern editor, including the old MS-DOS EDIT.EXE can move into the third line because they use some sort of virtual third line, even if there is no real third line. And's that my bug report is about, besides the other issue. You're right. It is a compatibility bug, because it differs from the behavior of MS-DOS EDIT. "I can add new characters or CR here in FreeDOS Edit 0.9a from FreeDOS 1.3." No, you can't. You will overwrite the 2 or you will put a char between the 2 and the the 't'. You're...
-
You can't mark the last line with the cursor as described above and this is a bug. Yes, you can't mark it that way, but it never was the intention of FED to support such behavior. -> Not a bug.
-
The cursor does not move to the third line, because there is no third line in your test text file. "You can't add a new character after the 2 without overwriting the 2." -> I can add new characters or CR here in FreeDOS Edit 0.9a from FreeDOS 1.3.
-
FED just behaves different from what you expect. So it's by design, but no bug. You issue is a feature request then.
-
https://gitlab.com/FreeDOS/base/edit-freedos/-/issues/7
-
FreeDOS 1.3 writes COUNTRY=049,858,C:\FreeDOS\BIN\COUNTRY.SYS to FDCONFIG.SYS, which is not that bad as before. :-)
-
https://gitlab.com/FreeDOS/base/edit-freedos/-/issues/6
-
Copying some followup sent via email, so we can track it in the bug report: I wrote: "I think maybe the best option is to remove the clock feature from the editor. I don't know that the clock adds much to the editor, anyway." Robert wrote: If a user doesn't care about heat generation or power consumption, it's okay to leave in. If you decide to remove the clock, a workaround for users relying on that feature would be to use "File" -> "DOS Shell" -> date and/or time commands. Maybe this could be added...
-
Better late, than never: Unpacking works fine with innounp 0.50.
-
Your text doesn't promise the opposite, but edlin-2.20.zip doesn't contain a binary. So, the download is not very useful for normal users.
-
this was a test ticket to verify that anonymous users can now enter new bugs (and now they can) .. marking as closed EDIT: Just a test by 'bttr'.
-
Could not delete Directory: TESTDI This is probably a result of the line: file[strlen(file)-1]=0; // remove final '\\' It came to my mind, that you are just using the wrong syntax. So I tried XDEL TESTDIR\ /d /y: Invalid name in "testdir\" Next try: XDEL TESTDIR\*.* /d /y --> no output, but TESTDIR still present. HISTORY.TXT says: It has one major difference: XDEL /SRDN DIR\*.* will delete all files and subdirectories just as DELTREE /Y DIR\*.* but the directory DIR\ will NOT be removed (This is...
-
Maybe http://josh.com/tiny/ is, what you are looking for.
-
Could not delete Directory: TESTDI This is probably a result of the line: file[strlen(file)-1]=0; // remove final '\\' It came to my mind, that you are just using the wrong syntax. So I tried XDEL TESTDIR\ /d /y: Invalid name in "testdir\" Next try: XDEL TESTDIR\*.* /d /y --> no output, but TESTDIR still present. HISTORY.TXT says: It has one major difference: XDEL /SRDN DIR\*.* will delete all files and subdirectories just as DELTREE /Y DIR\*.* but the directory DIR\ will NOT be removed (This is...
-
Could not delete Directory: TESTDI This is probably a result of the line: file[strlen(file)-1]=0; // remove final '\\' It came to my mind, that you are just using the wrong syntax. So I tried XDEL TESTDIR\ /d /y: Invalid name in "testdir\" Next try: XDEL TESTDIR\*.* /d /y --> no output, but TESTDIR still present. HISTORY.TXT says: It has one major difference: XDEL /SRDN DIR\*.* will delete all files and subdirectories just as DELTREE /Y DIR\*.* but the directory DIR\ will NOT be removed (This is...
-
Regarding the benefit: XDEL was introduced by DR-DOS and a long time later M$ introduced deltree. This implementation of XDEL is intended to be 100% compatible with DR-DOS version. If you find anything different, consider it a bug and send me a notofication, please. XDEL can be used in place of deltree, but in fact it has more options, including: - default is not to delete Read/Only files, - option to include _or_not_ subdirectories - option to wipe all files before deleting. - options to ask or...
-
This was by design. If a problem exists on the installed system, the user can boot in safe mode and disable FDAPM. Regarding APMDOS the FDAPM docs say: between the hookhandler call and the going TSR code, insert configuration through POWER API on int 2f. Should also configure savingstrat (whether to use HLT, whether to use APM CPU IDLE)... This should give you maximum energy savings. It is the only mode that causes FDAPM to stay resident in RAM. MS POWER syntax compatibility aliases: "ADV" and "ADV:MIN",...
-
Stop resetting file dates in packages
-
This was by design. If a problem exists on the installed system, the user can boot in safe mode and disable FDAPM. Regarding APMDOS the FDAPM docs say: between the hookhandler call and the going TSR code, insert configuration through POWER API on int 2f. Should also configure savingstrat (whether to use HLT, whether to use APM CPU IDLE)... This should give you maximum energy savings. It is the only mode that causes FDAPM to stay resident in RAM. MS POWER syntax compatibility aliases: "ADV" and "ADV:MIN",...
-
This was by design. If a problem exists on the installed system, the user can boot in safe mode and disable FDAPM. Regarding APMDOS the FDAPM docs say: between the hookhandler call and the going TSR code, insert configuration through POWER API on int 2f. Should also configure savingstrat (whether to use HLT, whether to use APM CPU IDLE)... This should give you maximum energy savings. It is the only mode that causes FDAPM to stay resident in RAM. MS POWER syntax compatibility aliases: "ADV" and "ADV:MIN",...
-
This was by design. If a problem exists on the installed system, the user can boot in safe mode and disable FDAPM. Regarding APMDOS the FDAPM docs say: between the hookhandler call and the going TSR code, insert configuration through POWER API on int 2f. Should also configure savingstrat (whether to use HLT, whether to use APM CPU IDLE)... This should give you maximum energy savings. It is the only mode that causes FDAPM to stay resident in RAM. MS POWER syntax compatibility aliases: "ADV" and "ADV:MIN",...
-
This issue is still present after 13 years. And yes, I consider at least Ctrl+G a bug, because it differs from the behavior of MS-DOS (6.22). Didn't test the others.
-
You could add a "Safe Live env. mode", where FDAPM (and maybe others) is/are not loaded.
-
This is a similar issue: [#309] fdshell: Browse GNU GPL: File not found (Help)
-
This is a similar issue: [#294] Doszip Commander help sub-entries not opening
-
This is a similar issues: [#294] Doszip Commander help sub-entries not opening
-
This is a similar issues: #294 Doszip Commander help sub-entries not opening
-
No need to re-open, as Andrew didn't reply for more than a year. I think, the bug is either in RMENU or VirtualBox.
-
I can confirm this for US English in MS Virtual PC. Message/Dialog says: "Unable to install the 'base/htmlhelp' package." But it doesn't give further details on the error. I was unable to use advanced mode. After 10 minutes to let the list of packages appear, I pulled the plug.
-
I can confirm this for US English in MS Virtual PC. Message/Dialog says: "Unable to install the 'base/htmlhelp' package." But it doesn't give further details on the error. I was unable to use advanced mode. After 10 minutes to let the list of packages appear, I shut down.
-
I understand that. See my reply to Jim.
-
Looks like I need to be more specific next time. I wrote that "FYI post" just for the record. To make Shidel's explanation more complete. But now, that it is already open again: Please add "(>64 MB RAM recommended)" right after the "Use FreeDOS 1.3 in Live Environment mode" like I already suggested on 2020-01-16. :-) Then this (not a)bug report can be closed.
-
I can confirm this for US English in MS Virtual PC. Message/Dialog says: "Unable to install the 'base/htmlhelp' package." But it doesn't give further details on the error. I was unable to use advanced mode. After 10 minutes to let the list of packages appear, I quit.
-
Load keyboard layout in live environment
-
I lost contact to the author of RMENU Jürgen Hoffmann, not the bug reporter Andrew Pennebaker.
-
FYI: With 32 MB RAM for RC4 I get (in Bochs): ... Bring util\rawrite package online. OK Bring util\wcd package online. OK Low on free space. Unable to load all FreeDOS packages -- (probably) Add more RAM! ...
-
It is NOT implemented. To reproduce: Boot from RC4 ISO, select "Use FreeDOS 1.3 in Live Environment mode", wait for the command prompt to come up, look at the output of "mem/c". There is no FDAPM present.
-
It is NOT implemented. To reproduce: Boot from RC4 ISO, select "Use FreeDOS 1.3 in Live Environment mode", wait for the command prompt to come up, look at the output of "mem/c".
-
Do you have any projects in mind? No. I just like playing with small, but useful, software. Cheers, Robert
-
Hi Stephen! At least under FreeDOS 1.3 RC3 or Windows XP ASM.COM is not locked by DOS during execution. So renaming is not required. ASM.COM "accepts" as many parameters as you want, but it treats the complete parameter string as the source file name. See lines 3859-3867. Cheers, Robert
-
Hi Matthias! I used the same command here and had no problems. I'm on Windows XP x86. What's your environment? For the simple Hello Word example see below. Cheers, Robert ; print message mov ah, 9 mov dx, msg int 21h ; return to DOS ret ; message msg: ; ASM.COM does not support this syntax ; db 'hello, world', 13, 10, '$' ; workaround #1 db 'hello, world', 13, 10, 36 ; workaround #2 ; db 'hello, world', 13, 10 ; db '$'
-
Hi Dalibor! Thanks for your detailed feedback! Can you please repeat the DN test with MS-DOS 6.22, PC-DOS, or OpenDOS? I guess, these behave exactly the same, so it's probably a bug in hardware emulation by QEMU. See (ordered from new to old) the following QEMU reports: 1. keyboard errors in DOS, found links to similar errors for reference 2. Strange keyboard behaviour in Vim editor 4. Arrow keys press is double in some programs in Dos 5. Dos Keypad is not working for numbers - numlock is not working...
-
Hi Jan-Peter! Did you already test Tom's new mkeyb044.zip? Cheers, Robert
-
Here is another converter to RTF. This time written in Perl: https://hc-ddr.hucki.net/wiki/doku.php/cpm/wordstar (Untested by me.)
-
Hi Piotr! 1. https://github.com/kbarni/wsconvert has a converter to Markdown written in Python. (Untested by me.) 2. http://www.georg-basse.de/retro/wsrtf-konverter/ is written in C, converts the document to RTF and worked fine for me with a WordStar 4.0 sample file. Sorry, but I can't answer your question about those extra-long documents. Cheers, Robert
-
Hi Piotr! 1. https://github.com/kbarni/wsconvert has a converter to Markdown written in Python. (Untested by me.) 2. http://www.georg-basse.de/retro/wsrtf-konverter/ is written in C, converts the document to RTF and worked fine for me with a WordStar4 sample file. Sorry, but I can't answer your question about those extra-long documents. Cheers, Robert
-
Hi Piotr! 1. https://github.com/kbarni/wsconvert has a converter written in Python. (Untested by me.) 2. http://www.georg-basse.de/retro/wsrtf-konverter/ is written in C and worked for me with a WordStar4 sample file. Sorry, but I can't answer your question about those extra-long documents. Cheers, Robert
-
Some more WordStar links in case we need these later: https://texteditors.org/cgi-bin/wiki.pl?WordStar http://fileformats.archiveteam.org/wiki/Wordstar https://github.com/kbarni/wsconvert http://www.gmayor.com/downloads.htm -- WordStar (for DOS) converter for Word
-
Hi Piotr, for the future: Please don't link to sites with questionable legal content. Regarding your questions: 1. Pico: Having Windows XP here, I can say, you can just download http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/latest/edit/pico.zip, extract it and run BIN\PICO.EXE. Should be similar on Windows 98. 2. WordStar: You write "I have converter". Does this converter not work? You can also try http://www.georg-basse.de/retro/wsrtf-konverter/. (Untested by me.) Cheers,...
-
Outdate DOSLFN in FreeDOS 1.3 RC3
-
Okay, thanks. Maybe you or Paul could test, if that behavior changes by performing a clean boot (= skip processing FDAUTO.BAT and FDCONFIG.SYS). I don't think so, but let's check it.
-
Hi Vladimir! Does this behavior also occur with FreeDOS 1.3 RC3? Exact error message would be really nice. Cheers, Robert
-
Hi Werner! Sorry to hijack your report. As you write you are using QEMU 5.1.0, would you be so kind to test for this bug: DN2 (disk navigator): arrows double effect, numpad arrows are fine? Thanks in advance! Cheers, Robert
-
Hi Paul again! Is Doszip Commander also affected? Can you reproduce this behavior with MS-DOS 6.22 or OpenDOS 7.01? Cheers, Robert
-
Doszip Commander help sub-entries not opening
-
Hey Paul! I can confirm this for a base install + clamav. Complete error message is: LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar supp ort unavailable LibClamAV Error: cl_load(): Can't get status of /dev/env/DOSDIR/lib ERROR: Can't get file status Unfortunately, I have no idea how to fix it, because I don't use clamav at all. Cheers, Robert
-
Hey Paul! I can confirm this. This bug can be fixed by adding quotes to file C:\FDOS\NLS\WELCOME.FR. Change line Bienvenue au système d'exploitation to Bienvenue au système "d'exploitation". Cheers, Robert
-
Hi Paul! This seems to be a QEMU bug also reported at: Qemu On Windows - DOS machine - Keyboard arrows problem (double press detected in some Filemanagers). Maybe upgrading to QEMU 5.1.0 helps. Cheers, Robert
-
Hi Paul! Thanks for reporting, but you're wrong here. "fdisk 1" is as invalid as "fdisk c:" or "fdisk c". MS-DOS FDISK, if you mean that with "other DOS", supports only "/STATUS" and (undocumented) "/MBR". Please lookup FreeDOS HELP for correct FDISK syntax. Cheers, Robert
-
Alt+P hotkey is still present in FreeDOS 1.3rc2 EDIT 0.9a. I think, because of i18n, we should avoid Alt+letter hotkey combinations at all. There's also Alt+X to exit EDIT. What alternatives? Ctrl+P is already in use. MS-DOS EDIT is no inspiration here, as it doesn't support "paragraph reforming" and doesn't have a hotkey for exiting. How about the Windows-like Alt+F4 for exiting and Ctrl+R for reform(att)ing?
-
Hi Raul! I cannot confirm this bug, but for me BMPVIEW hangs in FreeDOS 1.2 and MS-DOS 6.22. So it's probably not a very mature tool. Unfortunately BMPVIEW doesn't come with a README file or source code and BMPVIEW.EXE has no indication of its author. One can only see it has been compiled with Microsoft C 6.0. (This compiler is from 1990.) Maybe it's better to look for another tool: https://www.bttr-software.de/freesoft/graphics.htm#viewers Cheers, Robert
-
Maybe you want to have a look at a similar issue at https://github.com/sqlitebrowser/sqlitebrowser/issues/893 Cheers, Robert
-
Hi Dave! you may wish to test the new FreeDOS 1.3 RC (= Release Candidate) 2. It provides a live environment, if you have >=64 MB RAM in your machine. Cheers, Robert
-
Why can I not edit my own tickets? UPDATE: Editing works now. Thanks, Jim.
-
For the settings either look for the Country setting in HELP or at http://wiki.freedos.org/wiki/index.php/Country_codes Cheers, Robert
-
@jhall1 Please close the ticket in the next days. Thanks.
-
Hi Dan! Thanks, but I don't have a personal need for this software. And with you saying "so the bug is in the VirtualBox software, not FreeDos.", I think we can close this bug report. Cheers, Robert
-
Um, I see, I'm the only one who cares. ;-) I changed my FDCONFIG.SYS to !COUNTRY=049,,C:\FDOS\BIN\COUNTRY.SYS and it worked fine. So what do you mean by "like German still don't have any of that data."? Cheers, Robert
-
Ah, sorry. I stopped reading your answer after "This is not a bug. It is a feature..." I missed the word "request". Sorry again. Cheers, Robert
-
Okay. As for the message: Please don't hide from the user sitting in front of the computer, what sufficient RAM would be! Pleased add >64 MB recommended. or something like that. Maybe also to the "Welcome to FreeDOS 13-RC2 (LiveCD)" screen. Cheers, Robert
-
High CPU usage in FreeDOS EDIT 0.9a
-
Please tell me more.
-
I understand. But maybe show a hint to a user, that he could try to load it. Otherwise CPU is running really hot for no reason. Cheers, Robert
-
Sorry, I don't understand. It was a feature request not to display such a hint? The SHUTDOWN command works fine without FDAPM being loaded in RAM. I just verified in Live mode. Cheers, Robert
-
With 64 MB it worked fine for me. Thanks. Please add a RAM size check before starting Live mode. Or at least a warning, that it doesn't work with <64 MB. Cheers, Robert
-
Hi Dan, I don't use Oracle VM VirtualBox Manager at all, so I have no use for the files. Cheers, Robert
-
Hi Joe, nice to hear, it works for you now. Took only 10 years. ;-) Cheers, Robert
-
@jhall1 and @tomehlert Hi Jim & Tom, I think we should change default tab size to 8, because that's what compatibility with MS-DOS means for me. I know, discussion the perfect tab size or using tabs at all, is like the talking about vi vs. emacs or Linux vs. Windows, but I don't intend to start a flame war. Cheers, Robert
-
Hi Jose! MORE's default tab size is 4 spaces: Using more /t8 picdisl.txt worked for me. Cheers, Robert
-
Hi Dan, where can we get MicroCADAM? Cheers, Robert
-
Live environment mode not loading FDAPM
-
Live environment mode fails to load net\mtcp package
-
Why can I not edit my own tickets?
-
Irritating installer
-
COUNTRY setting after installation
-
Include HALT/SHUTDOWN in boot greeting
-
Andrew is talking about https://www.bttr-software.de/products/jhoffmann/#rmenu In August I got two mails from him in private, but I was unable to help. And I lost contact to Jürgen Hoffmann. :-(
-
I played a little: This bug is related to using the /O option. /O in FreeDOS 1.2 installations is active by default, because of SET DIRCMD=/P /OGN /Y in autoexec.bat. You can reproduce the behaviour by unsetting it: SET DIRCMD= Then run dir/w fdos and compare to dir/w/o fdos. The bug is still present in http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/command/0.84/com084b7-xmsswap.zip But maybe Bart can have a look? Wild guess: It doesn't take the outc('n') branch, because rv is other...
-
I played a little: This bug is related to using the /O option. /O in FreeDOS 1.2 installations is active by default, because of SET DIRCMD=/P /OGN /Y in autoexec.bat. You can reproduce the behaviour by unsetting it: SET DIRCMD= Then run dir/w fdos and compare to dir/w/o fdos. The bug is still present in http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/command/0.84/com084b7-xmsswap.zip But maybe Bart can have a look? Wild guess: It doesn't take the outc('n') branch, because rv is other...
-
I played a little: This bug is related to using the /O option. /O in FreeDOS 1.2 installations is active by default, because of SET DIRCMD=/P /OGN /Y in autoexec.bat. You can reproduce the behaviour by unsetting it: SET DIRCMD= Then run "dir/w fdos" and compare to "dir/w/o fdos". The bug is still present in http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/command/0.84/com084b7-xmsswap.zip But maybe Bart can have a look? Wild guess: It doesn't take the outc('n') branch, because rv is other...
-
Mail archives links broken
-
Unable to start version 2.6.11 on Windows XP SP3 x86
-
Hi, I'm unable to unpack Jill of the Jungle: The Complete Trilogy. innounp 0.47 writes: Signature detected: Inno Setup Setup Data (5.6.2) (u) This is not directly supported, but i'll try to unpack it as version 5507 ; Version detected: 5602 (Unicode) Unpacking failed. This version is not supported. I think, it's time to make innounp 0.48. Cheers, Robert
1