TOTD
-
Also, on other BIOSes, you can usually set how the power button works.
Glenn Dawson wrote: Also, on other BIOSes, you can usually set how the power button works Man. I want one of those :-D
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
-
Paul Watson wrote: I have a lengthy Stored Procedure open (and unsaved) So what's the longest stored procedure you have written Paul. Mine is sitting at 1308 lines, I left a nice disclaimer at the top to any individual who considered modifying it. ;P The shorter the better as far as I can see. -Nick Parker
Nick Parker wrote: Mine is sitting at 1308 lines Wow. No I am not that hardcore :) This one was only 149 lines. I am not a DBA or anything like that, so it is hectic for me. Though this one was the first time I got to use recursion in a SP. Boy does it suck in comparison to recursion in something like C#, even VB beats it. I cannot wait for Yukon so that I can use C# to code SPs. That will be a beautiful day. Nick Parker wrote: The shorter the better as far as I can see Amen. 90% of my stored procs. are just INSERT and UPDATE statements really.
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
-
i never use end task... i use end process which seems to work more indiscriminantly (spelled right?)... just kills the f*ing thing
Roman Nurik
Roman Nurik wrote: never use end task... i use end process which seems to work more indiscriminantly (spelled right?)... just kills the f*ing thing I could not even get Task Manager up to get to the Processes tab. The best I could do was click the Close Window button of Notepad and wait for it to bring up the End Task dialog (which took awhile.) You are right though. End Process is normally better, though I bitch when it tells me "You cannot end that process blah blah" :)
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
-
Paul - NEXT time, before you open all these processes, install wrkill from the NT resources kit .. its better than the Task Manager for killing things like Notepad, except, it doesnt do it 'nicely' .. it kills 'em good and proper without asking questions hth, Garth
Garth J Lancaster wrote: install wrkill from the NT resources kit .. its better than the Task Manager for killing things like Notepad, except, it doesnt do it 'nicely' .. it kills 'em good and proper without asking questions Cool, thanks for the tip. As Gary said up above: "I want it to assasinate the offending process"
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
-
Ouch! Will it respond well enough to switch to a different task, Explorer.exe perhaps? "Please don't put cigarette butts in the urinal. It makes them soggy and hard to light" - Sign in a Bullhead City, AZ Restroom
Roger Wright wrote: Will it respond well enough to switch to a different task, Explorer.exe perhaps? Naah nothing. Even the Cap and Numlock light test was a bit fickle. And as per usual after it managed to kill Notepad, Windows still decided to keep all the resources in some loop of space time. Had to reboot to get it all back. One day someone needs to explain to me how an ended process can smack my resources into another unusable dimension.
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
-
I have a lengthy Stored Procedure open (and unsaved) plus two half written emails and a couple ASPX pages open in VS.NET that need to be saved. Now you know why some of us are in the habit of pressing Ctrl-S so often...
"Pretending to guide me, you led me astray, And I don't want to fall into your kind of ways." "Melt", Front 242
Daniel Ferguson wrote: Now you know why some of us are in the habit of pressing Ctrl-S so often... But things were going so well! Haven't had a problem with WXP for so long that I started to trust it*. "Oh WXP can handle this, no need to save that stuff" :-D :rolleyes: * That is were I made my fatal mistake, right? :laugh:
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
-
Paul Watson wrote: I have a lengthy Stored Procedure open (and unsaved) plus two half written emails and a couple ASPX pages open in VS.NET that need to be saved Should teach you to do one thing at a time. sorry - but you know the saying - um... how do you say that in english: "Wer den Schaden hat, braucht für den Spott nicht zu sorgen"? All thumbs for your machine being idely twiddely happy to await your commands in the morning...
Italian is a beautiful language. amare means to love, and amara bitter.
sighist | Agile Programming | doxygenpeterchen wrote: Should teach you to do one thing at a time You only do one thing at a time? No ways I can limit myself to one thing at a time, even if I wanted to. Boss on IM, sending bug sheets via email, writing a SP for someone, code reviewing someones code in VS.NET, double checking it against an opened specification document in Word, CP etc. etc. etc. :rolleyes:
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
-
I have a lengthy Stored Procedure open (and unsaved) plus two half written emails and a couple ASPX pages open in VS.NET that need to be saved. Now you know why some of us are in the habit of pressing Ctrl-S so often...
"Pretending to guide me, you led me astray, And I don't want to fall into your kind of ways." "Melt", Front 242
I wouldn't press it too often. I used to work with someone that (out of habit) used to press CTRL-S three or four times in quick succession. This backfired on him since the app (I think it was VB6) didn't lock the file and it had two (or more) threads write to the same file at the same time. The next time he tried to open that file he realized it was corrupt. :wtf: Important lesson: save often, but not too often. :-D
-
Tip of the day: It is pretty stupid trying to open a 256 megabyte file with Notepad, even though it has an extension of TMP. What is even more stupid though is End Tasking that straining Notepad. I don't know what End Task was trying to do (dump the contents of the 256meg file?) but it just farked my machine back to the stone age (writing from another machine right now. My machine is sitting there doing something, has been for the last 20 minutes...) Night all!
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
-
Wow, thanks. Hey, I have admin rights on a co-workers machine..... :evil grin: :-D
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
-
Paul - NEXT time, before you open all these processes, install wrkill from the NT resources kit .. its better than the Task Manager for killing things like Notepad, except, it doesnt do it 'nicely' .. it kills 'em good and proper without asking questions hth, Garth
Another good one is 'pskill' from System Internals. It doesn't ask questions or tell you 'access denied' or anything. You can quite easily kill off system processes, though I would not recommend it... ;P
Bruce Duncan, CP#9088, CPUA 0xA1EE, Sonork 100.10030
Blackadder: Baldrick, have you no idea what irony is?
Baldrick: Yeah, it's like goldy and bronzy only it's made of iron. -
Errr, most 'off' buttons still work, at least with Phoenix BIOS motherboards. If you hold the power switch down long enough (3 seconds or so), the BIOS will shut the machine off regardless of how confused/hosed/sc***wed-up the O/S is. And yes, I know what you mean about Task Manager. It apparently tries to talk all nicey-nice to applications first, whereas I want it to assasinate the offending process. No mercy!
Software Zen:
delete this;pskill it!!! Die Kill Maim Destroy it! pskill is one of the most useful tools that I use. None of this nice talky happy stuff! And they still ran faster and faster and faster, till they all just melted away, and there was nothing left but a great big pool of melted butter "I ask candidates to create an object model of a chicken." -Bruce Eckel
-
Daniel Ferguson wrote: Now you know why some of us are in the habit of pressing Ctrl-S so often... But things were going so well! Haven't had a problem with WXP for so long that I started to trust it*. "Oh WXP can handle this, no need to save that stuff" :-D :rolleyes: * That is were I made my fatal mistake, right? :laugh:
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
* That is were I made my fatal mistake, right? Hehe ... yep. Actualy XP is pretty good. Usually you can End Task an offending process and continue, but I still like to press ctrl-s periodically to make sure.
"Pretending to guide me, you led me astray, And I don't want to fall into your kind of ways." "Melt", Front 242
-
I wouldn't press it too often. I used to work with someone that (out of habit) used to press CTRL-S three or four times in quick succession. This backfired on him since the app (I think it was VB6) didn't lock the file and it had two (or more) threads write to the same file at the same time. The next time he tried to open that file he realized it was corrupt. :wtf: Important lesson: save often, but not too often. :-D
_(I think it was VB6) _Hmmm.. a there's lesson here too. ;)
"Pretending to guide me, you led me astray, And I don't want to fall into your kind of ways." "Melt", Front 242__
-
Roger Wright wrote: Will it respond well enough to switch to a different task, Explorer.exe perhaps? Naah nothing. Even the Cap and Numlock light test was a bit fickle. And as per usual after it managed to kill Notepad, Windows still decided to keep all the resources in some loop of space time. Had to reboot to get it all back. One day someone needs to explain to me how an ended process can smack my resources into another unusable dimension.
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
Paul Watson wrote: One day someone needs to explain to me how an ended process can smack my resources into another unusable dimension. I'd like to understand that myself. I know there are two Win32 API calls that kill processes - one is polite about it, the other rude. I wrote a little routine once that used them to kill errant processes on a WinNT4 server. I called the polite one and waited for a bit, then if it failed I called the rude one... something akin to giving last call, then throwing the bums out at closing time. But I have no idea which one is used by Task Manager. My guess is that it's the rude one, which shuts down the process whether it wants to shut down or not, and as a result the offending process doesn't do any cleanup or closing of opened resources. It's ugly, but sometimes there's no other way to kill a program, and many don't implement any kind of trap for the polite shutdown method. Glad to see you back to normal - were you able to save that stored procedure? "Please don't put cigarette butts in the urinal. It makes them soggy and hard to light" - Sign in a Bullhead City, AZ Restroom
-
Paul Watson wrote: One day someone needs to explain to me how an ended process can smack my resources into another unusable dimension. I'd like to understand that myself. I know there are two Win32 API calls that kill processes - one is polite about it, the other rude. I wrote a little routine once that used them to kill errant processes on a WinNT4 server. I called the polite one and waited for a bit, then if it failed I called the rude one... something akin to giving last call, then throwing the bums out at closing time. But I have no idea which one is used by Task Manager. My guess is that it's the rude one, which shuts down the process whether it wants to shut down or not, and as a result the offending process doesn't do any cleanup or closing of opened resources. It's ugly, but sometimes there's no other way to kill a program, and many don't implement any kind of trap for the polite shutdown method. Glad to see you back to normal - were you able to save that stored procedure? "Please don't put cigarette butts in the urinal. It makes them soggy and hard to light" - Sign in a Bullhead City, AZ Restroom
Roger Wright wrote: Glad to see you back to normal - were you able to save that stored procedure? Yes thanks, after about 20 minutes of churning it finished whatever it was doing and I could start using the PC again. I saved everything and rebooted as half my reources were in that aforementioned dimension.
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
-
_(I think it was VB6) _Hmmm.. a there's lesson here too. ;)
"Pretending to guide me, you led me astray, And I don't want to fall into your kind of ways." "Melt", Front 242__
Daniel Ferguson wrote: Hmmm.. a there's lesson here too. exactly what I was thinking. :-) Regardz Colin J Davies
Sonork ID 100.9197:Colin
I'm guessing the concept of a 2 hour movie showing two guys eating a meal and talking struck them as 'foreign' Rob Manderson wrote:
-
Roman Nurik wrote: never use end task... i use end process which seems to work more indiscriminantly (spelled right?)... just kills the f*ing thing I could not even get Task Manager up to get to the Processes tab. The best I could do was click the Close Window button of Notepad and wait for it to bring up the End Task dialog (which took awhile.) You are right though. End Process is normally better, though I bitch when it tells me "You cannot end that process blah blah" :)
Paul Watson
Bluegrass
Cape Town, South AfricaMacbeth muttered: I am in blood / Stepped in so far, that should I wade no more, / Returning were as tedious as go o'er DavidW wrote: You are totally mad. Nice.
I downloaded a great tool called "EnableDebugPrivAndRun.exe" from the March 98 MSJ -- running Task manager through that will let you assasinate all the processes you like. ;) (But be careful, certain processes have post-assasination agreements in effect that could mess things up enough that a power-off is the only way out.) John :D