I suggest you post the first six Error Reports from the System log for
the current boot, if necessary reboot, so that we can see how problems
develop. All reports record the date and time. Most Reports should be
Information Reports and you can ignore these.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 31/05/2008
Time: 01:40:42
User: N/A
Computer: PC0939
Description:
The Application Management service terminated with the following error:
The specified module could not be found.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

You can dispense with the part of the Report corresponding to /
beginning with "For more information". The link only works on the
machine where the Error was generated. You can see further details after
the link but the information is not intelligble to us mere mortals.

What happens if you connect an old style wired conventional keyboard U
(used normally with a desktop)? Does it work without error?

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



truevirgo61 wrote:
> Im using on screen keyboard, thats why Im able to space. Still using
> same laptop.
>
> Green LED lights on either F10 or F11 when I use fn key, that never
> used to be.
> Keyboard is clean. Somebody says that I might have turned on a kb
> mode. He doubted that it was Word, but he asked me about the LED when
> I mentioned I thought the problem might have something to do with
> Word or Bios.
>
> "Olórin" wrote:
>
>>
>> "truevirgo61" <truevirgo61@discussions.microsoft.com> wrote in
>> message news:BDF60646-483B-47F6-8787-B716DDC98855@microsoft.com...
>>> Correction, I see in my first post I said this week in regards to
>>> blue screen, I meant to say the previous week. Also, the on screen
>>> keypad works
>>> fine, all keys are functioning normally.
>>>
>>> "truevirgo61" wrote:
>>>
>>>> Hey Gerry, I would really love to send you that info, but there is
>>>> just way
>>>> too much of it. I can tell you this, the majority, if not all the
>>>> errors are
>>>> from the source Service Control Manager. Theres heaps of them.
>>>>
>>>> There is also SidebySide (lots) and many SNMP too, not to mention
>>>> some RemoteAcess warnings too. I didn' t know that my remote
>>>> access was on.
>>>>
>>>> Most of the Service Control Manager staff either has N/A or
>>>> system as user.
>>>>
>>>> RemoteAccess user N/A, a fewTcpip warnings dating back to last
>>>> week-User is
>>>> n/a.
>>>> Theres a lot mate. Too much to send. Should I be looking for
>>>> anything in
>>>> particular?
>>>>
>>>> Olorin,
>>>>
>>>> Nothing was spilled on the laptop. The blue screen mentioned BIOS
>>>> issue, something about turning it off, that maybe something was
>>>> corrupted, a file or
>>>> software I downloaded. That problem occurred regularly, but then
>>>> stopped. I
>>>> didnt see a blue screen the entire week before my keyboard
>>>> malfunctioned.
>>>>
>>>> I appreciate the help guys.
>>
>> What was the MS Word connection?
>>
>> Things I'd try:
>> - turning laptop upside down and shaking to see if paperclips, food
>> crumbs, illegal immigrants etc fall out
>> - try seeing if keyboard part is fairly easily lifted up and out
>> (check with laptop handbook/PDF) and check connections (but not if
>> this would void any warranty)
>> - open Device Manager (Start > Run > devmgmt.msc); if keyboard has a
>> separate entry, right-click and Uninstall it, then reboot and let it
>> be re-discovered.
>>
>> Did you do or try anything that seemed to stop the blue screens? If
>> you get any more blue screens, be sure to write down the messages
>> this time: "...mentioned BIOS issue, something about turning it off,
>> that maybe something was corrupted..." isn't really precise enough
>> to give us a direction to look in! And see if any of the Event Logs
>> has any relevant entries relating to the time when you *were*
>> getting these blue screens regularly, if they go back far enough.
>>
>> Are you posting from a different machine than to the other group,
>> where--you--had--to--type--like--this, or has your spacebar started
>> working now?