Click to See Complete Forum and Search --> : fujitsu stylistic


fnction22
March 19th, 2005, 07:42 PM
Hey folks I was wondering if anyone could help, here is the deal I have this Fujitsu Tablet pc that had a Win. 2000 pro os installed and I was trying to upgrade it to xp pro. i did the upgrade without deleting partition just the upgrade and now when it turns on it starts to load the startup proggies and shuts down with a blue screen and tells me to check the drivers bios etc... problem is I don't have a keyboard attached ( oh and the touch screen doesn't respond?) So I don't know how to get it into safe mode to try the drivers:eek2:

Any help from you pros out there would be greatly appreciated

fnction22

Sorry if it's in the wrong section I just saw Notebook and posted:rolleyes::rolleyes:

Update: I located the driver that was shutting it down as the on screen mouse (pen) and downloaded a new driver , and it Shut down again anyone know what driver to use
Its a Fujitsu Stylistic

confus-ed
March 20th, 2005, 04:55 AM
Which 'stylistic' ? .. there's a few !

fnction22
March 20th, 2005, 11:33 AM
Thanks for answering confus-ed , It is a Stylistic ST... But anyho I got the pen driver to work by disableing a com Port that was conflicting (sharing resources). Now a new Question Any way to correct that resource conflict ? There does not seems to be any new drivers on the Fujitsu Website for the com port.

Thanks
Fnction22

confus-ed
March 21st, 2005, 01:41 AM
..Now a new Question Any way to correct that resource conflict ? There does not seems to be any new drivers on the Fujitsu Website for the com port...

There's still a load of stylistic st's ! :D (its a series) -so what I'll say off the top of my head (without particularly looking or thinking about it ;)) is to look for bios updates or things called 'chipset patches' relating to xp ..

By changing the operating system you may have caused this resource conflict yourself, w2k will have a driver for a com port for sure (they are a 'standard' device) - whats causing you problems isn't one particular driver, but how your O/S is attempting to 'arbitrate' on how resources (IRQs & memory ranges) get shared out or shre those resources between themselves - I'd however add if you don't actually intend to use the com port & its not seemingly causing any more problem than being off, then just leave it as it is ? ;)

fnction22
March 23rd, 2005, 06:33 PM
Thanks confus-ed that is exactly what I ended up doing, By the way sorry for the very delayed post .
And again thanks for your reply :smile:

fnction22

confus-ed
March 24th, 2005, 03:32 AM
Most welcome :) .. not that I did much, other than confirm what you'd already figured out would work ;)