Double Boot with Das Keyboard?

[watduzhkstand4]

I'm asking this for my friend.
I've looked through other threads about the DAS keyboard but didn't seem to find anything on it.
When he turns on his computer, his Das pro won't be recognized but once he restarts, everything is back to normal.
Does anyone know what the problem is here?

Thanks in advance!

[watduzhkstand4]

USB recognition issues.  Happened all the time to me.  RMA'd board.  Same with second board.

so there is no way to fix it? =(

[Manyak]

Is this only in Windows or in BIOS as well?

If it's in BIOS as well it's an easy fix. Reset CMOS and make sure you reenable legacy USB afterwards.

In case that somehow doesn't work, try setting "PnP OS" to "No". Or even update the BIOS completely.

[Manyak]

Worth a try.  Didn't help this guy.

I thought Legacy only turns on Bios level support. The OS should pick up the board on it's own.

It's a little more complicated than that. Ever try running DOS or Win95 with a USB keyboard and legacy disabled? Won't happen!

Traditionally and with PS/2 keyboards, keystrokes generate a hardware level interrupt (on IRQ1). This puts a keystroke into the BIOS's keyboard buffer. The OS can then retrieve keystrokes from it using the BIOS interrupt handler INT16h (a software interrupt).

With legacy support enabled, BIOS will, in a sense, translate USB keyboards into PS/2 keyboards by directing keystrokes to that keyboard buffer and letting software access it through INT16h like it would with a PS/2 board. With it disabled, the OS is left to use it's own code for everything and just gets the data over USB like with any other device.

I'm not 100% sure about the method Windows uses with it enabled since it has two choices (though I'm leaning towards it ignoring the BIOS buffer), but if it's having trouble detecting a USB keyboard there's a good chance that you can at least reroute the keystrokes through BIOS instead.

[Rajagra]

Is this only in Windows or in BIOS as well?

If it's in BIOS as well it's an easy fix. Reset CMOS and make sure you reenable legacy USB afterwards.

I'm not sure that will work with the DAS because the keyboard connects indirectly via its own internal USB hub. If the hub doesn't initialise you don't get to see the keyboard. That may partly explain the double boot issue.

[ch_123]

so there is no way to fix it? =(

Actually, there's a simple five-step guide -

1) RMA the board
2) Get refund
3) Buy a Filco
4)
5) Profit!

[watduzhkstand4]

Is this only in Windows or in BIOS as well?

If it's in BIOS as well it's an easy fix. Reset CMOS and make sure you reenable legacy USB afterwards.

In case that somehow doesn't work, try setting "PnP OS" to "No". Or even update the BIOS completely.

It works in bios, just not windows.
Do you guys think it's because the computer is just recognizing something of a higher priority (i.e. graphic tablet) and not booting the port next to it being the one that is connected with the Das?

Actually, there's a simple five-step guide -

1) RMA the board
2) Get refund
3) Buy a Filco
4)
5) Profit!

My friend got it as a birthday present and he loves it =)

[ch_123]

Which, the Filco or the Das?

Btw - is the problem specific to his computer? Have you tried it on another one?

[itlnstln]

I like USB hubs.  They come in very handy, and if they are integrated with a monitor or keyboard, even better.  One less box on your desk.

[itlnstln]

The Extreme Makeover team couldn't help that setup.

[GreeN]

Just find a landscape picture of Johansson to set as your background and you won't even notice the rest

[watduzhkstand4]

Thanks for all the help guys. My friend got lucky and he found out that a different arrangement in his setup will get the board to boot. =)

Good point.  Would clean up my setup.

Show Image

Well, maybe not.

Who cares about the mess? Just the keyboard that we care about =D
BTW is that the Filco with blue or brown?

EDIT:
Also, just a quick question. What speakers are those? My speakers just blew out after a thunderstorm! I need a new set. Got any recommendations you guys?

[watduzhkstand4]

Hey, he got it to boot with the Das, yaah!

We'll see how long that lasts.


The Monitors are Mackie HR824's - way overkill but one of my former roommates was a Recording Engineer so I got spoiled.  I built the surrounds though - that's probably overkill too.  Frankly, any Goodwill amp with decent speakers will kill any Logitech setup.

They look really nice and I'm sure they sound nice. I was thinking of getting the m-audio studiophile av 40 just to start off. I don't know too much about monitors but I don't really need a sub because I can't listen to music loud anyways because someone is always sleeping in the house.

[megarat]

If you need to contact tech support, I believe this recognition issue is referred to as the "Das Boot" problem.

[keyb_gr]

I was thinking of getting the m-audio studiophile av 40 just to start off. I don't know too much about monitors but I don't really need a sub because I can't listen to music loud anyways because someone is always sleeping in the house.

Those AV40s seem to be pretty decent for what they are. Obviously you won't get any insane amounts of bass out of the 4" "woofers", but they do go reasonably low. (If in doubt one can always still place them close to the wall, as the bass reflex openings are on the back.) They'll certainly beat any regular desktop computer speakers hands down.

Alternatively, look into headphones. They usually give better sound quality when compared to speakers at the same price.

"Das Boot" problem - LOL...