Subject: | |
From: | |
Reply To: | |
Date: | Sun, 9 Dec 2007 12:40:30 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
I haven't seen that but what I do see with the last 2 versions of winamp,
and it's really annoying me is, when I exit winamp, AIM also exits. I'm
thinking when I have time I'll have to uninstall both and try to reinstall
since just reinstalling doesn't work. I tried that, but I have yet to see
the problem you're having. I'd say memory except you already said you have 2
GB, and that's more than enough for your setup. I know, I have the same
setup here except I'm running JFW but I'm sure it's not even a screen reader
issue. It almost sounds like winamp isn't too happy with something you have
installed on there.
----- Original Message -----
From: "Howard Kaufman" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Sunday, December 09, 2007 12:27 PM
Subject: off topic
> All of a sudden, I noticed that if I tried to play a file in winamp, it
> would tie up my computer for over a minute, until the file loaded and
> started playing. This only happens if I try to run winamp more than one
> time before rebooting my computer. I was using window-eyes, winamp 5.35,
> windows XP home, with 2 GB ram. I went back to winamp 5.13, and the
> problem
> is gone. Has anybody else seen this one?
>
|
|
|