PK>  ME> What is the advantage to creating objects and running things as
object
ME> opposed to just making shadows or running with a program?
PK> 
PK> A Shadow of an Object is really a ALTERNATIVE REFERENCE to the original
obj
PK> it is not a COPY of the original. The prime advantage of this is that any 
PK> changes made to the Object using a SHADOW reference, makes changes to the 
PK> original Object itself. Its just a handy way of allowing the user to have 
PK> access to a resource from different places within their system, without
the
PK> need for the user to keep all those references in order, a SHADOW takes
car
PK> that for him automatically. A classic example of this is that the the Warp 

PK> Taskbar uses shadows for everything.

I'm not sure if this answers me or not since the way i phrased it may be 
unclear. I know when i make a shadow and then rename it, the original name
gets changed, I learned that the hardway :).  But if i create an object, can
i rename it (or create it) as any name i want?

here is likely what i should have asked....

In my zip shell program I use, I can open things in a file viewer or open
using object association.  so what is the difference between opening say a
text file with my text viewer (specified as an EXE) or creating my text file
viewer as an object? It seems to me an object is sort of like system wide, 
where as my text viewer will have to be specified in every program where i 
want to use it.

PK> You will probably receive a few different comments on this one. I use both 

PK> them here, the STARTUP Folder contains those items I ALWAYS want started,
a
PK> that dont have dependences with other items being started. 
PK> My STARTUP.CMD contains items that I want Started in a particular order,
an
PK> only when other items exist first! Examples of this include drive mappings 

PK> across the Network and functions that MUST be performed in strict sequence 

PK> system startup. I also have the option of stopping STARTUP.CMD at any
point
PK> I wish. 

I getcha. What is the format of the startup.cmd file? just plain text similar 
to a batch file?

PK> EG, on the BBS machine, the STARTUP Folder runs all the utilies that are
al
PK> loaded regardless. STARTUP.CMD cleans out my FLAGS directory (I use flags
t
PK> control various BBS backgrou tasks) and tidies up after any system
crashes.
PK> also checks that certain files exist before then staring each of the BBS
li

Any tips for running a dos bbs? thats pretty much all i will be doing on this 
machine....maybe i should ask you in the os2 bbs echo....

PK> Go to the System Setup Folder, Scheme Palette, and make your changes. Once 

PK> have the layout you want, then drag that layout to the desktop while
holdin
PK> down the ALT key. This makes the Pallette change system wide rather than
ju
PK> to the object it was dropped on.

so i can do this for fonts as well?

PK> Thats probably going to be a bit tight depending on what you wish to do
wit
PK> the system, however I would start by using HPFS partitions with no more
tha
PK> 512KB Cache, probably better off with 256KB. You system is going to do a
lo
PK> swapping with any decent sized applications running so too much cache may 
PK> actualyl slow it down. Start with 256 and then try 512 and see how that
aff
PK> it.

yes, I'm using only HPFS partitions. is this cache the line that starts:

IFS=C:\OS2\HPFS.IFS /CACHE:2048

or the one that is:

DISKCACHE=D,LW


PK> Dont run too many applications at the same time, try and close the ones
you
PK> dont need before opening up new ones. 

90% of the time it will be the bbs only as a single node. the other 10% will 
be the bbs and me locally at the same time


PK> If you have the chance, place your SWAPPATH on the MOST USED PARTITION, of 

PK> LEAST USED DRIVE! This helps to reduce the head movements and optimises
the
PK> swap file performance.

yes, I remembered this part. I have it on the only partition, on the second 
hard drive. Pretty much nothing will be on this drive except files for d/l'ing
from the bbs. Everything else will be on one of the 2 partitions on the first 
drive. this drive where the swap file is will be 500megs and i set the swap 
file at 16000 16000, so this means it will always leave 16megs free on the 
drive and will always start at 16megs in size, is that correct? I'll adjust
these once i get up and running to match what is actually going on.

thanx for the info

---
600
1500