Archive for the 'tech support' Category

Blinking Dash: The Video

Saturday, February 23rd, 2008

I still have no solution to this problem. Will Sheldon had some useful suggestions for me yesterday, but messing around with boot.ini did not do anything. The /sos option did not display anything. I also tried stuff like /safeboot, /safeboot:minimal, /basevideo and etc. It seems that the problem happens before NT loader even gets to parse the ini file soo none of these instructions really do much.

Ben on the other hand seems to think it might be a power supply problem. It could be but I have full access to the hard drive when I boot off the CD. It just doesn’t boot. As far as I can tell my problem is somewhat unique. I have yet to find someone having exactly the same problem. There are a lot of documented issues out there that are somewhat similar (ie share the blinking dash thing) but most actually make sense and are some sort of easily solvable driver problems.

Either way, I figured out that I take a vid of what is happening so that you guys can see the what is this thing all about. This was taken at approximately 3am in a dark room with my Nikon Coolpix S50 so sorry for the quality. Also, don’t mind the mess on my desk.

The computer usually doesn’t sit on the floor like that. It’s actually tucked in the nifty little “computer shelf” of my desk but I moved it out when I was ripping out all the USB cables from the back hoping this will fix the issue.

And yes, that is a Think Geek binary clock on top of the monitor. mrgreen

I wiped the drive clean and reinstalled Windows on it today. My machine boots once again. I already transfered my firefox profile from the backup drive so I’m 80% back to normal. Now I will need to slowly install all the little pieces of software that I will need. I’ll probably keep it light this time - this is bound to happen again. I just wonder when - I got 2 months out of it last time around. Let’s see how long can I go this time…

Blinking Dash: The Sequel

Friday, February 22nd, 2008

Remember that one time (at band camp) that my computer wouldn’t fucking start, because it was busing blinking a little tiny dash in the upper left corner of the screen? That was the end of December (just before Christmas). You might remember me struggling to find a reasonable solution and finally giving up and re-formating the drive and reinstalling windows.

So I have been running with a fresh Windows for close to 2 months now. Yesterday (actually, technically today at 3am) I rebooted the machine and it never came back up. All I see is that damned blinking dash. And once again I haven’t the faintest clue as to what is really causing this issue. This is really irritating, because now I know it’s not just some random glitch. It happened twice already, and it will probably happen again.

Btw, as far as I can tell, the data on the HD is fine - or at least it was last time. It just wouldn’t boot. I know this is not a corrupted MBR because running FIXBOOT and FIXMBR tools did absolutely nothing last time. Neither did installing windows on the same partition without actually formating the drive which means it is not a Windws problem either.

Could it be software related? It’s possible but it kinda seems unlikely at this point. I have no clue what could have caused it. Last time the machine bricked itself while applying Windows Media Player update. This time around it was rebooting to update McAfee. Then again, I don’t reboot that machine often - it runs continuously for weeks on end. The only time it reboots is when the software forces it too. I haven’t checked the uptime before it went down yesterday but I think it has been running for at least a week. I installed several apps in the last 2 weeks - Bitpim, MS Visual Studio, Flickr Uplodr, ActiveState Perl and some CPAN modules and probably few more things. It could have been any of these.

Or perhaps it is some insidious virus or trojan that went undetected. Perhaps it is sitting there camouflaged in one of my data files, just waiting to pounce and fuck up my boot sequence. It’s possible, but you’d think that a 2 month old piece of mallware would get snagged by the on access scanner made by any mainstream AV provider, no matter how shitty or bloated their software is.

I’m beginning to suspect this might be something like Ben described in one of the previous threads - a perfectly good hard drive with few faulty sectors in the boot area. But then again I ran the quick built in DELL IDE drive diagnostics and they passed. Of course it’s possible that these things gloss over this type of things and wouldn’t notice it. But this is a relatively new drive - I think it only has like a year or so. The data drive is much older, and it is working perfectly fine. Of course that one never was a bootable drive but still.

Perhaps it’s because I have 2 drives sitting virtually on top of each other in the cramped Dell case and the heat and vibration is doing it’s damage over time? I just don’t know. I’m at a loss here. Perhaps this is a sign from above that it is really about time to invest in a new gaming machine…

Those pesky PDF files

Friday, February 8th, 2008

At some point in the past we sent out an email to the staff saying that we can assist them with file conversion services. Very often they get large data files (agings, inventory, sales receipts) in various formats. Some are plain text, some are comma/tab delimited ASCII but most are PDF. Using tools like Monarch we can relatively easily extract the data locked inside the PDF files and convert it to just about any format. The one requested most often is of course Excel.

To this day we regret not wording that email a little bit better. We still have to explain to people how this conversion process really works.

For example one guy found out that we can convert PDF files to excel from a co-worker. It just happened that he had some large, tab delimited text files that he wanted to manipulate in excel. So he came up with a brilliant plan:

  1. He printed out what came out to be close to a 60 pages of data
  2. He then scanned them in as PDF files
  3. Naturally he was scanning them one page at a time since he didn’t know better
  4. The copy machine sent the ~60 scanned PDF’s to him, one page per email
  5. He then took the time to download all these files, save them, rename and reorder them
  6. Finally he zipped the 60 PDF files and emailed them to me asking if I could convert them to excel

I didn’t know this story. I’m recounting it to you now because it’s silly but at the time all I knew was that I got 60 PDF files all of which essentially contained scanned images. I really didn’t know whether I should laugh or cry. I decided to call him up and find out what the deal was. When he recounted this process to me I had to take a break to bang my head against the wall for 5 minutes. Afterwards I called him back and explained to him how to open the tab delimited file in Excel and then click next 2 or 3 times and watch the built-in import feature does the magic.

Sigh… At least he didn’t photograph the pages on a wooden table.

Another lady was doing test counts one day. She painstakingly recorded the values of the counts using the old fashioned pen and paper method. Normally she would have to re-enter all this data into some XML file but fortunately she remembered that email we sent out. So she scanned in all these hand written notes into a PDF file and then sent them to me for conversion. It took me a while to explain to her that I didn’t really have tools to do this type of OCR. She just kept saying “But they are PDF files!”.

I don’t think she ever got it, but she eventually gave up trying to convince me to convert them. She probably figured I was lazy or something. P

There seems to be something about PDF files that makes the small minded people very confused. We had another guy who kept sending word documents to the office to be “scanned in as PDF”. The secretary would then print them out, walk across the hall to the copy room, scan the printout, type in her email on the copy machine’s touch screen, go back to her desk, wait for the email, and forward it back to this guy.

They were both floored when I introduced them to PDFCreator. They absolutely loved it but it introduced a brand new problem. The Word guy would now create a document, generate a PDF and then realize he had few typos and/or mistakes in it. Fortunately he remembered we had full version of Adobe Acrobat (the one that can do touch-ups on PDF files) in the office. So he would now send us his newly converted PDF file along with the list of corrections.

I called him up and our conversation basically went like this:

Him
“Can you remove the fourth and sixth sentence in the third paragraph? This should make the whole document fit on 2 pages.”.
Me:
“Well, you see… The Adobe tool is mostly for touching up text objects. It doesn’t really re-flow the paragraphs. Btw, how do you know it will cut down the size to 2 pages?”
Him
“Oh, I did it in my word document so I can see how it will look when you do these changes.”
Me:
“Um… Wouldn’t it be easier if you just used PDFCreator to generate another PDF file out of this updated Word document?”

[long pause]

Him
“Sigh… I just thought it would be easier with the adobe thing”

I don’t know what is it about the PDF files. These folks seem to be doing ok working with Word and Excel files. But PDF files seem to have some sort of extra magical properties that induce confusion in some people.

Blnking Dash Problem: The Non-Solution

Friday, December 28th, 2007

I figured I should probably post my solution to the blinking dash problem. As you may know, few days ago I rebooted my machine only to be greeted a blank screen and a blinking dash in the upper left corner of the screen. This was happening right after the BIOS memory tests. The system was booting just fine from the CD and so I was able to back everything up.

I tried just about everything to get my windows installation bootable, including running FIXMBR from the recovery console, repairing windows installation, doing parallel install and etc. Nothing worked.

I’m glad to report that I finally got this machine up and running. My solution?

Format the hard drive and reinstall windows.

Yup, sorry that’s the only thing that helped. I tried, and tried to find a better way to do this but there was just no way this machine would cooperate with me. The interesting question is: what caused this? Was it the graphics card as Alphast suggested in the other thread? I kinda doubt it since the installation went so smoothly after I reformatted. Was it a hard drive issue? It would be odd since this was a relatively new HD. I got it in July when my old system drive failed on me. Could it be the HD controller? But if so, how come my second drive is working just fine?

I hope this was just some random fluke…

As a side note, I noticed that it only took me few minutes to get the machine to the point of usability after I finished installing the drivers and AV suite. Here is the list of apps I really needed to function:

  1. Firefox
  2. Vim
  3. WinRar
  4. VLC
  5. uTorrent

That’s about all I needed to feel at home. In fact I don’t really “need” VLC and uTorrent right away, but I installed them for a good measure. I will probably need MS Office on here sooner or later, but for now I’m fine. I hardly use that damn thing anyway. I will probably end up installing MikTex and Emacs first. P

I guess this is an evidence that I do live in the browser more than I think. Once I copied my Firefox profile from the backup drive, I was ready to pick up things where I left few days ago. Btw, does your browser let you completely save the current state (including all the open tabs in the current session) by simply copying a folder? This is why I love Firefox so much - all my plugins, bookmarks, custom adblock filters and greasemonkey scripts fit nicely in just few KB - and that’s just about everything I need for my daily browsing and blogging. )

What are the crucial apps that you install after a clean install?

Infinite Loop BSOD (nv4_disp)

Friday, December 28th, 2007

I love easily solvable problems. I call them instant hero issues - you can solve them in 5 minutes flat, and you instantly become a hero. I wish my problem that I was struggling with for the last two days was this easy to fix. A guy dropped off a desktop at my desk yesterday with a BSOD on boot. I looked at the message and it said (and I’m paraphrasing here) that nv4_disp caused an infinite loop.

I love infinite loops - they are awesome. Whenever I cause one, I sit back and say “behold mortals, for I have created infinity”. Of course I can usually kill my own infinite loops. Ones that occur during the windows boot process are not nearly as much fun. So I decided to track down nv4_disp which turned out to be an Nvidia display driver. Thanks Nvida!

Solution was trivial:

  1. Boot windows into Safe Mode with Networking
  2. Go to Nvidia website and nab brand new set of drivers for the GeForce FX 5200
  3. Install the drivers
  4. Reboot
  5. ???
  6. Profit (INSTANT HERO BONUS +30)

Apparently this problem is caused by the well known “NVidia Sucks Ass” issue with the GeForce drivers. Hopefully this won’t happen again - the drivers are up-to-date now, and the machine seems to be fully functional. But you never know. At least I should be able to easily fix it next time if this thing comes back.

I know, I know - a half witted monkey with a full frontal lobotomy could probably fix this. Sigh… I wish my users were as smart as monkeys with full frontal lobotomy. But you know what, sometimes it’s nice to solve an easy problem for a change. Cause, really these are the only types of problems that can give you this sort of instant gratification. Putting a check in the win column now and then, and actually helping someone gives us the energy to plug away on those hopless projects that have no real solutions - only workarounds an mega-hacks. It’s nice to have someone actually thank you for resolving a problem rather than trying to explain to them you not secretly the infrastructure and crashing the servers just to have something to do. ;P