Re: [Freedos-user] DOSHEXED - memory bug
Hallo Herr Mateusz Viste, am Samstag, 19. Februar 2022 um 15:08 schrieben Sie: > On 12/01/2022 18:22, tom ehlert wrote: >>> You might want to try uHex. Requires some 20 KiB of RAM and handles >>> files up to 2 GiB. >> >> use int 21, 6C EXTENDED OPEN/CREATE and you can handle 4GiB. > This does not appear to be present in the FreeDOS kernel. Or at least > the source code comment says "not implemented yet" (and the O_LARGEFILE > flag does not appear to be used anywhere later in the code): > https://github.com/FDOS/kernel/blob/master/kernel/dosfns.c#L498 OOPS. I hadn't thougt about this as the FreeDOS kernel (AFAIK) doesn't check for offsets beyond 2GB. > Do you have a FreeDOS kernel version that supports this? most likely no ;) Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOSHEXED - memory bug
On 12/01/2022 18:22, tom ehlert wrote: You might want to try uHex. Requires some 20 KiB of RAM and handles files up to 2 GiB. use int 21, 6C EXTENDED OPEN/CREATE and you can handle 4GiB. This does not appear to be present in the FreeDOS kernel. Or at least the source code comment says "not implemented yet" (and the O_LARGEFILE flag does not appear to be used anywhere later in the code): https://github.com/FDOS/kernel/blob/master/kernel/dosfns.c#L498 Do you have a FreeDOS kernel version that supports this? Mateusz ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOSHEXED - memory bug
Hi Michał, > I'm trying to edit different files with DOSHEXED from FreeDOS 1.3RC5 CD > and it's just disappointing. This editor will complain it's out of > memory if we're trying to open a file that won't entirely fit into the I had a look at the DOSHEXED source code, because it doesn't have any user documentation. It reads "Added dosmem free check, wont load if document is greater than ramavail." So, it's definitely a limitation of DOSHEXED. Do we really need DOSHEXED in a FreeDOS distro, when we already have UHEX? UHEX is open source (2-clause BSD) and works even on a 808x processor. > leftover conventional memory (<1MiB). I tried editing LOTUS.DAT (approx > 1.4MB, from Lotus 3: The Ultimate Challenge) and Stargunner's SETUP.EXE. > Luckily the second one fits, given you don't load too many drivers in > DOS. Is there any other hex editor for FreeDOS, which works a lot better? Closed source, but my preferred hex editor in DOS or Win32: http://mklasson.com/hexit.php Cheers, Robert -- +++ BTTR Software +++ Home page: https://www.bttr-software.de/ DOS ain't dead: https://www.bttr-software.de/forum/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOSHEXED - memory bug
Hi, On Wed, Jan 12, 2022 at 7:59 AM Michał Dec wrote: > > Is there any other hex editor for FreeDOS, which works a lot better? Try this: * https://www.sac.sk/download/utilprog/hiew650.zip This is the well-known "freeware" Hacker's View (HIEW) hex editor. IIRC, its built-in disassembler can handle up through Pentium III. There are others like BIEW/BEYE and QVIEW, both with sources, that try to mimic the same interface and features. * https://sourceforge.net/projects/beye/files/biew/6.1.0/ * https://sourceforge.net/p/beye/bugs/38/ * https://www.sac.sk/download/utilprog/biew562.arj * https://www.sac.sk/download/utilprog/qv291src.zip I still use HIEW a lot, it's pretty rock solid. I have used the others occasionally, but I can't say they're quite bug-free. Your mileage may vary. (If you want automated hex editing for batch files, I have other tools in MetaDOS. I also added recompiling BIEW as one of my tests.) Just FYI. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOSHEXED - memory bug
On 12/01/2022 18:22, tom ehlert wrote: You might want to try uHex. Requires some 20 KiB of RAM and handles files up to 2 GiB. use int 21, 6C EXTENDED OPEN/CREATE and you can handle 4GiB. Sure, but that's not very portable code. And it is not enough anyway. To handle 4 GB one would also need to: - replace all 'long' position tracking variables by unsigned long - handle errors in a different way (than passing -1) - use a non-portable construct to replace fseek() - and probably more that I don't think about right away Mateusz ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOSHEXED - memory bug
> On 12/01/2022 14:58, Michał Dec wrote: >> Is there any other hex editor for FreeDOS > You might want to try uHex. Requires some 20 KiB of RAM and handles > files up to 2 GiB. use int 21, 6C EXTENDED OPEN/CREATE and you can handle 4GiB. > IIRC it is shipped with FreeDOS, but if not then you will find it here: > http://uhex.sourceforge.net/ > Mateusz Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOSHEXED - memory bug
On 12/01/2022 14:58, Michał Dec wrote: Is there any other hex editor for FreeDOS You might want to try uHex. Requires some 20 KiB of RAM and handles files up to 2 GiB. IIRC it is shipped with FreeDOS, but if not then you will find it here: http://uhex.sourceforge.net/ Mateusz ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOSHEXED - memory bug
Hi, > On Jan 12, 2022, at 8:58 AM, Michał Dec wrote: > > Hi everyone, > > I'm trying to edit different files with DOSHEXED from FreeDOS 1.3RC5 CD and > it's just disappointing. This editor will complain it's out of memory if > we're trying to open a file that won't entirely fit into the leftover > conventional memory (<1MiB). I tried editing LOTUS.DAT (approx 1.4MB, from > Lotus 3: The Ultimate Challenge) and Stargunner's SETUP.EXE. Luckily the > second one fits, given you don't load too many drivers in DOS. Is there any > other hex editor for FreeDOS, which works a lot better? > > Best regards, > > Michał Don’t know about feature comparison. But, UHEX works well enough for most of the stuff I need from a hex editor. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] DOSHEXED - memory bug
Hi everyone, I'm trying to edit different files with DOSHEXED from FreeDOS 1.3RC5 CD and it's just disappointing. This editor will complain it's out of memory if we're trying to open a file that won't entirely fit into the leftover conventional memory (<1MiB). I tried editing LOTUS.DAT (approx 1.4MB, from Lotus 3: The Ultimate Challenge) and Stargunner's SETUP.EXE. Luckily the second one fits, given you don't load too many drivers in DOS. Is there any other hex editor for FreeDOS, which works a lot better? Best regards, Michał ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
