PC gurus please look at this problem

I don't really understand what you're asking. If you could re-word it and number your questions I could better help you.

~~Mad Mod Mike, pimpin' the world 1 rig at a time

joke deleted

Are you saying that every time you tell the system to shut down, it reboots?

If so, make sure you have ACPI (I think thats the accronym) enabled, and your power options set in the control panel.

I had the problem I think you have and I found the answer by googling

If it's something else, I agree with MMM, please speeel owt moar cleeerlee

Okay, so when you boot into Windows normally, if you select Start => Shutdown, it reboots the machine, and if you boot into Safe Mode, than you can shutdown normally? This may be a problem with APM/ACPI, what motherboard are you running and what version of WIN2K?

~~Mad Mod Mike, pimpin' the world 1 rig at a time

shutdown -s -m \COMP is better .

~~Mad Mod Mike, pimpin' the world 1 rig at a time

Thank you, actually I tried, it did not help. You know, I can shut it down if booted to safe mood. This is really strang. If there is a problem with ACPI, I should not shut down either in safe mode, right?

MSI 848, win2k professional w/ sp4

Okay, so when you boot into Windows normally, if you select Start => Shutdown, it reboots the machine, and if you boot into Safe Mode, than you can shutdown normally? This may be a problem with APM/ACPI, what motherboard are you running and what version of WIN2K?

~~Mad Mod Mike, pimpin' the world 1 rig at a time

I agree. Though if this was Windows 2000 Server, it would most definately be a ACPI problem, as Windows 2000 Pro uses APM and W2K Server uses ACPI IIRC. Make sure you have the latest BIOS and drivers installed, if all else fails, reformat.

~~Mad Mod Mike, pimpin' the world 1 rig at a time

shutdown -s -m COMP is better .

~~Mad Mod Mike, pimpin' the world 1 rig at a time

LOL



shutdown -hf 0; = better

Err..

su
password:

shutdown -h -t now

8O . o O (now?)

About the ACPI... perhaps it is disabled in the Bios?
I remember my system freaking out on shutdowns when it was disabled... or was I freaking out? <bah long time ago>

linux_o, dont u dare say a word.

I have the sameboard (in two machines) and had the same problem. One of the things I did was use a bootable linux (knoppix) in order to troubleshoot the mobo. The strange is that i was only having the problem with one board. I found that the one one that had your same problem didnt exist in linux for some reason . Even stranger is that when I swapped my PSU (from my one machine that did work Antec True) the problem resolved (strange).

From AMI BIOS, in Power Management Features, ACPI standly state: S1/POS; Power Management/ APM: Enabled. You know, I tried both enable it and disable it, all the same.

So, I think it has to be the difference between safe mode and normal. Could you guys know what is major difference driver loading between them. I know the VGA driver is not loaded, but I know it is not the reason. Thanks

Can you look inside your motherboards BIOS and write down all the settings it gives you for Power, APM, ACPI, or anything related to them?

~~Mad Mod Mike, pimpin' the world 1 rig at a time

I am looking at the manpage for shutdown and do not see a -s or -m flag anywhere. I have -atkrhznfFc listed as valid options. What are -m and -s for?

I was kidding :-D

This is the Linux shutdown:
[code:1:08f6261c2b]
/sbin/shutdown [-t sec] [-arkhncfF] time [warning-message]

/sbin/shutdown
Usage: shutdown [-akrhfnc] [-t secs] time [warning message]
-a: use /etc/shutdown.allow
-k: don't really shutdown, only warn.
-r: reboot after shutdown.
-h: halt after shutdown.
-f: do a 'fast' reboot (skip fsck).
-F: Force fsck on reboot.
-n: do not go through "init" but go down real fast.
-c: cancel a running shutdown.
-t secs: delay between warning and kill signal.
** the "time" argument is mandatory! (try "now") **

[/code:1:08f6261c2b]

And this is the Windoze shutdown:

[code:1:08f6261c2b]
Usage: shutdown [-i | -l | -s | -r | -a] [-f] [-m \computername] [-t xx] [-c "comment"] [-d up:xx:yy]


No args Display this message (same as -?)
-i Display GUI interface, must be the first option
-l Log off (cannot be used with -m option)
-s Shutdown the computer
-r Shutdown and restart the computer
-a Abort a system shutdown
-m \computername Remote computer to shutdown/restart/abort
-t xx Set timeout for shutdown to xx seconds
-c "comment" Shutdown comment (maximum of 127 characters)
-f Forces running applications to close without war
ning
-d [u][p]:xx:yy The reason code for the shutdown
u is the user code
p is a planned shutdown code
xx is the major reason code (positive integer less than 256)

yy is the minor reason code (positive integer less than 65536)

[/code:1:08f6261c2b]


I prefer the Linux / BSD / Unix one of course

Just a little more information. When I do shutdown -s in start =>run, it give me "now, it is safe to shut down". then I push the power button for a few seconds, shut it down. It looks like I am going back to win95 age. Really sad, really just curious, why it can do in safe mode, but not in normal. Strang!!!

Oh, I thought you were talking about the Linux shutdown command: /sbin/shutdown as you were talking to linux_0 and for some reason I think that he doesn't run Windows I didn't realize that you were talking about the Windows one or even that there *was* a Windows shutdown command.

So, any idea about the solution.

Now, after trying all these ways, I am more intending to think that my msi848p mb somehow conflicts with the win2k APM/ACPI driver, or with my PSU. And in safe mode, system does not load the driver, so it can do it. But, I still can not pursuade myself this is it. Again, it is so strange problem that I never heard.

When windows shows that it means it can't shutdown your PC by itself so it's either on crack and or your APM / ACPI is not working quite right.

LOL- that sounds just like one of my professors. (He actually got me introduced to Linux about two years ago.) But you know what? He is usually right.

Go into Device Manager,

View Devices by type

<Name of PC>
- Computer branch
-- <What does it list under the computer branch ?>

Can you uninstall that and reboot ?

Can you 'upgrade' it (advanced installation, not auto) to something else ?

Have you got APIC (vs PIC) enabled in the BIOS (View Devices by Type, and if there are only 16 IRQs listed it is PIC, if there are 24+ it is APIC).

Try uninstalling then rebooting.

Your computer isn't going to explode, and the auto re-install at next boot may fix it.

Failing that I'll recommend some chipset drivers from the Intel website. (Intel - assuming they manufactured your mainboard chipset, not CPU).

Also run a CHKDSK <drive letter:> /F on each of your drives (from the command prompt), as NTFS / MFT can do screwball things and cause shutdown problems from time to time.

A nice guy searched this for me: http://aumha.org/win5/a/shtdwnxp.htm

I think my problem is more likely from hardware campatibilty. It says some drivers may account. So, winxp upgrate may or may not help. But I have not lost all hope. Here I do a little test.

1. Since the safe mode is the key, ie, if in safe mode, shut-down is fine, no matter with or without network

2. So, I compare the system process between the normal and safe mode.

3. I found these three pieces are different between them, I guess they might be the reason. They are spoolsv.exe; regsvc.exe; mstask.exe, and another one is svchost.exe, which appeared several times with different PID value, but in safe mode, it only appeared once with PID value 380.

4. My questions are: any pc gurus can explain what these pieces for? Is there any way I can correct them if they were proved to be the reason, or how to prove them?

Actually, I tried to inactive them, the system won't allow me. I guess they are the core pieces, but they are the extra ones not needed for safe mode. Thanks

Thanks. So, in your case, the antec psu fixed the problem. Could you please tell me what kind of antec psu you got?

Well... this may seem to be a pain, but I suggest, you take all the expansion cards out, execpt the video card.

Then plug one card in at a time, boot into Win2k, install drivers if needed, shut down, install the next card.

Perhaps PnP could, or you could figure out a better way of balancing the IRQ for the devices.

Or you could see if it is another device is conflicting. That way you could eliminate if it is a driver causing the conflict.

So, just having the video and USB/Firewire card installed. Though, hard to say how many onboard stuff your running.

How many onboard peripherals (sound, network, USB 1.1? do you use printer port/coms?) are you using and have you tried disabling all of them, then pluging in the card to see if it shuts down properly?

Then just turn them on one by one, and take note of the IRQ's from the bios as it hands it out.

Integrated Sound, Lan and presumely supporting 8 USB 2.0 device, no printer and no parallel/com/game device. So, there actually are plenty of usb for use, and plus a 4-port usb hub. Anyway, the only thing i need from that pci card is its 1394 for transfer the vidoe.