Text 692, 78 rader
Skriven 2007-05-08 09:43:16 av Jeff Smith (1:14/0)
    Kommentar till text 685 av Marc Lewis (1:396/45.0)
Ärende: System peculiarities...
===============================
Hello Marc.

05 May 07 05:24, you wrote to all:

 ML> xc: COMP-OS2-NETWORK-MISC
 ML> Hello All.

 ML> Last week my BBS machine suffered from a bad memory stick... corrupted
 ML> zip files and that sort of garbage.  It's a 550MHz Intel Copamine
 ML> (sp?) processor. Unit had 2x128M PC133 sticks originally.  Replaced
 ML> both with 2x256M PC133.  No other changes, either hardware nor
 ML> software-wise.

 ML> Now I am running into a minor problem copying files to/from a
 ML> networked OS/2 machine.  The copy is successful, but very
 ML> substantially SLOWER than before.  It seems to be about the same in
 ML> either a VDM or straight OS/2 (under 4OS2 as a command processor).
 ML> Network settings haven't changed, nor has any hardware or software on
 ML> the other OS/2 Warp 4.52 machine.  Both are running under
 ML> FP6. Likewise copies initiated from the OTHER machine TO the BBS
 ML> machine are noticably slower.  Copies to/from drives on the BBS
 ML> machine are very fast; only across the network have the copies slowed
 ML> down.  The network is pretty much standard OS/2; no oddball protocols
 ML> or other addendums to it, just standard OS/2 Netbios and NetBEUI.

 ML> Further info:  The OS/2 DOS COPY command no longer works on either
 ML> OS/2 machine.  No matter what size file is copied or where it's copied
 ML> to/from this error pops up:

 ML> -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
 D:\>> copy ALLFILES.45 W:\WORK
 ML> SYS0008: There is not enough memory available to process this command.
 ML> All available memory is in use.
 ML>         1 file(s) copied.
 ML> (Though no file is actually copied in most cases.)
 ML> -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-

 ML> (In VDMs I utilise Patriquin's PCOPY instead (always have), but it
 ML> also runs into network errors when copying large files.  Even small
 ML> files (less than 1 Meg. for example) take a LONG time to copy across
 ML> machines, regardless of direction.)

 ML> Do you think that perhaps 1/2 Gig of memory is too much for this
 ML> machine or is there perhaps some undocumented problem with FP6beta.
 ML> If the problem lies in the FixPak, how would I roll back to an earlier
 ML> version?

     I think that the question of whether the motherboard fully supports
the new memory sticks may be a factor. I have a number of 256mb, 512mb simm's
and dimm's and have noticed that a lack of adequate support for the memory
by the motherboard is usually the problem or a flakey memory stick of course.
The MB may work perfectly fine otherwards.


 ML> UNRELATED QUESTION:

 ML> In the standard OS/2 DOS AUTOEXEC.BAT, what does the line:
 ML> "LOADHIGH APPEND C:\OS2;C:\OS2\SYSTEM" (immediately after the PATH
 ML> statement.) do ?

    If I recall correctly that commandline would append "C:\OS2;C:\OS2\SYSTEM"
to your PATH statement and load it in into the reserved area of memory (between
640K-1M).

 ML> Any help on these items will be VERY much appreciated!

 ML> Best regards,
 ML> Marc

 ML> ... If thine enemy offend thee, give his child a drum.
 ML> --- timEd/2 1.10.y2k+
 ML>  * Origin: Sursum Corda! BBS-Meridian, MS-bbs.sursum-corda.com
 ML> (1:396/45)

Jeff

--- FMail/Win32 1.60
 * Origin: Twin_Cities_Metronet - MN USA (1:14/0)