Check your Power supply unit friend

 

No Avenger, wtf are you on about power on via USB allows the pc to wake up, my problem is that I can't shut the pc down when a USB lead is conected to my line 6 pod hd?
KidPix my MB has USB 2 and 3 (Asus Hd81) I'm using the USB 2 slots, I'm assuming as the line 6 pod is a few years old (pre USB 3) so it wouldn't be comparable.
Thanks tboth of you for your input

 

Surely the power supply on three separate computers can't be wrong......can they?

 

Sorry No Avenger, no offence meant. I've been trying to solve this problem with the line 6 POD HD, off and on for well over 5 years, it seemed to work fine on XP ,but to be honest I can't really remember back that far. I seem to have tried thousands of configurations but none seemed to work. Just recently I bought a Digitech RP360, and this seems to have the same problems, on a fresh windows 7 install that is. Any sugestion is a step in the right direction, I apologise most humbly for my curt reply.

 

Last edited: Nov 7, 2017

Maybe buy a small outlet switch to turn off the device without having to unplug it, if it is USB powered, they make a small USB hub with power switches.

 

Sorry, this won't help you, but did you ever consider the damn thing to be broken?

I've had some serious problems with my computer years ago. HDD wasn't recognized, mouse or keyboard didn't work from time to time, PC didn't come up at all and some other things. At the end it turned out it was a malfunctioning USB dongle. Dumped. Done.

 

Twoheart, it would seem strange that the line 6, when connected stopped the pc from shutting down. Also another unit, the digitech 360 gives the same effect, seems strange ... But could be a possibility highly unlikely though.

Tarkus.....what you deem to be a positive solution, none of the units are USB powered, but a swichable power outlet is the way.

 

Last edited: Nov 8, 2017

Spewing some more ideas... have you updated the motherboard's BIOS to the latest one? Do you have the latest chipset drivers?

I found something else that might help - changing the MPS 1.4 table to 1.1 in BIOS, if you have that option. btw. What's your motherboard?

Have you tried disabling the Power Management for USB Root Hub in Device Manager? Try unchecking the "Allow the computer to turn off the device to save power" in "Power Management" tab of the USB Root Hub. That's what I always do on my audio PCs, too. If they use USB audio interface, which is kinda rare in pro studios. [usually FireWire or Thunderbolt these days]

Great that you don't run an AV and it's not connected to the Internet. Much less problems to think about.

 

Last edited: Nov 7, 2017

True. Unlikely when it's two devices with the same effect. But...
Please check, if your device starts an APP (observe Taskmanager while plugin in device). It is possible that USB devices start a program, that may prevent a shutdown. Just a thought.

 

I think at this point, if it were me, I would start digging for more information such as looking in the shutdown logs...
A comparison of the logs from both a successful shutdown and a hung shutdown should help determine which process is hanging. Then you go from there depending on what you see. Much more straightforward than guesswork.

https://www.sevenforums.com/tutorials/160855-shut-down-view-details-last-shutdown-computer.html

 

It would make sense to verify first that the device is not broken. I would connect it to another machine and check if the effect is the same. If yes it's defective.

 

Soundwave, thanks for the reply, mobo is an Asus H81 plus, have tried turning off power management, to no avail. I use FireWire for the soundcard, focusrite pro 40. I use the pod and the digitech as guitar processors, connected via analogue audio leads and only use the USB side to run the editors, but being an older person, I have back problems and have difficulty getting into positions to edit the units manually. So an onscreen editor is a plus, but having to get down to undo USB leads is a bit of a pain, but not as bad as trying to edit stuff.

Twoheart, will try that tommorrow

Digitaldragon, what you say is excellent and the way to go, but I don't think I'm technically proficient enough to follow that. Ill try and digest it tomorrow,

Thanks all you guys for your help, its most appreciated.

 

And then they say Linux is difficult to use. Most of the time everything just works in Linux. You install it and it just works without having to install any drivers. You connect something and it works. You press shutdown and it goes off. In the case when something doesn't work like it's supposed to, solutions are easier than in Windows... just an observation. [and I use Debian 9 with MATE desktop, it could be completely different with some other distribution and desktop]

Anyway, I think we'll get to the bottom of it, sooner or later.

 

It's quite a time ago I used Unix/Linux/Xenix/OSX, so I'm not up to date.
Your observations are correct. The iX OSes are more stable and produce less errors. But why. Unix and it's derivates were first developed at universities and for scientists. The main purpose was producing a rock solid OS without bells and whistles. UI and ease of use wasn't the main goal and most of the time iX OSes are setup by professionals. In the 80ies setting up a Unix system was quite a heroic project for normal user. This changed with the years, but even today it's not as easy as to set up Windows for the normal computer dumbass.

In contrast, Windows was created to serve average people and office users. Also MS in the past tried to serve their customers for extreme long periods, so that you can use peripherals and old hardware for ages (this seems to be changing).
This is the attemt to create an One-For-All-And-Ever OS and this approch doesn't pay in terms of stability but in customer loyalty. This leads to an unparalelled coverage in software.

There is no better or worse OS, it depends.

 

You don't have to feel ashamed or bad, for that matter. Operating systems are very complex beasts these days and I always wonder how the hell do they manage to make them work at all.

Just imagine... Microsoft with a whole army of top-paid [notice top-paid, not top programmers LOL] programmers is unable to make a bugless OS and the more code there is, the more buggy it gets and more debugging is needed. That's why I'm so weary about the newer=better. Just look at the poor FXpansion suite of plugins, for example. Their Guru 1 is still more stable than anything else they've done. Waves 7 and 8 are more stable and work better than 9 and so on... Plus programmers are lazy beasts who like to program new features, but hate fixing bugs. Just imagine that?

This was an interesting bug hunt jefft! If you manage to make it work I'd really love to hear about it! I *really hate* unresolved issues! Sometimes I can't sleep when something is not working properly until I solve it.

 

I suppose it depends on how you like to work. To some it's easier to try hooking into different devices to guess which is the culprit. I prefer the substance of looking at logs and such, especially after trying the different PC, different hub, etc. approach. It's a lot easier to me, but that's me. It usually leads me right to the culprit.
If it's a service hanging, then it would be a software bug. If it's the Line6 software, it likely wouldn't get fixed (discontinued device), but he could stop the service with a batch prior to shutdown as per @No Avenger's post. It probably is the equipment, not being actually defective or anything, just poorly coded services or drivers which didn't play well with some update that occurred with Windows 7. Something in the driver or service which is hanging on shutdown.
Easiest non techie solution, rewire the Line 6 into some sort of switchable power, or put it on some kind of switchable hub.

 

I tend to think along terms that digitaldragon says that my problem is relating to a now obsolete line 6 product, I tried the batch that No Avenger suggested, with no luck. So as a compromise I'll Wire up the power to switchable sockets I tried a switchable hub, to no availe. What I can't understand is why the digitech has the same results, as it's a newer model.
I spent most of my life, fault finding on domestic goods ie Tv, video, hifi etc, at the component level, now sadly at the ripe age of 63, I tend to look for a quick workaround. As Signwave says coders are lazy they tend to create workarounds rather than find the source of the problem, something that's not really in my vocabulary. But this I'm afraid has me beat. Thanks for all your contributions, if I ever find an answer, I'll let you know.