Failure To Unpin From Taskbar, Related To Diablo 3?
May 16, 2012
i recently installed diablo 3, and in the process of installing i somehow managed to pin a shortcut to my taskbar. this shortcut says "Battle.net Account Management". the shortcut works, and is actually a link to the battle.net login screen. HOWEVER... i cannot right click or drag on the icon to try and remove it. i can drag it along the taskbar, but thats all. its a small problem but for one as OCD as myself its extrememly unnerving. i found a related thread in support, but it was for the diablo 3 beta.
I just bought a new HP laptop. They've included some items in the task bar for Windows Live and HP Utilities. I've selected unpin, but the tiled/group items are still there. I individually selected and clicked the x to delete and the they were removed, but the group icon is still present and I can't get ride of it
Is it possible to unpin a program on your taskbar and turn it into a shortcut on the desktop or anywhere else? Or should I say; can I move a shortcut out of a pin to another location? In previous operating systems I could just drag a shortcut almost anywhere you wanted.
I have several internal card readers for my desktop computer. Two are Rosewill brand from NewEgg and one is RocketFish from BestBuy. They are all of the type that read SDHC, CF and a host of other cards and also have a USB port for a flash drive. They all connect to main board dual-port headers.For no reason apparent to me, the card readers still read USB flash drives but do not even acknowledge any flash memory cards at all in any manner. It is as though I did not insert one at all. I researched the 'net and found some things to try (registry edits, scanning for malware, disconnecting the power cord for several hours, etc.etc.); but, after several hours of troubleshooting, I decided I had three bad card readers. In a last act of desperation, I restored the OS to an Acronis image I made several months back and now the card readers function flawlessly,So, where in Windows 7 can I begin to look for a cause/solution to this kind of problem if it happens again? It probably will happen again as I already have an XP system where the problem has popped up with these same card readers.Additional Info: I have an external reader that functioned fine on the same systems on which the internal readers did not work.
i'm trying to run an older game called Daiblo 2 Lord of Destruction. The game seemed to install fine, but every time I try to play it it gives me a Critical Error 22 (Something involing the directdraw). I can't see what's wrong because I just formated and installed my windows 7 ultimate 64bit and updated it before even intstalling the game. Anyone want to shed some light on this matter?
When ever i play Diablo or any other game it runs smoothly for about 30 minutes and the monitor shuts off and theres no sound but the computer is still on. I bought my computer a few months ago so i dont know what the problem is. Here are my specs.
OS Version: Microsoft Windows 7 Home Premium, Service Pack 1, 64 bit
Processor: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz, Intel64 Family 6 Model 42 Stepping 7
I just got Diablo II and I just bought a new laptop and it is running Windows 7 64 bit and everything runs fine but the colors in the game are all messed up. Like rainbowy. I downloaded the latest patch as well.
I am trying to install Diablo 2 on my Windows 7 64bit system and I am getting an error at the end of the installation process that says: Setup was unable to create the following directory:C:Program Files (x86)Diablo IIsaveI have looked into this a lot and have been told to create the directory myself, How do I do this without it adding another Diablo II folder in the directory? Example: if i create C:Program Files (x86)Diablo IIsave, it will end up being: C:Program Files (x86)Diablo IIsaveDiablo II, Adding the Diablo II file folder at the end of the directory. It is still having the same error. Is this the correct way of installing?
I have had this problem ever since my dad built this computer and even he has no idea what has happened. I am not a computer genius but I came across the windows helps forum so now I am deciding to give it a try. This blue screen occurs most when I am playing games or when I am trying to rate my computer's assesment through the windows experience index sometimes it would say windows assesment tool has stopped responding in the middle of the test, but I think I have finally solved it through the clean boot method that windows has shown me. But the BSOD still happens and I do not know why.
I downloaded the Diablo 3 beta client from the official blizzard website yesterday and ever since I started installing it I was able to connect with my wireless but not access any sites whatsoever, (for some reason aim works). I have tried connecting on the same computer with a wired connection and that works and tried using my wireless on another computer and that works.When I try going to any sites in google chrome or try the windows troubleshooter they both give me a DNS error message.So far I have tried:
Game worked fine for the beta and even for a week or two after launch. Randomly (not on a patch day), the game started crashing. Now it crashes after 2 or 3 minutes in the game almost every time. I've followed all the regular troubleshooting steps (see Battle.net thread here). At first I didn't see any error logs, but the Action Center came up today with a bunch of errors looking like this. I included the recommended error files, the dump files from the error in the above screenshot, and the perfmon report.
randomly get the following exception while playing Diablo 31) KMODE_EXCEPTION_NOT_HANDLED2) IRQL_NOT_LESS_OR_EQUALIs Windows 7 . . .- Windows 7 64 ?- Windows 7- Full Retail- What is the age of system (hardware)?2~3 years- What is the age of OS installation (have you re-installed the OS?)
When I try to run D2 in fullscreen I get a UE. However, when I run in windowed mode it runs just fine. Not sure why this is, but it works for me.If you want to run D2 in windowed mode you have to right click your Diablo 2 shortcut, go to properties, and in the "Target:" field you should see something like "C:Program Files (x86)Diablo IIDiablo II.exe" Just add -w to the end of that (after the quotes and with a space between) so it looks like "C:Program Files (x86)Diablo IIDiablo II.exe" -w
I have the hard copy of Lord of Destruction but I decided it best to download it from blizzard.net (or battle.net, i'm not sure, it's irrelevant) because I thought it might run more smoothly on Windows 7 Home Premium 64. For whatever reason though, it won't run in full screen mode. The game has an inch or so of black bars on the left and right side of it. They appear from the intro (the Blizzard logo), to the main menu and into game play?
I've been getting a BSOD with the 0x000000124 STOP code while playing D3. It's not very frequent, maybe once or twice in a 4 hours span. It's happened after long periods of playing and after very short periods.
Windows 7 . . . - x64 - the original installed OS on the system? YES - OEM - What is the age of system (hardware)? ~1 year old - What is the age of OS installation ~1 year old
In the last few days I have started getting BSOD's When playing games, The two mentioned in the title specifically. They will run OK for around 5/10 mins then BSOD. The only change I have made to the system in this time that i can think of is updating my ATI driver, But I did that after this started happening.
My PC is Windows 7 OEM Home premium Intel Core i7 920 ATI 6970 6GB RAM.
Every 3 hours i get one big BSOD only when i play this game. I also play the game from a laptop and its working very well on it.Found earlier here on the forum Driver Update and FixCleaner and bought them. I thought it will find the problem...but it didnt?
Just got a question regarding D2 - LOD expansion. Here's what happened, I downloaded the game, installed the game. All good then I mounted the Expansion image via Daemon Tools, had no success. It's not accepting / won't run the image and gave me an error. I got freaked out. System froze and there's nothing that I can do aside from pressing the "reset" button. Is my OS compatible to the game? I got a broken file on my OS (OS issues) or the image itself is corrupted?
Currently I'm building a server for a client who wants to run several copies of Diablo 3 on multiple Virtual Machines.Further, they also need the ability to use a hardware unity function.
After launcing the game my Windows crashes all the programs and windows ( volume control ) that are related to sound as i try to edit or change anything ( change volume etc ). And i hear no sound from anything, only after i restart the computer ( i then hear "ssssss" noise instead of nothing ).
I recently build a new Sandy Bridge computer to replace an older Conroe system. The new build retained the SSD (OS and programs) drive and the SATA data drives along with the existing Windows 7/64HP installation.I built an Asus P8Z68V Pro with an Intel i5-2500k and DDR3-1333 ram (12GB). I did not reinstall Windows 7/64HP. I had to tweak a few programs that had an issue with my substitute hardware, but otherwise it seems to run fine.However, I've had some crazy BSODs that seem to tie into grmnusb.sys. Yesterday I had 3 BSODs in a row that would happen as soon as I plugged in my Garmin Edge 305. The first happened while I was OCed. I rebooted and changed to default BIOS settings. Another BSOD when I reconnected the 305. So I uninstalled the Garmin USB driver and rebooted. Another BSOD when I connected the 305.I finally just left the Edge 305 connected and rebooted the computer and it came up ok and let me access the data on the device in a normal manner. And yet on the same system, I've had a number of times I've plugged the Garmin device in with no issues at all.When I first built the box (a couple of weeks ago) I had a BSOD from the Edge 305 connection, again with the gmnusb.sys tie-in. I rebooted, uninstalled the affected usb driver and all was ok for a time. And then the Garmin didn't want to connect so I re-installed the Garmin usb driver and all was well for a time.. and then, here we go again.Before I go though the routine of uploading the BSOD jcgriff zip files, I want to see if this is a known issue related to Z68 boards, or perhaps because I didn't re-install Windows 7 for the new hardware or if it's because computers just don't like me for some reason.
