Attn: Mart -- Not enough memory

Hi Mart :-))

So glad you found me--had a hard time finding my post myself! I clicked
"New Message" to send in my news but I guess I should have used a fresh
subject line? I can't figure how these newsgroup threads work :-b

Anyway, I've tried two different drivers for my sound card--the one on CD
that came with it, and another I got from the Creative web site. Neither
made any difference in the way it performed. At one point before I replaced
the HD, the properties sheet for the sound card told me I was not authorized
to make any changes! (it's allowing them now though). In view of the card's
gradual performance decay and recently developed blue-screening of a variety
of programs (which always happens after a series of rapid ticks, clicks,
beeps or midi plays--never after just the occasional noise), I'll be very
happy to have a new one. I once had a spanking new Creative CDRW that never
wrote me but three CD's that could be read: I threw out over a dozen
failures and lost my temper too '-) ; so in all, my experience with that
brand of computer products has been VERY NOT satisfactory.

After having more than my fair share of problems with new hardware, it had
crossed my mind that I might have defective RAM also :-( but didn't know
how to check it. I did manage to get WEFT to install perfectly right after
a first boot (not a reboot) but haven't altered Windows' memory handling.
I've checked out all Noel's suggestions except for the corrupted swap file,
which I can't believe has happened after only a couple weeks of use! I
keep all my Temp folders emptied and use Diskeeper to defrag. I reset the
SysRes cache at 1095 MB (it was either that or 200 MB--no setting in
between?) and its size is 604 MB, 2550 files, 5 folders. I've still got
59.9 GB of free space on C.

Thanks muchly for your time and info and the link to DocMemory. I'll post
back with the results.

calamity carol





"Mart" wrote in message
...
Hi Carol, good to see that you've managed to replace and set-up your new
Samsung HDD.

Your 'sound' and OE problems *may or may not* have something to do with
your
RAM issues, but until you sort the RAM out, don't try troubleshooting too
many things at once - it'll only lead to confusion g

FWIW - my 'guess' is that the underlying cause of your sound card problems
is more likely to be driver related - but see previous paragraph. If the
card is 'pre-WinMe' you may well have problems finding the 'perfect' WinMe
drivers and have to put-up with the WDM (Windows Driver Model) versions
supplied on the WinMe CD (or even Win98 drivers) and live with their
short-comings. Not many manufacturers were interested in writing WinMe
drivers for their obsolete sound cards - Cynical? Moi??

However, you say that you have only 512 MB fitted, so the Q253912 article
should not be relevant - it only applies to memory greater than 512 MB.

If you think that your memory *may be* faulty, check out your memory chips
using Simmtester's DocMemory from www.simmtester.com or
http://www.simmtester.com/page/products/doc/docinfo.asp and create the
boot
disk from that - run it overnight to check the RAM.

One other possibility is that you *may not* be letting Windows manage your
swap-file. Confirm that there are no min/max limits set by the User. Let
Windows manage it. Don't forget to defrag too g But I seem to recall
Noel
giving you some pointers in this direction last November.

Regarding WEFT, I've no knowledge of this 'application' so I can't really
help you with it. However, you should try to confirm that it is expected
to
run with a minimum of 512 MB from
the 'minimum requirements' product specification. Again, see your previous
threads for pointers from Noel and Mike etc.

In view of the date of the original thread - August thru' December last
year - and especially with the change of HDD and a 'clean' installation
since then, it might be a good idea to start a brand new thread/topic.
Keep
to a single issue per topic and don't forget to include error reports.

HTH and good luck

Mart


"caroloyl" wrote in message
...
Hi there!

I'm back up and running :-)) Installed and formatted the new Samsung
drive
myself December 30 and am still slowly installing my programs.

My sound problem with OE and other programs didn't go away--not with
either
the new drive or fresh Me and sound-driver install--so I've ordered a
new
sound card. The sound has been doing other peculiar things for ages,
like
playing a midi in two different keys at once and "wobbling" (nope,
don't
have reverb)--so I'm guessing it's used up after less than three years
(the
life span of cheap?)

But I'm really writing for help again with the subject line here because
I'm
still getting the "not enough memory . . ." error. I got that warning
three
times trying to install WEFT (MS' embedded-font making tool) before it
finally completed. Never had that happen before and I've used WEFT for
years--so I did a little looking around in the MS database and found
this
item referring to having this problem with large amounts of RAM
installed
(I
have 512 MB):

http://support.microsoft.com/support.../Q253/9/12.asp

It offers two fixes of which--to me--this one, editing the Sys ini file,
looks easiest since I haven't a clue what the other's about:

http://support.microsoft.com/kb/108079/EN-US/

I've looked at my sys ini and there is nothing at all entered under the
[VCache] section. Can specifying a maximum amount for Windows to use
help
me? And if so how much should I allow it? I read somewhere recently
that
if unlimited Windows will glom all the available RAM leaving no room for
opening another platform (have I remembered that right?)--and I do
believe
WEFT uses a different one for installation (coarse fonts in the dialog).
I've also just found an "out of memory" error in a Java log after trying
unsuccessfully to download an applet (installed the latest Sun Java
program
a few days ago).

Your help, as always, much appreciated.

carol




A couple of things to mention:
"caroloyl" wrote in message news:...
Thanks for the reassurance guys--I needed that . . . and for your time
assessing this matter. I'm sure hoping this will be the end of the
line
for
my string of problems--and I'm consoled to find once again Millennium
is
not
to blame.

carol



"Mart" wrote in message
...
Noel wrote:-

The fact that the utility would not complete is almost certainly
sufficient evidence that there are physical problems with the HD.
... etc., etc., ..

I totally concur with your comments, Noel.

For whatever cause - heat, mechanical, surface, etc., - Carol has a
(terminally) 'sick disk'

Mart

Hi Carol, I await to hear the results of your DocMemory tests with interest,
although I'm no longer particularly suspecting RAM issues.

Regarding Diskeeper, like WEFT, I don't use it so can't comment (although
several other 'regulars' on these WinMe News Groups do and report good
results), I prefer to use Scandisk (and Defrag) as supplied by MS. My
philosophy being that as MS 'invented' Windows, then their own maintenance
utilities *ought* be adequate. My experience of certain Third Party
utilities is "disappointment" - e.g. Norton (I've never touched their
products since the mid 90's when they progressed?? from DOS to Windows and
the 10ft bargepole took on a whole new meaning g) I tend to use almost
exclusively (except AV utils) MS utilities and am still here to tell the
tale.

As I mentioned previously, 'older' soundcards do not sit too comfortably
with WinMe and what a surprise that you mentioned Creative g. Forget
using their 'bundled' (Win95/98) application software on WinMe - it won't
install properly, if at all. Uninstall it (and the drivers - in Safe Mode)
and just re-install their (Win98?) drivers ONLY during the reboot (Plug 'n
Play)

Don't expect any of the original fancy gimmicks (which you might have
experienced in Win95/98) and you *might* just find that your .mid files
sound reasonably good.

... I once had a spanking new Creative CDRW that
never wrote me but three CD's that could be read:
I threw out over a dozen failures

CD-R's & CD-RW's? - Can often depend on the different 'quality' between
manufactures - try a different brand. And sadly, this has also been known to
apply to different brands of CD-ROM's and perhaps even more importantly,
between different software houses and their versions of burning software.
Not all CD-ROM's are recognised by all versions of software, nor media by
the CD-ROM - a slight blurring of science, (black) art and moving goal
posts.

Mart



"caroloyl" wrote in message
...
Hi Mart :-))

So glad you found me--had a hard time finding my post myself! I clicked
"New Message" to send in my news but I guess I should have used a fresh
subject line? I can't figure how these newsgroup threads work :-b

Anyway, I've tried two different drivers for my sound card--the one on CD
that came with it, and another I got from the Creative web site. Neither
made any difference in the way it performed. At one point before I
replaced
the HD, the properties sheet for the sound card told me I was not
authorized
to make any changes! (it's allowing them now though). In view of the
card's
gradual performance decay and recently developed blue-screening of a
variety
of programs (which always happens after a series of rapid ticks, clicks,
beeps or midi plays--never after just the occasional noise), I'll be very
happy to have a new one. I once had a spanking new Creative CDRW that
never
wrote me but three CD's that could be read: I threw out over a dozen
failures and lost my temper too '-) ; so in all, my experience with that
brand of computer products has been VERY NOT satisfactory.

After having more than my fair share of problems with new hardware, it had
crossed my mind that I might have defective RAM also :-( but didn't know
how to check it. I did manage to get WEFT to install perfectly right
after
a first boot (not a reboot) but haven't altered Windows' memory handling.
I've checked out all Noel's suggestions except for the corrupted swap
file,
which I can't believe has happened after only a couple weeks of use! I
keep all my Temp folders emptied and use Diskeeper to defrag. I reset the
SysRes cache at 1095 MB (it was either that or 200 MB--no setting in
between?) and its size is 604 MB, 2550 files, 5 folders. I've still got
59.9 GB of free space on C.

Thanks muchly for your time and info and the link to DocMemory. I'll post
back with the results.

calamity carol





"Mart" wrote in message
...
Hi Carol, good to see that you've managed to replace and set-up your new
Samsung HDD.

Your 'sound' and OE problems *may or may not* have something to do with
your
RAM issues, but until you sort the RAM out, don't try troubleshooting too
many things at once - it'll only lead to confusion g

FWIW - my 'guess' is that the underlying cause of your sound card
problems
is more likely to be driver related - but see previous paragraph. If the
card is 'pre-WinMe' you may well have problems finding the 'perfect'
WinMe
drivers and have to put-up with the WDM (Windows Driver Model) versions
supplied on the WinMe CD (or even Win98 drivers) and live with their
short-comings. Not many manufacturers were interested in writing WinMe
drivers for their obsolete sound cards - Cynical? Moi??

However, you say that you have only 512 MB fitted, so the Q253912 article
should not be relevant - it only applies to memory greater than 512 MB.

If you think that your memory *may be* faulty, check out your memory
chips
using Simmtester's DocMemory from www.simmtester.com or
http://www.simmtester.com/page/products/doc/docinfo.asp and create the
boot
disk from that - run it overnight to check the RAM.

One other possibility is that you *may not* be letting Windows manage
your
swap-file. Confirm that there are no min/max limits set by the User. Let
Windows manage it. Don't forget to defrag too g But I seem to recall
Noel
giving you some pointers in this direction last November.

Regarding WEFT, I've no knowledge of this 'application' so I can't really
help you with it. However, you should try to confirm that it is expected
to
run with a minimum of 512 MB from
the 'minimum requirements' product specification. Again, see your
previous
threads for pointers from Noel and Mike etc.

In view of the date of the original thread - August thru' December last
year - and especially with the change of HDD and a 'clean' installation
since then, it might be a good idea to start a brand new thread/topic.
Keep
to a single issue per topic and don't forget to include error reports.

HTH and good luck

Mart


"caroloyl" wrote in message
...
Hi there!

I'm back up and running :-)) Installed and formatted the new Samsung
drive
myself December 30 and am still slowly installing my programs.

My sound problem with OE and other programs didn't go away--not with
either
the new drive or fresh Me and sound-driver install--so I've ordered a
new
sound card. The sound has been doing other peculiar things for ages,
like
playing a midi in two different keys at once and "wobbling" (nope,
don't
have reverb)--so I'm guessing it's used up after less than three years
(the
life span of cheap?)

But I'm really writing for help again with the subject line here
because
I'm
still getting the "not enough memory . . ." error. I got that warning
three
times trying to install WEFT (MS' embedded-font making tool) before it
finally completed. Never had that happen before and I've used WEFT for
years--so I did a little looking around in the MS database and found
this
item referring to having this problem with large amounts of RAM
installed
(I
have 512 MB):

http://support.microsoft.com/support.../Q253/9/12.asp

It offers two fixes of which--to me--this one, editing the Sys ini
file,
looks easiest since I haven't a clue what the other's about:

http://support.microsoft.com/kb/108079/EN-US/

I've looked at my sys ini and there is nothing at all entered under the
[VCache] section. Can specifying a maximum amount for Windows to use
help
me? And if so how much should I allow it? I read somewhere recently
that
if unlimited Windows will glom all the available RAM leaving no room
for
opening another platform (have I remembered that right?)--and I do
believe
WEFT uses a different one for installation (coarse fonts in the
dialog).
I've also just found an "out of memory" error in a Java log after
trying
unsuccessfully to download an applet (installed the latest Sun Java
program
a few days ago).

Your help, as always, much appreciated.

carol




A couple of things to mention:
"caroloyl" wrote in message news:...
Thanks for the reassurance guys--I needed that . . . and for your time
assessing this matter. I'm sure hoping this will be the end of the
line
for
my string of problems--and I'm consoled to find once again Millennium
is
not
to blame.

carol



"Mart" wrote in message
...
Noel wrote:-

The fact that the utility would not complete is almost certainly
sufficient evidence that there are physical problems with the HD.
... etc., etc., ..

I totally concur with your comments, Noel.

For whatever cause - heat, mechanical, surface, etc., - Carol has a
(terminally) 'sick disk'

Mart

... I once had a spanking new Creative CDRW that
never wrote me but three CD's that could be read:
I threw out over a dozen failures
It should be mentioned that upgrading the "firmware" will often resolve
burning issues, aside from suitable media. Firmware upgrades can be had at
the manufacturer's website. Myself and a friend have determined this can
make the difference between burning a good CD/DVD and making coasters.
Heirloom, old and think it's gonna rain

"Mart" wrote in message
...
Hi Carol, I await to hear the results of your DocMemory tests with
interest, although I'm no longer particularly suspecting RAM issues.

Regarding Diskeeper, like WEFT, I don't use it so can't comment (although
several other 'regulars' on these WinMe News Groups do and report good
results), I prefer to use Scandisk (and Defrag) as supplied by MS. My
philosophy being that as MS 'invented' Windows, then their own maintenance
utilities *ought* be adequate. My experience of certain Third Party
utilities is "disappointment" - e.g. Norton (I've never touched their
products since the mid 90's when they progressed?? from DOS to Windows and
the 10ft bargepole took on a whole new meaning g) I tend to use almost
exclusively (except AV utils) MS utilities and am still here to tell the
tale.

As I mentioned previously, 'older' soundcards do not sit too comfortably
with WinMe and what a surprise that you mentioned Creative g. Forget
using their 'bundled' (Win95/98) application software on WinMe - it won't
install properly, if at all. Uninstall it (and the drivers - in Safe Mode)
and just re-install their (Win98?) drivers ONLY during the reboot (Plug 'n
Play)

Don't expect any of the original fancy gimmicks (which you might have
experienced in Win95/98) and you *might* just find that your .mid files
sound reasonably good.

... I once had a spanking new Creative CDRW that
never wrote me but three CD's that could be read:
I threw out over a dozen failures

CD-R's & CD-RW's? - Can often depend on the different 'quality' between
manufactures - try a different brand. And sadly, this has also been known
to apply to different brands of CD-ROM's and perhaps even more
importantly, between different software houses and their versions of
burning software. Not all CD-ROM's are recognised by all versions of
software, nor media by the CD-ROM - a slight blurring of science, (black)
art and moving goal posts.

Mart



"caroloyl" wrote in message
...
Hi Mart :-))

So glad you found me--had a hard time finding my post myself! I clicked
"New Message" to send in my news but I guess I should have used a fresh
subject line? I can't figure how these newsgroup threads work :-b

Anyway, I've tried two different drivers for my sound card--the one on CD
that came with it, and another I got from the Creative web site. Neither
made any difference in the way it performed. At one point before I
replaced
the HD, the properties sheet for the sound card told me I was not
authorized
to make any changes! (it's allowing them now though). In view of the
card's
gradual performance decay and recently developed blue-screening of a
variety
of programs (which always happens after a series of rapid ticks, clicks,
beeps or midi plays--never after just the occasional noise), I'll be very
happy to have a new one. I once had a spanking new Creative CDRW that
never
wrote me but three CD's that could be read: I threw out over a dozen
failures and lost my temper too '-) ; so in all, my experience with that
brand of computer products has been VERY NOT satisfactory.

After having more than my fair share of problems with new hardware, it
had
crossed my mind that I might have defective RAM also :-( but didn't know
how to check it. I did manage to get WEFT to install perfectly right
after
a first boot (not a reboot) but haven't altered Windows' memory handling.
I've checked out all Noel's suggestions except for the corrupted swap
file,
which I can't believe has happened after only a couple weeks of use! I
keep all my Temp folders emptied and use Diskeeper to defrag. I reset
the
SysRes cache at 1095 MB (it was either that or 200 MB--no setting in
between?) and its size is 604 MB, 2550 files, 5 folders. I've still got
59.9 GB of free space on C.

Thanks muchly for your time and info and the link to DocMemory. I'll
post
back with the results.

calamity carol





"Mart" wrote in message
...
Hi Carol, good to see that you've managed to replace and set-up your new
Samsung HDD.

Your 'sound' and OE problems *may or may not* have something to do with
your
RAM issues, but until you sort the RAM out, don't try troubleshooting
too
many things at once - it'll only lead to confusion g

FWIW - my 'guess' is that the underlying cause of your sound card
problems
is more likely to be driver related - but see previous paragraph. If the
card is 'pre-WinMe' you may well have problems finding the 'perfect'
WinMe
drivers and have to put-up with the WDM (Windows Driver Model) versions
supplied on the WinMe CD (or even Win98 drivers) and live with their
short-comings. Not many manufacturers were interested in writing WinMe
drivers for their obsolete sound cards - Cynical? Moi??

However, you say that you have only 512 MB fitted, so the Q253912
article
should not be relevant - it only applies to memory greater than 512 MB.

If you think that your memory *may be* faulty, check out your memory
chips
using Simmtester's DocMemory from www.simmtester.com or
http://www.simmtester.com/page/products/doc/docinfo.asp and create the
boot
disk from that - run it overnight to check the RAM.

One other possibility is that you *may not* be letting Windows manage
your
swap-file. Confirm that there are no min/max limits set by the User. Let
Windows manage it. Don't forget to defrag too g But I seem to recall
Noel
giving you some pointers in this direction last November.

Regarding WEFT, I've no knowledge of this 'application' so I can't
really
help you with it. However, you should try to confirm that it is expected
to
run with a minimum of 512 MB from
the 'minimum requirements' product specification. Again, see your
previous
threads for pointers from Noel and Mike etc.

In view of the date of the original thread - August thru' December last
year - and especially with the change of HDD and a 'clean' installation
since then, it might be a good idea to start a brand new thread/topic.
Keep
to a single issue per topic and don't forget to include error reports.

HTH and good luck

Mart


"caroloyl" wrote in message
...
Hi there!

I'm back up and running :-)) Installed and formatted the new Samsung
drive
myself December 30 and am still slowly installing my programs.

My sound problem with OE and other programs didn't go away--not with
either
the new drive or fresh Me and sound-driver install--so I've ordered a
new
sound card. The sound has been doing other peculiar things for ages,
like
playing a midi in two different keys at once and "wobbling" (nope,
don't
have reverb)--so I'm guessing it's used up after less than three years
(the
life span of cheap?)

But I'm really writing for help again with the subject line here
because
I'm
still getting the "not enough memory . . ." error. I got that warning
three
times trying to install WEFT (MS' embedded-font making tool) before it
finally completed. Never had that happen before and I've used WEFT
for
years--so I did a little looking around in the MS database and found
this
item referring to having this problem with large amounts of RAM
installed
(I
have 512 MB):

http://support.microsoft.com/support.../Q253/9/12.asp

It offers two fixes of which--to me--this one, editing the Sys ini
file,
looks easiest since I haven't a clue what the other's about:

http://support.microsoft.com/kb/108079/EN-US/

I've looked at my sys ini and there is nothing at all entered under
the
[VCache] section. Can specifying a maximum amount for Windows to use
help
me? And if so how much should I allow it? I read somewhere recently
that
if unlimited Windows will glom all the available RAM leaving no room
for
opening another platform (have I remembered that right?)--and I do
believe
WEFT uses a different one for installation (coarse fonts in the
dialog).
I've also just found an "out of memory" error in a Java log after
trying
unsuccessfully to download an applet (installed the latest Sun Java
program
a few days ago).

Your help, as always, much appreciated.

carol




A couple of things to mention:
"caroloyl" wrote in message news:...
Thanks for the reassurance guys--I needed that . . . and for your
time
assessing this matter. I'm sure hoping this will be the end of the
line
for
my string of problems--and I'm consoled to find once again Millennium
is
not
to blame.

carol



"Mart" wrote in message
...
Noel wrote:-

The fact that the utility would not complete is almost certainly
sufficient evidence that there are physical problems with the HD.
... etc., etc., ..

I totally concur with your comments, Noel.

For whatever cause - heat, mechanical, surface, etc., - Carol has a
(terminally) 'sick disk'

Mart

Hi HL, I was very pleased that you used the word "often", rather than
"always". I need not expand, save to say that I don't anticipate having any
more trouble scaring the birds away whilst I still have my 'upgraded'
Philips CDD3610 generic burner. g

Mart



"Heirloom" wrote in message
...
... I once had a spanking new Creative CDRW that
never wrote me but three CD's that could be read:
I threw out over a dozen failures
It should be mentioned that upgrading the "firmware" will often resolve
burning issues, aside from suitable media. Firmware upgrades can be had
at the manufacturer's website. Myself and a friend have determined this
can make the difference between burning a good CD/DVD and making coasters.
Heirloom, old and think it's gonna rain

"Mart" wrote in message
...
Hi Carol, I await to hear the results of your DocMemory tests with
interest, although I'm no longer particularly suspecting RAM issues.

Regarding Diskeeper, like WEFT, I don't use it so can't comment (although
several other 'regulars' on these WinMe News Groups do and report good
results), I prefer to use Scandisk (and Defrag) as supplied by MS. My
philosophy being that as MS 'invented' Windows, then their own
maintenance utilities *ought* be adequate. My experience of certain Third
Party utilities is "disappointment" - e.g. Norton (I've never touched
their products since the mid 90's when they progressed?? from DOS to
Windows and the 10ft bargepole took on a whole new meaning g) I tend to
use almost exclusively (except AV utils) MS utilities and am still here
to tell the tale.

As I mentioned previously, 'older' soundcards do not sit too comfortably
with WinMe and what a surprise that you mentioned Creative g. Forget
using their 'bundled' (Win95/98) application software on WinMe - it won't
install properly, if at all. Uninstall it (and the drivers - in Safe
Mode) and just re-install their (Win98?) drivers ONLY during the reboot
(Plug 'n Play)

Don't expect any of the original fancy gimmicks (which you might have
experienced in Win95/98) and you *might* just find that your .mid files
sound reasonably good.

... I once had a spanking new Creative CDRW that
never wrote me but three CD's that could be read:
I threw out over a dozen failures

CD-R's & CD-RW's? - Can often depend on the different 'quality' between
manufactures - try a different brand. And sadly, this has also been known
to apply to different brands of CD-ROM's and perhaps even more
importantly, between different software houses and their versions of
burning software. Not all CD-ROM's are recognised by all versions of
software, nor media by the CD-ROM - a slight blurring of science, (black)
art and moving goal posts.

Mart



"caroloyl" wrote in message
...
Hi Mart :-))

So glad you found me--had a hard time finding my post myself! I clicked
"New Message" to send in my news but I guess I should have used a fresh
subject line? I can't figure how these newsgroup threads work :-b

Anyway, I've tried two different drivers for my sound card--the one on
CD
that came with it, and another I got from the Creative web site.
Neither
made any difference in the way it performed. At one point before I
replaced
the HD, the properties sheet for the sound card told me I was not
authorized
to make any changes! (it's allowing them now though). In view of the
card's
gradual performance decay and recently developed blue-screening of a
variety
of programs (which always happens after a series of rapid ticks, clicks,
beeps or midi plays--never after just the occasional noise), I'll be
very
happy to have a new one. I once had a spanking new Creative CDRW that
never
wrote me but three CD's that could be read: I threw out over a dozen
failures and lost my temper too '-) ; so in all, my experience with that
brand of computer products has been VERY NOT satisfactory.

After having more than my fair share of problems with new hardware, it
had
crossed my mind that I might have defective RAM also :-( but didn't
know
how to check it. I did manage to get WEFT to install perfectly right
after
a first boot (not a reboot) but haven't altered Windows' memory
handling.
I've checked out all Noel's suggestions except for the corrupted swap
file,
which I can't believe has happened after only a couple weeks of use! I
keep all my Temp folders emptied and use Diskeeper to defrag. I reset
the
SysRes cache at 1095 MB (it was either that or 200 MB--no setting in
between?) and its size is 604 MB, 2550 files, 5 folders. I've still got
59.9 GB of free space on C.

Thanks muchly for your time and info and the link to DocMemory. I'll
post
back with the results.

calamity carol





"Mart" wrote in message
...
Hi Carol, good to see that you've managed to replace and set-up your
new
Samsung HDD.

Your 'sound' and OE problems *may or may not* have something to do with
your
RAM issues, but until you sort the RAM out, don't try troubleshooting
too
many things at once - it'll only lead to confusion g

FWIW - my 'guess' is that the underlying cause of your sound card
problems
is more likely to be driver related - but see previous paragraph. If
the
card is 'pre-WinMe' you may well have problems finding the 'perfect'
WinMe
drivers and have to put-up with the WDM (Windows Driver Model) versions
supplied on the WinMe CD (or even Win98 drivers) and live with their
short-comings. Not many manufacturers were interested in writing WinMe
drivers for their obsolete sound cards - Cynical? Moi??

However, you say that you have only 512 MB fitted, so the Q253912
article
should not be relevant - it only applies to memory greater than 512 MB.

If you think that your memory *may be* faulty, check out your memory
chips
using Simmtester's DocMemory from www.simmtester.com or
http://www.simmtester.com/page/products/doc/docinfo.asp and create the
boot
disk from that - run it overnight to check the RAM.

One other possibility is that you *may not* be letting Windows manage
your
swap-file. Confirm that there are no min/max limits set by the User.
Let
Windows manage it. Don't forget to defrag too g But I seem to recall
Noel
giving you some pointers in this direction last November.

Regarding WEFT, I've no knowledge of this 'application' so I can't
really
help you with it. However, you should try to confirm that it is
expected
to
run with a minimum of 512 MB from
the 'minimum requirements' product specification. Again, see your
previous
threads for pointers from Noel and Mike etc.

In view of the date of the original thread - August thru' December last
year - and especially with the change of HDD and a 'clean' installation
since then, it might be a good idea to start a brand new thread/topic.
Keep
to a single issue per topic and don't forget to include error reports.

HTH and good luck

Mart


"caroloyl" wrote in message
...
Hi there!

I'm back up and running :-)) Installed and formatted the new Samsung
drive
myself December 30 and am still slowly installing my programs.

My sound problem with OE and other programs didn't go away--not with
either
the new drive or fresh Me and sound-driver install--so I've ordered a
new
sound card. The sound has been doing other peculiar things for ages,
like
playing a midi in two different keys at once and "wobbling" (nope,
don't
have reverb)--so I'm guessing it's used up after less than three
years
(the
life span of cheap?)

But I'm really writing for help again with the subject line here
because
I'm
still getting the "not enough memory . . ." error. I got that
warning
three
times trying to install WEFT (MS' embedded-font making tool) before
it
finally completed. Never had that happen before and I've used WEFT
for
years--so I did a little looking around in the MS database and found
this
item referring to having this problem with large amounts of RAM
installed
(I
have 512 MB):

http://support.microsoft.com/support.../Q253/9/12.asp

It offers two fixes of which--to me--this one, editing the Sys ini
file,
looks easiest since I haven't a clue what the other's about:

http://support.microsoft.com/kb/108079/EN-US/

I've looked at my sys ini and there is nothing at all entered under
the
[VCache] section. Can specifying a maximum amount for Windows to use
help
me? And if so how much should I allow it? I read somewhere recently
that
if unlimited Windows will glom all the available RAM leaving no room
for
opening another platform (have I remembered that right?)--and I do
believe
WEFT uses a different one for installation (coarse fonts in the
dialog).
I've also just found an "out of memory" error in a Java log after
trying
unsuccessfully to download an applet (installed the latest Sun Java
program
a few days ago).

Your help, as always, much appreciated.

carol




A couple of things to mention:
"caroloyl" wrote in message news:...
Thanks for the reassurance guys--I needed that . . . and for your
time
assessing this matter. I'm sure hoping this will be the end of the
line
for
my string of problems--and I'm consoled to find once again
Millennium
is
not
to blame.

carol



"Mart" wrote in message
...
Noel wrote:-

The fact that the utility would not complete is almost certainly
sufficient evidence that there are physical problems with the
HD.
... etc., etc., ..

I totally concur with your comments, Noel.

For whatever cause - heat, mechanical, surface, etc., - Carol has
a
(terminally) 'sick disk'

Mart