|
So I've been bitching lately about BSODs and Microsoft and what have you. I have in the works a book about debugging problems. Chapter 1 is "Your assumptions are wrong."
I'm a big proponent of calling a turd a turd. Not to belittle anyone, but if you want to solve a problem you have to be honest. Own it. Your code is crap? Own it. you got lazy? own it. It's not personal it's reality. Part of that reality is admitting when you're an idiot.
I'm an idiot.  JSOP go away.
I have worked on a high end laptop for almost 5 years. It's had heat issues, random crashes (careful with drivers), high cpu at times etc. When I bought it, I purchased the minimum RAM because oems always jack up the upgrades on order. So I ordered 2 32 GB SODIMMs, popped them in and 4+ years later support told me they were incompatible. In fact, I have 32GB under my keyboard that I never knew about.
Correct memory on order, we'll see what happens. if you want a good laptop with NA first person support, check out Eluktronics.
Jeesh, read the manual.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
|
That is copywrited now. By me. 
so many issues go way too long because of assumptions.
Chapter 2: "It's not personal, you're wrong."
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
charlieg wrote: Chapter 2: "It's not personal, you're wrong."
This is the book that The World needs now!
|
|
|
|
|
charlieg wrote: if you want to solve a problem you have to be honest. Own it.
Absolutely! If you don't acknowledge your mistake, you can't prevent it happening next time. Everybody makes mistakes: the measure of a person (or a company) is how you deal with it.
But having said that ... in development, the hardest lesson I had to learn was "this is not going to work, throw it away". The urge to tinker with almost working code is ... considerable. It very hard to admit "this whole idea was a mistake" and go back to what you had before. Microsoft has never, ever learned this lesson, which colours every product they produce. 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
charlieg wrote: "Your assumptions are wrong."
I have to work with a credit card processor outfit whose track history is not very good. Recently I blamed them for something, turned out it was my code. Time to reset the prejudice, lol. Not all the way, mind you, but I do need to tone it down a bit, if only for the sake of not embarrassing myself!
And yes, I owned my mistake, apologizing to all involved.
|
|
|
|
|
At the risk of jinxing myself, my laptop has now been up for over 2 days with the correct and new memory. Helps to know your system.
Now, just out of curiosity, I'm sending the 4+ yo sticks back to Crucial for warranty replacement. Wish me luck.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
And I jinxed myself. 53 minutes after posting I have a UNEXPECTED_KERNEL_MODE_TRAP.
We'll see what the BSOD analyzers say. I smell driver issues or possibly a dying motherboard. I cannot suffer any more like this. I have way too much work to do.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
I Know an ISA Port when I see one!
|
|
|
|
|
What's an ISA port? I can't even recognize a SCSI port.
|
|
|
|
|
But do you know a EISA port when you see one -- and...
Do you remember when EISA was used in PS/2[^] (which is not a playstation 2 device made by Sony, but a computer made by IBM)?
|
|
|
|
|
ISA and EISA, sure, but not as ports, as connectors on the motherboard.
|
|
|
|
|
PIEBALDconsult wrote: but not as ports, as connectors on the motherboard
Yeah, I guess port isn't the exact best word.
Here are some wordnik defs which probably describe port as an ok choice:
noun A porthole.
noun Archaic A cover for a porthole.
noun An opening, as in a cylinder or valve face, for the passage of steam or fluid.
noun A hole in an armored vehicle or a fortified structure for viewing or for firing weapons.
noun An entrance to or exit from a data network.
noun A connection point for a peripheral device.
|
|
|
|
|
A "header" then.
FDD header, ISA header, EISA header.
A motherboard may have an internal "USB header", but rarely an internal USB port.
|
|
|
|
|
Yeah, header is probably better term. 
|
|
|
|
|
Isn't that the new docking ring on the ISS?
|
|
|
|
|
I know a Vintage Port when I drink one.
[Today's is 2007, sometimes you just have to take what life throws at you]
veni bibi saltavi
|
|
|
|
|
|
Any port in a storm....
(I seem to remember that gin was your poison)
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
|
Would it not be more accurate to say ISA socket / ISA card (depending to which you are referring)? What was that small one "only designed for modems" apparently that suddenly appeared on mobos?
|
|
|
|
|
It's due to the fact I took off the side and Newbe's saw it and went 'whats that?'...
|
|
|
|
|
I don't know where to post this as it's not a programming question as such, but more of a question about general interest of a certain little concept i cooked up.
Background: I built a thing that can run tokenization from inside a T-SQL database (and i'd support others but i want to try to use their builtin regexes if they have them, and that requires solving a math problem I can't solve yet - Ardens theorem or the state removal method of turning a state machine into a regex). In the future I'll support them efficiently.
anyway, point is, you can "type", validate and detect different types of fields in a text stream.
so what you can do with it is create "typed CSVs" you could submit to stored procedures to update a whole mess of data in one call, with validation and rejection of invalid CSVs.
The upshot is you don't need to grant a webserver access to your DB tables - just the stored procs - that becomes practical - at least in some situations - because you can update a whole CSV** worth of data at once.
**The CSV could only be as long as either NTEXT or NVARCHAR(MAX) but whatever.
I haven't performance tested it in MSSQL - yet. However, I stand by the general algorithm as over 3 times faster than the one the Microsoft .NET Regex engine uses though running it in a database is iffy performancewise. Still, I don't think it's bad enough to be unrealistic unless you need very rapid turnaround times on your updates.
Real programmers use butterflies
|
|
|
|
|
Not me. Better to do that on the client rather than the server.
|
|
|
|
|
How do you do it in the server without giving the server access to your tables, or perhaps using SQLXML diffgrams, which frankly i think is worse?
Answer me that.
PS: I've worked in more than one environment where direct access to DB tables is literally not allowed in production, but approved stored procs could be installed and run.
Real programmers use butterflies
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
