The fact that it works in Safe Mode indicates that the
problem is caused by something that is loaded in Normal
Mode. I can see two options for you:

a) Use System Restore to fix the problem. This is a safe
method that is fully reversible.
b) Run msconfig.exe and disable the various tasks under
the Startup tab until you find the culprit. This will take
quite some time because you have to reboot the PC
many times.


"david carvalho" <davidcarvalho@discussions.microsoft.com> wrote in message
news:C377F739-D55E-4094-82FA-A39446DDC13C@microsoft.com...
> Hi !
> thanks for the reply.
> it worked on rescue mode, even that application (nasmIDE) that I was
> trying
> to run.
> i was avoiding to use system restore without knowing what caused this...
> This pc is used by 3 different groups during classes....
> Any ideas please ?
> Thanks
>
>
> "Pegasus (MVP)" wrote:
>
>>
>> "david carvalho" <davidcarvalho@discussions.microsoft.com> wrote in
>> message
>> news:32758AFD-5207-4B90-BD47-106F9A0D5282@microsoft.com...
>> > hi !
>> > This windows xp home edition installed on a lab. It is basically only
>> > used
>> > to run a assmbly compiler (NASM IDE).
>> > when running this editor, wich opens a ms-dos window like edit.com,
>> > nothing
>> > happens. the keyboard and mouse not respond on this window.
>> > Since this application runs on the environment like the edit.com,
>> > I've tested it too. Also, nothing happens with edit.com.
>> > I've recover the edit.com from cd installation using expand edit.co_
>> > but
>> > it's still the same. Any ideas of what's causing this ?
>> > thanks !
>> >
>>
>> Is this a recent problem? If so, use System Restore to fix it. If not
>> then try this:
>> - Reboot the machine in Safe Mode
>> - Click Start / Run / cmd {OK}
>> - Type this command ***verbatim***:
>> %SystemRoot%\System32\edit.com {Enter}
>> Report exactly what happens.
>>
>> By the way, MS-DOS is a legacy operating system that was
>> introduced some 30 years ago. It is rarely used these days and
>> it does not exist under Windows XP. The black screen you're
>> thinking of is probably the Command Prompt.
>>
>>
>>