Hi guys, I think that Russian sites simply share a property of Chinese sites here: It is hard to reach the helpdesk, so they are useful for people who want to host materials of doubtful origin. On the other hand, even American computers have their very own cyber problem: Many cable and DSL users with very low understanding of computers, and therefore often used for zombie networks e.g. to send spam. They all speak English, so they are also a popular group of recipients for those who send spam.
Whatever. KAV is Russian (right?), why not. The FreeDOS problem in the whole story is that it uses ZRDX DOS extender (as does QV32 / QuickView, the DOS multimedia viewer), and that this DOS extender crashes on return to DOS. Back in the QV32 discussion I had the idea that this could be caused by too high stack usage during the extender shutdown process. The README tells that "512 bytes of common DOS stack" should be enough.. DOS32A DOS4GW and PMODE/W now work with FreeDOS afaik, and the DPMI16BI / RTM compatibility (vs. ramdisks and vs. int 21.30 returned CX) problems have been solved as well. My mail about ZRDX was in november. In january (I guess it turned out that stack size was not really changeable or did not help), Lucho called the problem with ZRDX "one of the toughest problems". See FreeDOS FAQ Using_FreeDOS 157. > the KAVDOS32 problem is in its Zurenava DOS extender (Russian, of > course ;-) Bind any 32-bit DOS executable with it and it'll hang on exit > under FreeDOS and cleanly exit under MS-DOS. Zurenava source and binary > code are available in a ZIP archive at http://dx.zr.spb.ru/zrdx047.zip A Russian but otherwise fine download location for ZRDX :-). Some old comments about ZRDX: > ZRDX tries DPMI, VCPI, XXMS, XMS, int15 in that order (you can move VCPI > first if you have a buggy DPMI already loaded, and you can configure the > maximum amount of allocated XMS and transfer buffer size and an amount > of DOS RAM that should be kept free - if you do not configure this, there > will be no XXMS / DOS RAM left, so you cannot shell out from the extended > program. ZRDX dynamically allocs stacks, callbacks, LDT and page tables as > needed. There is experimental (not enabled by default) support for a VMM > with swap file. LFN are supported, but FAT32 "int21.73xx" things not (i.e. > the extender will not alloc transfer buffers for those sub-functions that > would need them). Maybe a 386SWAT (or if you prefer SoftICE - but 386SWAT is free) wizard can finally find the problem of ZRDX - that would be great. Eric. ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
