untgz and double zipping (was Re: Re: [fd-dev] Enquiry: Update packs)
On Mon, 2 Dec 2002, tom ehlert wrote:
But this is tricky to unpack
No.
Depends :)
and needs more temp space.
Yes.
Not necessarily.
I recommend using TGZ in that case.
not available for DOS.
It is, see:
ftp://ftp.cs.pdx.edu/pub/elvis
It's called untar, but it really is untgz.
((Er, it's also the coolest editor around ;-
but only a monolithic TAR+GZ would avoid
the temp space problem
And if I'm not mistaken, this one is one.
BTW: I slightly remember that the INSTALLER already includes the UNZIP
source(s). When you do a UNZIP archive.ZIP, there is no need to seek
around within the file, no need to read the ZIP directory and stuff; so
the UNZIP loop might looks like the one in untar:
while(read a chunk from the ZIP file) {
if(new file header) {
create the file
open the file
} else {
decompress the block into the currently open file
}
}
Does somebody know about the memory consumption of the decompression
process and if two of them can exists in parallel simultaneously? Then and
if you know that you unpack a double-zipped archive in advance, it should
be easy to implement it. -- Where is the volunteer? ;-)
Bye,
--
Steffen Kaiser
--
list options/archives/etc.: http://www.topica.com/lists/fd-dev
unsubscribe: send blank email to: [EMAIL PROTECTED]
==^
This email was sent to: archive@mail-archive.com
EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^
RE: untgz and double zipping (was Re: Re: [fd-dev] Enquiry: Update packs)
Steffen Kaiser Does somebody know about the memory consumption of the decompression process and if two of them can exists in parallel simultaneously? Then and if you know that you unpack a double-zipped archive in advance, it should be easy to implement it. -- Where is the volunteer? ;-) If you use the zlib uncompressor, you need a buffer of max 32K for good results. I don't know how much memory the zlib code would take since I have only used it for Windows progs. -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
Re: [fd-dev] [hands on!] COUNTRY= and load_unf
On Mon, 2 Dec 2002, Bart Oldeman wrote: - the new country info only affects secondary shells, not the freecom that you run load_unf.exe from Arrgh, did you filed this bug? Bye, -- Steffen Kaiser The current maintainer of [EMAIL PROTECTED] http://freedos.sourceforge.net/freecom/FreeCOM.html -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
Re: [fd-dev] Enquiry: Update packs
Eric Auer wrote: Hi Aitor, you did not get the point... when you zip 100 files that are the same, the zip will be 100 times some size. However, when you use an UNCOMPRESSED zip, then the file will basically contain 100 times the same data structure. TAR is in principle the same as an uncompressed zip, but it is more UNIX while zip is more DOS. Yes, I knew this. However, we are talking about the resident size it will take in your harddriver after it has been installed. I am not trying to discuss the reduced/full issue. Aitor -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
Re: [fd-dev] DISPLAY CON?=
tom ehlert wrote: One could at least think of having multiple console drivers residing concurrently in a system, say CO80: and BW80: connected to different video systems and screens, and CON dynamically assigned one can *always* think of something, that would break something else. but with this kind of thinking, FAT16 would never have been presented to users (there might be drives larger then 1 Gb ...) BTW: I have a dual monitor configuration the second IS HGC I USE the hercules card - nearly every day I NEVER EVER got even the idea to install a DOS driver for that. I'm VERY happy to have a HGC card (and minitor) IMO, I prefer working 2003 for 98% all cases over might work in 2010 - eventually (if I'm not too busy) sorry for being harsh, but these 'one could think of' messages effectively STOP all useful work. Well, just a bit of positivity: at least it opens your mind to other possibilities, not meaning that they are going to be implemented in the near future. For example, I am conscious that DISPLAY should be a device driver that should parse files in a format being part of a CPI file, but if I had implemented this, I wouldn't have released any DISPLAY yet. Well, just it's nice to know even if just for information... (my opinion). Aitor -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
[fd-dev] resubscribe
Hi! My email was banned on fd-dev in last hours, so I try to resubcribe and resend two next letters again. -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
Re: [fd-dev] Enquiry: Update packs
X-Comment-To: Aitor Santamaria Merino Hi! 3-äÅË-2002 16:55 [EMAIL PROTECTED] (Aitor Santamaria Merino) wrote to [EMAIL PROTECTED]: ASM Well, the good point is that the code could be disposed after loading KEYB. Of course. ASM I haven't used these libraries, but I just wonder if one can decompress ASM parts of a file, if the layouts are all (or most) in a single ASM KEYBOARD.SYS file. Why not? Simply pack file by separate parts (for example, split file by 2k-16k blocks/pages). To speedup seek you may also keep tabe of offsets to each page. ASM In any case, I think I'll leave this for version 3.X, there's enough ASM stuff to keep me busy with 2.X already ;-) -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^^=== This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^^===
Re: [fd-dev] DISPLAY CON?=
On 2002-12-03, Tom Ehlert wrote: I have a dual monitor configuration the second IS HGC I USE the hercules card - nearly every day I NEVER EVER got even the idea to install a DOS driver for that. I'm VERY happy to have a HGC card (and minitor) Fine, I'm too. All my systems are dual screen systems (most of them SVGA + HGC) and I know several people, who do use dual screen drivers to redirect text to just the other screen using something like: ECHO Foo CO80: ECHO Bar BW80: ECHO Hello World CON: IMO, I prefer working 2003 for 98% all cases over might work in 2010 - eventually (if I'm not too busy) Hm, being at 98% in 2003 is completely illusoric, IMHO. The FreeDOS kernel has made significant progress, that's great. And there are a few really outstanding drivers and utilities. But being realistic, several more years of hard work will have to go by before the majority of the FreeDOS utility set will have reached the same level of maturity as in MS-DOS/PC DOS or DR-DOS. I hope it will happen eventually. As I see it, the most significant problem for many volunteers is simply lack of knowledge, what's actually going on under the hood, and also of the historical background, why some DOS components were designed this way and not another, originally. Knowing this helps to better understand DOS' internals. Hence, I'm trying to share what I can share (and my time allows), and I'm also very happy to learn from others, where they can provide expertise. sorry for being harsh, but these 'one could think of' messages effectively STOP all useful work. No, not in my opinion. Knowledge can never harm, being ahead in ideas and design compared to the actual implementation cannot either. It enables people to create better and more compatible software. Not knowing issues will often lead into dead ends or cause compatibility issues. Look at most questions raised in the DOS related newsgroups (probably even more so in the Windows groups), most of them are the result of lacking knowledge or improper documentation. Of course, even with enough knowledge it is still some kind of trial-and-error process, but I hope the learning curve will be much higher, as potential mistakes can be identified much earlier. IMHO the fine arts of engineering is to find the right compromise, that is, to /be/ knowledgable at first, and then /actively/ decide to temporarily put down some marginal issues to fulfill the deadline. But since there is no deadline for FreeDOS, and we do have mature and flexible (but now for the most part static) DOS issues already, there is IMHO no point in recreating the wheel without coming up with a better solution in the end... ;-) I don't say, the first release will/could/should be final, but if you don't think of potentially planned extensions right from the start, you might have to start from scratch in the middle of the project. However, my comments are never meant like Please implement this for me - if I'd need it for myself *now*, I could and would sure just implement it myself. But I usually use DR-DOS anyway, so I won't have any direct advantage of FreeDOS extensions except for enjoying that some of the DR-DOS features and ideas are spreading into other implementations, thereby making DOS as is a more convenient and attractive platform, which, I hope, will keep it alive a bit longer. That's also why I care that my own solutions are compatible with any DOS, including FreeDOS and DR-DOS. My comments are always meant as Please take this non-obvious issue/ idea into account, while working on xyz so that different solutions stay compatible with each other. I have seen more than one FreeDOS component being seriously incompatible with established DOS standards due to an only partial understanding and therefore implementation of the standard, and while it is always possible to fix these problems in later issues, I see no purpose in introducing them in the first place. I don't know how this would be possible without deeper insight, that's why I try to answer questions raised here and give some background info. --- On 2002-12-03, Aitor Santamaría Merino wrote: Suppose that I name DISPLAY as device CO80:, who assigns CON to CO80: ? DISPLAY.SYS loads on top of another console driver, usually named CON:. I doubt other names of the console driver will be accepted despite the syntactical provision for the parameter. The CON: string is probably hardwired into the driver at the moment. But if you could already attach DISPLAY.SYS to other console drivers (as it for sure was planned to be possible), the CON: driver itself would have to use the, say, CO80: (or BW80:) driver internally, just like the PRN: driver internally uses the LPT1: driver (unless you are under a DOS issue where you can reassign this). If you would want independent codepage switching on both, CO80: and BW80:, you would have to load DISPLAY.SYS on top of both console drivers, I guess. Hypothetical example: DEVICE=DISPLAY.SYS
re: Re: [fd-dev] Modifying character's shape
Hi, I repeat: The error scenario is too improbable! - You are NOT supposed to place a text mode program into graphics mode anyway. Many write into the screen buffer directly and you will not see any text unless you give them a REAL text mode. - I hardly know any program that reads the screen at all, apart from screen shot programs, which would dump a graphical screen dump when they find the mode to be non-text normally. - You can add a warning that people should issue a CLS after loading another font - most font loaders do so anyway. And the error is VERY exotic. Add it to the X-files error possibilities in the readme, this is more than enough. Eric. -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
Re: [fd-dev] DISPLAY CON?=
Matthias Paul wrote: DEVICE=DISPLAY.SYS co80:=(ega,437,(6,3)) DEVICE=DISPLAY.SYS bw80:=(mono,(437,161),0) Interesting... understood. Well, this means that if a user makes a mistake like: DISPLAY CONN=(EGA,437,(6,3)) then it won't prevent DISPLAY from loading, but it won't work ;-) The : I assume it's optional Many times it appears, many others it doesn't. (and a silly comment, the : after the driver name makes your commandline look as if the := were the Pascal assignment operator ;-)) Hey, now that I notice, I'll have to review in the documentation (possibly in your long messages about internationalisation) what is meant by (437,161) At a first sight, the device to be replaced is single, the codepage should be single too (?). Note, that (unfortunately only) the DR DOS 6.0+ PRINTER.SYS driver supports multiple drivers in one go as in this example: DEVICE=PRINTER.SYS lpt1:=(1050,367,12) lpt2:=(4201,850,2) lpt3:=(5202,437,2) The advantage is that the code will be shared between these drivers and only the data is kept separate for each of them, resulting in a significantly reduced memory footprint compared to the usual sequence of: DEVICE=PRINTER.SYS lpt1:=(1050,367,12) DEVICE=PRINTER.SYS lpt2:=(4201,850,2) DEVICE=PRINTER.SYS lpt3:=(5202,437,2) So, at a later stage (not now!), it might be worth thinking about adding something similar to DISPLAY.SYS as well: DEVICE=DISPLAY.SYS co80:=(ega,437,(6,3)) bw80:=(mono,(437,161),0) Right A wish for the future, for a far future I guess :-) As another sidenote, under DR-DOS 7.02+ you can use the [D]CONFIG.SYS PRN=0,1..3,4 and AUX=0,1..4 directives to change the defaults. The main advantage of this being implemented into the DOS BIOS is that it required zero extra memory compared to a non-enhanced system (where you would have to overload drivers or hook into the System BIOS interrupts for a similar effect). I have seen something similar in the Waite group's book on DOS drivers, in the PRINTER driver, which is a driver for a printer in ANY port (or for several printers) you use IOCTL commands to change the port. Aitor -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
[fd-dev] OT: DRDOS 7.03
OT: FYI: I noticed DRDOS.COM has 7.03 image available for download (license)? -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
Re: [fd-dev] DISPLAY CON?=
IMO, I prefer working 2003 for 98% all cases over might work in 2010 - eventually (if I'm not too busy) Hm, being at 98% in 2003 is completely illusoric, IMHO. you are right. but then I prefer 80% in 2003, and hope for 95% in 2010 IMHO the fine arts of engineering is to find the right compromise, that is, to /be/ knowledgable at first, and then /actively/ decide to temporarily put down some marginal issues to fulfill the deadline. here I agree 100% But since there is no deadline for FreeDOS there is a deadline. today. each cyrillic user that hits FreeDOS and says 'Nice - IFF it would only have cyrillic fonts/codepage/...' is a lost user. I'm after something useful - NOW. DEVICE=DISPLAY.SYS co80:=(ega,437,(6,3)) bw80:=(mono,(437,161),0) AFAIK, there is no possibility to change the fonts on BW80 =HGC ? and so there is no need for display to do anything to BW80. and if you have echo hello worldCO80 echo hello worldBW80 you better keep 'hello world' below 0x80; else results will probably not be expected. tom -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
re: Re: [fd-dev] DISPLAY CON?=
Hi, I believe BW80 and BW40 are EGA/mono and CGA/mono modes, while MONO is used for HGC and MDA. Indeed, HGC has a fixed font as far as I can tell, but if you have MSHERC or similar loaded, you have modes 8/similar which are graphical but have the BIOS draw character stuff done by the driver. THEN you could change the font - by writing your own MSHERC (MSHERC seems to be used by some MS programming languages as a helper). And I believe MDA has no graphics or anything, thus no user fonts. Eric. -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
Re: [fd-dev] OT: DRDOS 7.03
On Wed, 4 Dec 2002, Mark Olesen wrote: OT: FYI: I noticed DRDOS.COM has 7.03 image available for download (license)? Nothing new here (non-commercial or 90 days evaluation use only) BIG FAT AD See what Doctor DOS can't let you see ... Use FreeDOS and you get FAT32, LBA, source code and unlimited commercial use for free! Bart -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
