[Freedos-devel] PG version 1.10 (Final)

2004-02-28 Thread maintainer freedospg
Hi,

I would like to announce PG 1.10 is ready now at
www.geocities.com/freedos_pg, changes include:
1. accepts lowercase commands again;
2. works fine and clean with 25,28,50 lines display
modes;
3. displays panning offset if  0;
4. sychronizes data in plugins;
5. uses only 35K system memory as it shells out; 
6. is able to find PG.MAN if properly setup;
Keep PG.MAN and PG.EXE in the same directory
accessible with %PATH%

Tested with:
1. Linux + X + DOS in a box   all features work
2. Linux DOSEMU 1.2.0 all features work
3. FreeDOS native modeall features work
4. M$DOS 6.2, 7.1 native  all features work
5. M$ Windows DOS box sychronize data not work
as Intra Application Communication Area 40:F0 modified
by M$ Windows.

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] re: PG version 1.10 (Final)

2004-02-28 Thread Arkady V.Belousov
Hi!

28--2004 23:26 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:

 5. M$ Windows DOS box sychronize data not work
 as Intra Application Communication Area 40:F0 modified
EA You did WHAT? Why that? This sounds very incompatible to
EA whatever future extension to BIOS data area might show up.

__O\_/_\_/O__
--M004000F0--
MEM 0040h:00F0h - INTRA-APPLICATION COMMUNICATION AREA
Size:   16 BYTEs
_
  O/~\ /~\O
__O\_/_\_/O__
40:00f0  16  (IAC) Inter-Aapplication Communication area.  Programs may use
 this area to store status, etc.  Might get overwritten by
 another program.
_
  O/~\ /~\O




---
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


[Freedos-devel] Possible BUFFER / LBAcache / UPX bug?

2004-02-28 Thread Eric Auer

Hi, I got some strange problems today. Maybe some bug in BUFFER
handling or LBAcache. I am using FreeCOM 0.82pl3 and kernel 2033
and lbacache,sys buf 30 flop (device, while FreeCOM is shellhigh,
using umbpci with non-cached but dma-enabled UMBs). XMS driver is
HIMEM64 of 1 Feb 2004, compressed (with SY2PACK, I guess).
I compiled a small (12k) program and UPXed it in DOS.
After that, the program would crash. In another attempt,
after UPXing, copying the program elsewhere would give
me the de-UPXed version in the target directory. Only after
renaming it to another extension, the effect stopped. Sounds
like a virus, but I was unable to find anything in RAM.
In a third attempt, copying the UPXed program resulted in
1 cluster being written in the target dir: That cluster contained
the contents of the target dir itself (empty except for a 0 byte
file with the target file name). In several other attempts between
those 3 spooky ones, UPXing simply worked. I never found any file-
system errors with CHKDSK 0.31 or DOSFSCK 2.8 on this FAT16 file-
system, even while in spook state. I cannot really reproduce
either. Nor can I figure out whether it is kernel / BUFFERS / LBAcache
or something else which causes the strange behaviour. LBAcache is
the sys version of 23 Oct 2003, UPXed.

So my question is: Can you reproduce anything like this? Like after
UPXing many small files any strange behaviour in using them, possibly
only after flushing / removing buffers and/or LBAcache or rebooting?
Maybe this is simply caused by something else, like EDIT DOS shell
mode or that FreeCOM context memory leak problem. Anyway, if somebody
wants to try himself, we would know if the problem is real or only
spurious (and not a bug which should be fixed by an update).


The programs were = 8192 bytes after UPXing, so size went down by  1 cluster.

Oh, extra oddity: At one time trying to add the program to a ZIP resulted in
1024*10 bytes of a zip (probably the same zip) being added instead of the
real contents of the program binary. The affected program was 12k or 13k big.

Curious whether there is a bug behind this or just a general system
instability because of other things which I had done at that moment :-).

Eric.




---
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


[Freedos-devel] re: re: PG version 1.10 (Final)

2004-02-28 Thread Eric Auer

Hi BAHCL,

 Memory area 40:F0..FF is documented in RBIL
Arkady already told me
 Besides, can C compiler take NULLs \x0 as part of a
 parameter string?
No but it would be VERY simple to convert the 32bit value to an ASCII
string like 42 instead of using 0x2aL. That way, you can use a command
line argument instead of having to use 40:Fx as transfer area (which is,
as you noticed, not compatible to Windows even if RBIL tells it should...).

 2. PLUGINs works as stand alone program too.
If you have e.g. convert to HEX as feature in PG, then no need to have
a separate binary for that! Simply do for example:
PG /TOhex  file.bin  file.hex
Much smaller on disk: Remember that each file will be at least 1 cluster big.
 5. All in one program takes up more resources.
Why?

 1. PLUGINs works with PG, no adverse effect.
I think there is an adverse effect! If you use pipes to communicate between
PG and the plugins, DOS will need temp files to simulate the files - PG
will e.g. only be able to display files as hex if DOS is able to write the
temp files...

  Why does PG contain a blacklist which makes it
  refuse to open bin com dll drv ...

 PG is a text file browser, as defined in its document,

Yes, but who is PG to tell the user that it is FORBIDDEN to look into
DLL files with PG? Especially given the fact that PG has an hex dump view?
Is PG going to tell me sorry, you are only allowed to see the hex dump of
TXT files, enjoy... ???

Eric.



---
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