the usb drivers that came with my unit work well with Win98, but XP does not recognize my player

I have searched FAQ and the net with no luck

where can I download new drivers?

THANKS

Yes, that's a known bug with the beta software. Instead, use ethernet. That works fine.

If you insist on using USB there is no solution yet. But the problem should be adressed in a future release.

doesnt recognize it via the ethernet either

using serial now -- UGH, new 2.2Gig P4 with 48x12x40 cd drive, yet thanks to XP all the time saved ripping is more than lost uploading to my player

thinking of loading an old version of win98

any other ideas?

mulitboot? You have to be good to make it work well

Try updating everything to Beta 11 (emplode and the player have to match), then try USB again, as USB problems often devlop if you plug in the player before you installed emplode, as it installs the wrong usb driver.

Ethernet should be pretty easy to get going. Make sure you've got a link light on both ends - if you don't, you may need a crossover cable. Once you know the link is good, try manually specifying IPs for both sides of the connection...

Don't even try uploading your music to the player over serial, it's just not worth it.

Matthew

Thanks, I have both beta 11s installed but I still get an error w the USB

Seems since I already made the mistake of plugging it in earlier it now has the wrong driver. How can I change the driver?

Thanks for all the help and SORRY for my continued questions

SORRY for my continued questions

Oh, yes, you're so dumb it's embarassing for the rest of us -- NOT!

Believe me, nobody is going to be upset about someone asking questions, and yours are not trivial. Probably half the people on this bbs are wondering about the same things you are and are just too intimidated or too lazy to write and ask them.

tanstaafl.

XP and the Empeg through USB are (for now) not a good combination. Chances are you won't be able to get it to work until an update of the beta software is available.

Instead, focus on getting your ethernet to work. Connect with serial and enter a fixed IP adress in emplode. Then try to re-connect to your empeg.
Before I had my router I also wasn't able to connect to my Empeg using DHCP. Now it works like a charm.
Also keep in mind that if you connect directly to a NIC, you'll need a crossover cable.

Strange.. I never had a problem with USB (other than it's speed, with 5 Gigs of music.. I's hate to be one of ya'll with 30-40!) Maybe I lucked out and installed everything in the right order, or somethin'. At the time, I didn't have Ethernet (thanks to a faulty cable in my house) but now I'm on that, and rockin'..

To CHANGE drivers, plug the Rio in so it's listed under Hardware Manager, in the USB section, (have the CD in already), right-click and Select "Change Driver" (may be "Upgrade Driver"), and browse the CD for it. (Sorry, not sure the exact location..)

Me.

XP and the Empeg through USB are (for now) not a good combination.

True... I mentioned this problem to my son Kenneth (the one marketing the "Delta V" board game) who is much better versed in the complexities of computers and operating systems than I am, and here is what he said:

My experiences with USB stacks.

The USB stack as originally implemented in drivers for third party
stand-alone cards for Win95, then in Microsoft's initial Win95 and Win98
implementations, was a very loosely written stack -- it would accept as
valid inputs material that was "out of spec". This got tightened up with
Win98, which many early USB devices couldn't work with, and then loosened
again with Win 98 SE. The USB stack in WindowsME is nearly identical to
Win98 SE's. This backwards compatability impacted system stability -- many
BSODs are caused by the USB driver flaking out.

When I was beta testing BeOS and its USB stack, Be's USB driver was written
tight to the specifications, and reasonably well documented in what was
required of third party drivers, and many of the USB devices extant at the
point in time where BeOS app and driver development was being pushed by Be
were so far "out of spec" that they would work unreliably, if at all, and
tweaking the USB stack to be friendlier to "commonly used" devices was
something that the dev mailing lists had religious arguments over, with one
faction saying "No, do it RIGHT" and the other saying "Make my
scanner/gizmo/whatever work".

Windows 2000, due to security and stability issues, has a very rigorous USB
driver built into the OS. As a result, a lot of older USB devices just
don't work well with it. This was fine, so far as Microsoft was concerned;
Win2K is meant for office and professional use, where there are IT managers
who presumably do research before buying things to add to systems.

Rumor has it that the reason WinME came out is because they couldn't make
"sloppy" USB work well at all on Win2K. Win2K was supposed to be "NT for
Aunt Minnie", which took a little longer to get working in a satisfactory
manner, and was released as WinXP. So they did WinME as, effectively,
"Windows 98 with everything" as a stopgap product.

WinXP, because it's USB 2.0 compatable, has to have a tight USB driver.
Which means many devices won't work with it...and worse yet, many devices
will work with it if they were later production runs.

FYI, for any of you who run programming or traffic at radio stations, there
is a program called Tune Tracker for BeOS. Been out and about for 3 years
now, just put out version 2.

Caveat: Dane Scott (programmer of Tune Tracker) is someone that I've worked
with in the past, and is the guy who first showed me BeOS (on a Pentium 166)
running 20 movies at once while rendering an openGL teapot. The experience
with BeOS is "Ooh. Cute." Followed by "Oh. My. God." Followed by ranting
and wailing at the heavens at the incredible injustice of the world that
none of the big software companies ever ported their apps to it.

There are, alas, good programming reasons why no major companies ever ported
their software to BeOS. It's not just a different development environment,
but the entire OS and API is pervasively multithreaded. Most programs are
written single thread mode -- opening a simple UI window runs two threads in
BeOS. So most of your programmers have to learn something different and
unfamiliar, and when things break, they do it from race conditions, which
are maddening to debug.

Here's the URL for Tunetracker.

http://www.beosradio.com/tunetracker/


tanstaafl.

Very informative post, thanks!

I think this would be a good time to ask the Empeg guys if they've had a chance to look more closely at the USB drivers on XP and if anything obvious has shown up?

Since emplode can connect to the Rio Central via USB, I would assume that this could be considered a higher priority than other car player work?

Has anybody tried the workaround of using the W2K USB stack and drivers with WinXP? People that have the Psion DAB Wavefinders also have really flakey XP drivers and that's what they've done to get around this problem.

I personally think it's a bad idea to do it but *shrug*

- Trevor