| From: | Shawn Holwegner |
| Date: | 21 May 2001 at 15:39:12 |
| Subject: | ChangeMemPri, DKB3128, WarpOS issues |
Hi'ya folks,
I have been trying to change my memory priorities, as my DKB3128 is
preferred over the CSPPC RAM, which makes this poor machine too slow.
I believe the fact that I am BlizKicking may be causing an issue, and
that is why I am writing now, asking for help. The explanation continues:
I am BlizKicking v44.1b3 w/ various modules at the beginning of my
Startup-Sequence; I tried to change memory priorities via Startup-Sequence,
and realized that it gets re-run due to the various reboots required, which
would throw things even more out of whack =).
I thought that setting things later (e.g. WBStartup++ triggered script),
which caused the system to GURU with a WarpOS requester when I tried to
launch virtually anything.
What is an intelligent way I can test to see if the machine was warm
reset and not a cold boot? I want my fastest fast RAM back as the highest
priority.
I've thought about testing for ENV:, or the like, and do not really like
that solution, so... any takers?
- S
Quote carefully and read all ADMIN:README mails
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/