Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!mcnc!ece-csc!ncrcae!ncr-sd!hp-sdd!hplabs!hpcea!hpsrla!hpsrlc!darrylo From: darrylo@hpsrlc.HP.COM (Darryl Okahata) Newsgroups: comp.sys.ibm.pc Subject: Re: PK ARC, Another View Message-ID: <3320034@hpsrlc.HP.COM> Date: Fri, 10-Jul-87 11:07:44 EDT Article-I.D.: hpsrlc.3320034 Posted: Fri Jul 10 11:07:44 1987 Date-Received: Sun, 12-Jul-87 14:38:08 EDT References: <287@cpsc6b.cpsc6a.att.com> Organization: Network Measurements Div - Santa Rosa, CA Lines: 53 In comp.sys.ibm.pc, dbercel@sun.uucp (Danielle Bercel, MIS Systems Programming) writes: >In article <287@cpsc6b.cpsc6a.att.com> crs@cpsc6b.cpsc6a.att.com (C. R. Seaman) writes: >> >>Interesting, that a ~30K COM file should determine that my 640K PC didn't >>have enough memory. I started poking around, and found that the problem >>was not really a lack of memory on my PC's part, but some confused >>interaction on the part of the software with my environment (I have it >>expanded to about 450 bytes). I discovered that, in order to run >>the PK ARC family, I must *completely* wipe out my environment! (I >>am using an AT&T PC6300, if that has any bearing). >> [ ... ] >You have described an environment that is *NOT* anywhere close to >my experience with PKARC and PKXARC. I run Phil's programs on my XT and >everything is fine. The environment doesn't have to be changed and >everything I've set for other programs remains unchanged. > [ ... ] > >From the various system I access, and the people I've spoken to, >nobody has been reporting the problems with PKARC and PKXARC that >you are having. Perhaps the environment problem is related to >your AT&T PC6300. > >danielle > > > >-- >UUCP: {hplabs,decvax,}!sun!toto!{danielle,dbercel} >/-------------------------------------\ >| Toto, I don't think this is Kansas. | -- Danielle Bercel >\-------------------------------------/ Sun Microsystems, Inc. >---------- I don't know what version I have, but pkarc gives me the same "out of memory" error on my PC -- and I have a true blue PC (64K motherboard). Pkxarc runs fine, however. Pkarc has about 300K of memory in which to play, so I know that the error message is bogus. Perhaps I'll look at it this weekend (maybe) using Periscope; I think the problem may have something to do with the values of the segment registers upon startup (Chris Dunford's PMAP utility says that pkarc is being loaded at segment 0x4030, 0x4040, or somesuch). -- Darryl Okahata hplabs!hpcea!hpsrla!darrylo CompuServe: 75206,3074 Disclaimer: the above is the author's personal opinion and is not the opinion or policy of his employer or of the little green men that have been following him all day.