Re: [Freedos-devel] Don't you think its better to use Msdos file names?
On Mon, 23 Feb 2004, Jim Hall wrote: I would prefer a C:\DOS directory with all exacutables inside. Users will feel more confortable with it ;-) My thought would be to put them inside C:\DOS as subdirs. Note that the install dir from the install program would need to use C:\DOS as the destdir, and the FreeDOS packages in the next distribution Actually, I would keep the BIN directory for the reasons you mentioned yourself (avoid conflicts installing two DOSes), but offer an options to move (or better hard-link ;-)) the BIN files into compatibly folder. Bye, -- Steffen Kaiser --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Don't you think its better to use Msdos file names?
Hi! 24--2004 20:04 [EMAIL PROTECTED] (Aitor Santamari'a Merino) wrote to [EMAIL PROTECTED]: mf C:\DOS - same as above + any support files I think, if there will be too many support files of some type (say, fonts), then they should be moved into own subdirectory (say, FDOS\FONT\*.cpi). Of course, application should search own data file_s_ in this subdirectory of startup directory. ASM In MS-DOS for most of the countries (I'd say) you rarely use much more ASM than EGA.CPI (or EGA2.CPI). So what? If many files are not used, you may remove them (to reduce used disk space), but originally there there more than one-two-three files. ASM I think that most interesting would be that the appropriate CPI file is ASM selectable from Install (but of course, this is a far away wish for ASM install while there may be other priorities). ASM Same goes for KEYBOARD.SYS and friends (when KEYB supports this, ASM hopefully soon). BTW, keyboard.sys may be placed into NLS. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Don't you think its better to use Msdos file names?
Hi, Arkady V.Belousov escribio': Hi! 24--2004 20:04 [EMAIL PROTECTED] (Aitor Santamari'a Merino) wrote to [EMAIL PROTECTED]: mf C:\DOS - same as above + any support files I think, if there will be too many support files of some type (say, fonts), then they should be moved into own subdirectory (say, FDOS\FONT\*.cpi). Of course, application should search own data file_s_ in this subdirectory of startup directory. ASM In MS-DOS for most of the countries (I'd say) you rarely use much more ASM than EGA.CPI (or EGA2.CPI). So what? If many files are not used, you may remove them (to reduce used disk space), but originally there there more than one-two-three files. The average user does not know what a CPI file is. Also IIRC Henrique has packed lots of CPI files (not only with standard DOS fonts, also Windows, KOI, etc, that may be a large number of CPI files and a quite a lot of space taken by DOS). Aitor --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Don't you think its better to use Msdos file names?
Arkady V.Belousov escribio': Hi! 24--2004 21:07 [EMAIL PROTECTED] (Aitor Santamari'a Merino) wrote to [EMAIL PROTECTED]: ASM In MS-DOS for most of the countries (I'd say) you rarely use much more ASM than EGA.CPI (or EGA2.CPI). So what? If many files are not used, you may remove them (to reduce used disk space), but originally there there more than one-two-three files. ASM The average user does not know what a CPI file is. We discuss directories hierarchy or knowledge of average user? I know that this knowledge is low, but this not (very) relates to hierarchy. No, we discuss wether it would be nice that Install removed the CPI files that the average user won't use in order to make room. (Just to be annotated as an interesting feature, of course; Install developers will evaluate the priority of this wish). ASM Also IIRC Henrique has packed lots of CPI files (not only with standard ASM DOS fonts, also Windows, KOI, etc, that may be a large number of CPI ASM files and a quite a lot of space taken by DOS). How this relates to directory, where these files should be placed (FDOS or, say, FDOS\FONTS)? In no way, as far as I know. Aitor --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Don't you think its better to use Msdos file names?
Alain wrote: Steve Nickolas escreveu: At Fri, 20 Feb 2004 3:19pm -0500, togermano.com wrote: Don't you think its better to use Msdos file names? So like a program can edit it. And its easyer for people that know msdos file names instead of like fddos for a directory etc.. Opinions vary but I do agree. -uso. I also agree. This was discussed some time ago, but we could open the chapter again because FreeDOS is getting really mature now I would prefer a C:\DOS directory with all exacutables inside. Users will feel more confortable with it ;-) Getting back to this topic .. I would like to update the docs on FD_DOC, and I want to make sure we have agreement before then. If we make this change, where to put source code, docs, etc? My thought would be to put them inside C:\DOS as subdirs. For example: DOS- all exe/com/sys files DOS\APPINFO- lsm files DOS\DOC\project- documentation for 'project' DOS\HELP - all help files DOS\NLS- national language support files DOS\SOURCE\project - source code for 'project' Note that the install dir from the install program would need to use C:\DOS as the destdir, and the FreeDOS packages in the next distribution would not use a 'BIN' directory - the exe/com/sys files would be at the 'root' of the .zip file. So this isn't a huge change. Sound okay to everyone? If you don't like this, then install your copy of FreeDOS in C:\FDOS instead of DOS, and the only thing that will be different for you is that you won't have a C:\FDOS\BIN. And a little history on this one: In the beginning, the plan was to keep FreeDOS separate from MS-DOS. This was because FreeDOS wasn't quite stable yet, so it was a good bet that many people would still have MS-DOS on the same system they installed FreeDOS. For example, you might still use the MS-DOS kernel, but use the FreeDOS Shell or FreeDOS utilities instead. However, FreeDOS has become quite mature, and I think it's a fair assumption that most (all?) FreeDOS users these days are using FreeDOS exclusively (no MS-DOS.) So it's time to look again at the decision we made long ago to use C:\FDOS as our install directory. -jh -- _ This email message has been automatically encrypted using ROT-26. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Don't you think its better to use Msdos file names?
Hi, --- Jim Hall [EMAIL PROTECTED] Alain wrote: My thought would be to put them inside C:\DOS as subdirs. For example: DOS- all exe/com/sys files DOS\APPINFO- lsm files DOS\DOC\project- documentation for 'project' DOS\HELP - all help files DOS\NLS- national language support files DOS\SOURCE\project - source code for 'project' This configuration makes me to go through all subdirectories to get a clear picture of a project. Will name crash happen in DOS\HELP like readme? I prefer: C:\DOS - same as above + any support files C:\DOC\project - the rest regards, BAHCL _ ... http://us.rd.yahoo.com/evt=22281/*http://ringtone.yahoo.com.hk/ --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Don't you think its better to use Msdos file names?
At Fri, 20 Feb 2004 3:19pm -0500, togermano.com wrote: Don't you think its better to use Msdos file names? So like a program can edit it. And its easyer for people that know msdos file names instead of like fddos for a directory etc.. Opinions vary but I do agree. -uso. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
