BeepApp??

[MilesAhead]

Hmmmmmmm had my Vista64 system 2 days and I see this program BeepApp.exe that I have in my autokiller program. Something keeps trying to launch it. It's in
C:\Windows\SysWOW64\BeepApp.exe

The only thing I see in the registry is in MuiCache.

It keeps coming up though and my autokill has to keep killing it.

Google only has a few references with nobody knowing what's up.

 

[Airbot]

Did you see this? This guy says its from AMD RAID/AHCI RaidXpert program and Asus. or google chrome? Pretty much the most I can find on it as well.
Arrrgghhhh! at Lemon Soju : Tokyo : Japan

 

[MilesAhead]

Thanks for that. I was getting really paranoid. I have RaidXpert so I guess it's cool. I don't understand why something like that keeps launching when you kill it though. I already have enough to do setting up new system.

 

[MilesAhead]

Whoops. Never mind.

(thought I was posting to another forum.. mod can please delete)

 

[Airbot]

Yeah, it may be something pretty important, hence the persistance. Or just an annoying process, I don't know. LOL But you seem to have that connection so maybe it's safe. You could check the process and see how high it's usage is. May not be very much at all.

 

[MilesAhead]

Thing is I've never had a system with Raid before so I'm being cautious. From the descriptions I've read it seems like the RaidXpert thing is for sysadmins to configure user systems Raid settings over the network. I just hesitate to kill the thing off without being sure.

I guess if I kill it and the disk doesn't access then a power cycle should bail me out. I hate it when they just stick stuff on systems without giving a clue. I guess they must have thought this stuff would be on business machines.. but the curve is moving these high performance machines out now where Joe Sixpack buys 'em.


If you go on the AMD site you get almost nothing about it except for a bunch of sales copy and how OEMs can configure the stuff. Not very helpful to the guy who owns the single PC.

 

[Airbot]

What are you going to do, you know. :huh:

 

[MilesAhead]

What are you going to do, you know. :huh:

I stopped the service, set it to manual, and killed the RaidXpert.exe. Everything still works. I have the feeling the "BeepApp" was probably a beacon so that the remote configuration can home in on it or something. Yet another thing that shouldn't be running by default unless you were setting up a business network.

More bloatware.

 

[MilesAhead]

Looks like it connects to your own machine via localhost to configure your Raid setup. So the same mechanism can be accessed remotely. Yet another "office" thing that's bleeding through to home PCs.

 

[Airbot]

LOL, did you ever see how much usage the process was using?

 

[MilesAhead]

LOL, did you ever see how much usage the process was using?

No but I did read a horror story on the web where a guy tried to tune his system with the thing. He spent the next 9 hours reinstalling because the disk was so slow it took that long to do an install.

Looks like if you just stop the service and set it to manual it doesn't kick off the client.
I hate annoying software like that. Like when you're trying to read some docs on a web page and some stupid popup blocks the mouse to ask you if you want to take a survey about how great the site is to use. Like, really well-designed code.

 

[Airbot]

Well, I guess you'll see if it affects anything from now on having it set to manual. Maybe, maybe not.

 

[MilesAhead]

Well, I guess you'll see if it affects anything from now on having it set to manual. Maybe, maybe not.

Just sitting there using memory doesn't help anything. Plus why would somebody who hasn't studied Raid yet(like me) want to try to tune the thing? It's suicide waiting to happen.