Re: [Freedos-user] CPI editor 1.2b
Hi Balthasar This looks really nice. I remember that once I was desperately looking for a CPI editor that would be GPL, and couldn't find any - yours would be really useful back then. IIRC I finally ended up using the Display Font Editor from Rimrock Software (1991, great tool, but commercial license only). Anyway, I have a few suggestions/ideas/bug reports below, maybe you will find these interesting ;) 1. I haven't managed to compile it from source (but haven't tried very hard either, and I have very limited knowledge about how to use Turbo C++). I did produced an executable, but the linker was complaining a lot about undefined symbols, so I probably missed how to link the egavga lib. A section in the readme about 'how to build from source' would be appreciated (maybe a makefile also? this would greatly simplify the build process). I assume the *.prj file contains some indications, but looking at it with a hex editor I see there are some hardcoded paths there, so it's probably useful only on your system. 2. When I pressed F4, and tried to get out (escape, empty string..) I broke the UI and had to abort via CTRL+C. Some input checking there could be nice. 3. I had some troubles to get started using it - mostly because I didn't knew what I should do (home/end, pgup/pgdown, etc...). An in-program help section could be of great help. Eg. under F1 - something that would display a short list of keys to use. 4. The 'official' name of the program is unclear. Is it 'cpied', 'CPI Editor', or 'Edytor Napisów' ? All these names appear at one point or another. 5. The version string is inconsistent - in the documentation and source code it says '1.2b', while in the program itself it states '1.2'. 6. When I want to load a file (F3), then press enter a few times, the input dialog stays displayed, but any new text appear much lower in the screen. Seems that you ignore enter if it's presses on an empty string, while I feel it should immediately provide some error message. 7. It's not clear how many codepages are stored in a file. To know this, one have to count them manually with home/end. It would be great if the total of avaiable code pages would be printed on screen (eg. in the title bar, next to the file name). Even better - having some kind of a menu that lists available codepages, and allows to choose the one we want. Such menu could be then used also to remove codepages or add new codepages, and it would be called like 'codepages management' or something like that. 8. You seem to always display 3 fixed sizes of fonts. I don't know anything about the CPI format, but is it possible that a CPI file could contain more font sizes? Or font sizes different from what you assume (8x8, 8x14, 8x16) ? 9. There is no CPX support, but nevertheless, it would be cool to be able to detect the CPX format, and provide some hints about what to do. Right now cpied just says 'Unsupported format, id0=0x81'. Would be great if it would say something like this is CPX, not supported format, but if you need to edit it simply uncompress it first using UPX -d font.cpx -o font.cpi cheers, Mateusz On 07/14/2013 11:51 PM, Rowery na Księżycu wrote: I made a CPI editor. Maybe it could be useful. It allows to edit the shape of the characters, remove or create fonts, remove or create codepages,.. It has a gui and can be controlled with the keyboard or mouse (if there is a mouse installed). It doesn't support *.cpx files yet download: http://baltixy.w.interia.pl/in05.zip http://baltixy.w.interia.pl/in05.htm -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Desqview
I have a retail box copy of DESQview version 2.42 with all the accompanying manuals. In the error messages appendix says the following about this error: The DESQview command you performed tried to read the indicated DESQview file, but couldn't. If you decide the indicated file is bad, delete it and then reinstall DESQview. There is no harm in reinstalling DESQview over the same version of an existing system. In addition, it says: Sometimes, loading memory-resident programs prior to starting up DESQview, or allocating too few DOS file handles (by the FILES command in your CONFIG.SYS file), can cause this error. Also, if DESQview cannot find the .DVO (Open Window Menu) file this message will appear as a Startup Message. On an installation of this program that I have on an old computer, the DESQVIEW.DVO file is 249 bytes. You are correct that QEMM is not required (at least for the version I have) because I am running DESQview 386 using MS HIMEM.SYS and EMM386.EXE without problems. This is because some IBM drivers I have for this old computer would not work with QEMM. I don't know if this is of any help, but it's all I know about the problem. Good luck. On 7/12/13, Jerome Ibanes jiba...@gmail.com wrote: I'm having an issue running Deskview 2.8 on FreeDos, which I would describe as such: - Desqview 2.8 can be freely downloaded at http://www.chsoft.com/dv.html - I am not running QEMM (not required with Desqview). - I do want to run Desqview, accept no substitute. - I am not running Dosbox. The installation process runs fine, but upon starting Desqview, I run across this error: Missing (or bad) DESQview file: DESQVIEW.DVO. Subsequently, the application is then unable to run dos applications. Would anyone know how to address this issue? The file DESQVIEW.DVO is indeed present in C:\DV (where I installed Desqview). Thank you, J. -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Desqview
I have a license and have used this. I see it as a wonder you've gotten this far. Cheers, John S Wolter LinkedIn: johnswolter http://www.linkedin.com/in/johnswolter johnswol...@wolterworks.com USA, Eastern Standard Time, -5 GMT, -4 GMT DST On Mon, Jul 15, 2013 at 10:55 AM, mcelha...@usnetizen.com wrote: I have a retail box copy of DESQview version 2.42 with all the accompanying manuals. In the error messages appendix says the following about this error: The DESQview command you performed tried to read the indicated DESQview file, but couldn't. If you decide the indicated file is bad, delete it and then reinstall DESQview. There is no harm in reinstalling DESQview over the same version of an existing system. In addition, it says: Sometimes, loading memory-resident programs prior to starting up DESQview, or allocating too few DOS file handles (by the FILES command in your CONFIG.SYS file), can cause this error. Also, if DESQview cannot find the .DVO (Open Window Menu) file this message will appear as a Startup Message. On an installation of this program that I have on an old computer, the DESQVIEW.DVO file is 249 bytes. You are correct that QEMM is not required (at least for the version I have) because I am running DESQview 386 using MS HIMEM.SYS and EMM386.EXE without problems. This is because some IBM drivers I have for this old computer would not work with QEMM. I don't know if this is of any help, but it's all I know about the problem. Good luck. -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Desqview
On 2013-07-12 06:38 (GMT-0700) Jerome Ibanes composed: I'm having an issue running Deskview 2.8 on FreeDos, which I would describe as such: - Desqview 2.8 can be freely downloaded at http://www.chsoft.com/dv.html - I am not running QEMM (not required with Desqview). - I do want to run Desqview, accept no substitute. - I am not running Dosbox. The installation process runs fine, but upon starting Desqview, I run across this error: Missing (or bad) DESQview file: DESQVIEW.DVO. Subsequently, the application is then unable to run dos applications. Would anyone know how to address this issue? The file DESQVIEW.DVO is indeed present in C:\DV (where I installed Desqview). The following is from CONFIG.SYS used on my last PC that would run QEMM and DV: [MAX] SWITCHES =/F/W DEVICE=C:\Q\QEMM386.SYS RAM ROM BE:N XSTI=1A X=F000-F8FF X=FE00-FEFF SHELL=C:\Q\LOADHI.COM C:\DOS\COMMAND.COM C:\DOS\ /p /f /k C:\AE.BAT set AUTOBAT=AE.BAT set CONFIG=MAX DOS = HIGH BUFFERS = 8 FILES = 60 FCBS= 1,0 LASTDRIVE = Z DEVICE=C:\Q\LOADHI.SYS C:\DOS\RAMDRIVE.SYS 6144 128 512 /E set BUFFERS=SMALL set RAMDISK=6144 set DOSHIGH=YES BREAK=ON STACKS=0,0 Maybe it holds a clue to a solution? I haven't used DV since 1997 when I found I needed full GUI internet access and made OS/2, the better DOS than DOS of that age and still, my primary OS. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] CPI editor 1.2b
Hi, On Mon, Jul 15, 2013 at 2:50 AM, Mateusz Viste mate...@viste-family.net wrote: 1. I haven't managed to compile it from source. I did produced an executable, but the linker was complaining a lot about undefined symbols, so I probably missed how to link the egavga lib. A section in the readme about 'how to build from source' would be appreciated (maybe a makefile also?). Can anyone with knowledge clarify that EGAVGA.OBJ is okay to redistribute? Honestly, without sources (and four freedoms) to that too, declaring the project as GPL is probably not even true. This is important if wishing to redistribute it. I've not really used EGAVGA stuff from Borland before, so I don't know how hard it would be to implement similar functionality with OpenWatcom (hopefully not very). Well, for obvious licensing reasons, OpenWatcom is preferred here, but I really don't wish to discourage anyone (or add any extra burdens). Nevertheless, without proper distribution rights, we can't use it at all. And even then, FreeDOS (tm) and Jim Hall heavily prefer free/libre (four freedoms) whenever possible. 5. The version string is inconsistent - in the documentation and source code it says '1.2b', while in the program itself it states '1.2'. Dunno, the filename is mysteriously named in05.zip! 8. You seem to always display 3 fixed sizes of fonts. I don't know anything about the CPI format, but is it possible that a CPI file could contain more font sizes? Or font sizes different from what you assume (8x8, 8x14, 8x16) ? I think here he's only trying to support the normal, most common modes: 80x25, 80x43, 80x50. 9. There is no CPX support, but nevertheless, it would be cool to be able to detect the CPX format, and provide some hints about what to do. Right now cpied just says 'Unsupported format, id0=0x81'. Would be great if it would say something like this is CPX, not supported format, but if you need to edit it simply uncompress it first using UPX -d font.cpx -o font.cpi Right, see MODE's sources for that bit. http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/mode/2005/mode-2005may12.zip BTW, the doc says this: On Windows Vista and 7, the system may refuse to launch this program (or any other fullscreen DOS program) or not. It depends on the video card driver. The simple truth is that Windows is very incompatible (on purpose) with DOS stuff. They don't care anymore, so honestly it is (IMO, though hardly a stretch) a lost cause for us. It always complains on any attempt to do anything even remotedly related to video modes, so you have to ignore as many messagebox complaints as possible. You're only safe if the program is pure text mode only and doesn't try to do any mode switches. (Depends on video driver ... you can allegedly swap in an older video card driver, e.g. from XP, but that disables Aero, which some other programs need to function properly.) -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] CPI editor 1.2b
Hi again, Just a few more minor comments. On Sun, Jul 14, 2013 at 4:51 PM, Rowery na Księżycu rowerynaksiez...@gmail.com wrote: I made a CPI editor. Maybe it could be useful. It allows to edit the shape of the characters, remove or create fonts, remove or create codepages,.. It has a gui and can be controlled with the keyboard or mouse (if there is a mouse installed). It doesn't support *.cpx files yet download: http://baltixy.w.interia.pl/in05.zip http://baltixy.w.interia.pl/in05.htm I don't know what tools others used previously (e.g. Henrique, the resident expert). In my recent dabblings in fonts, I didn't mess with .CPI files, only the raw bitmap font itself (in my case, 8x16 only, aka CO80 80x25, aka 4096 bytes). One particular tool that comes to mind re: CPI is BACHL's CPIFNT (cpf01.zip, vaguely related to PG): http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/file/pg/libs/ The raw font format isn't very complicated, but a nice user editor indeed makes things easier than editing raw bits (but see my translation of Terminus into .ASM source, it's far from impossible to manually edit). http://ftp.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/system/fonts/terminus.zip I used Fonte (aka, 2L8) to create my own font, which is old freeware (but no sources). http://ftp.sunet.se/pub/simtelnet/msdos/vga/2l8fe122.zip You could also use and adapt FFE from Freemacs MULE (as by default it only edits upper 128 extended chars; Turbo Pascal). http://ftp.ibiblio.org/pub/micro/pc-stuff/freedos/files/edit/emacs/mule/ (So, just for completeness, that's all I know.) -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] CPI editor 1.2b
On Mon, Jul 15, 2013 at 3:49 PM, Rugxulo rugx...@gmail.com wrote: The simple truth is that Windows is very incompatible (on purpose) with DOS stuff. They don't care anymore, so honestly it is (IMO, though hardly a stretch) a lost cause for us. It always complains on any attempt to do anything even remotedly related to video modes, so you have to ignore as many messagebox complaints as possible. You're only safe if the program is pure text mode only and doesn't try to do any mode switches. (Depends on video driver ... you can allegedly swap in an older video card driver, e.g. from XP, but that disables Aero, which some other programs need to function properly.) No surprise. MS-DOS assumed that the active program owned the machine and could do anything. DOS apps tended to write directly to the screen instead of using BIOS calls for compatibility, because BIOS writes were too slow. . Windows really doesn't like you to address the hardware directly, because your program won't be the only thing running, and gets surly if you try, up to and including terminating your program. __ Dennis https://plus.google.com/u/0/105128793974319004519 -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
