COCKTAIL TUMBLR!!

The Blog of an (ex) Bartender Gone Terribly Wrong

By Krakie!! I've Done IT Again!!!

That’s “IT” as in “Information Technology”. I had a problem with a Canon iC D800 Printer installed on a network. It was one of those damned MS Windows errors: The instruction at “0x77f41d24” referenced memory at “0x00000000.” The memory could not be written.  (That’s the exact message, but the numbers are not exactly the same - so don’t anybody go crazy out there looking that up - an exact search in fourteen search engines for the right numbers came up with nothing anyway)

I worked on the problem for three hours and then I called Canon - twice. They told me to go to Microsoft’s site and said the answer might be there. I did. It wasn’t. I stayed with the XP Professional SP3 and the Canon iC D800 for five more hours until 10 pm and drove my 50 miles home. That weekend I remoted in and worked on it another five hours - and Canon said they would send me the “latest” drivers on disk. The next Thursday I got the disk and drove 50 miles out there again and worked on it again, opened the “latest” drivers disk plastic bag they sent me (not yet available on the web, they assured me) and it was dated 2004… which means that this printer has been on thousands or tens of thousands of XP computers for at least four years (and there have been people having this problem before and nobody ever found a solution to put in their database) - NOBODY at Canon could figure out how to solve this problem, and the same with Microsoft. After installation of the updated drivers - the original error message came back again! I had fixed it to the point where at least it had stopped giving me the error message and stopped crashing Explorer every time I tried to print - and now it was back to both again.

Well, fifty miles each way with my gas guzzling 15 miles per gallon van meant I’d already spent over 12 gallons of gas on this problem - eating into my contract - so, once again, I did it by myself. For a few hours I had thought that it must be that DEP was causing the problem. Only how to turn that sucker off??? Data Execution Prevention has no button or setting to turn it off! I checked around for a while though and came across a totally different problem on the web, having nothing to do with “the memory cannot be written” but it did have to do with turning off DEP which is what I wanted.

Ok - so how to turn off DEP: Go to the boot.ini file, right click it and take away the “read only” attribute so you can edit it. Open boot.ini with notepad and remove the word NO from NOexecute=optin.

Save and reboot and there will be no more DEP running, and your Canon iC D800 will print like a dream with no problems whatever.

What shitty coding. A printer crashing explorer because DEP won’t let it work, and nobody at Microsoft in four years of getting “Do you want to send this error message to Microsoft?” had a patch to fix it. What a shame - but now VISTA is upon us - thrust upon us - ready or not, with Microsoft ready to ream us   a - g - a - i - n !!!  Has anyone else wondered at how this planned obsolescence has made them filthy rich and not helped us one bit?  When I type my letters I still use the same 26 letter keyboard, same 0-9 numbers, and still use my fingers to type - so whoopdie doo what new features they include - it all comes out looking the same.

Comments on Above Topic(View)
blog comments powered by Disqus