Can anybody replicate this?

I'm using Screenshot Captor v2.82.01 - June 1st, 2010 on Vista Home Premium with a user account, UAC On.  I've hit what seems to be a weird bug.  SSC locks up when I use Shift-PrtScr = Grab selected Region.  I make a screenshot, SSC makes its capture sound, and the New Screenshot window (at least I think that's its title - the buttons on the title bar obscure it) pops up.  At that point, SSC locks up and I have to forcibly terminate it.  I didn't try scrolling region or repeat last, but all the other methods seem OK.  This behaviour mostly happens if Shift-PrtScr is the FIRST capture.  That is, if I tried other methods first, it usually, but not always, works as expected; sometimes it locks up even if I have tried another capture method first.  I think Red Box mode may have a problem?  Something like this happened with the beta, but I think earlier versions were OK.

-rjbull (June 04, 2010, 03:23 PM)

I'm experiencing a similar issue with v2.82.01 on Windows XP.  If I try a Ctrl+Shift+Print Screen and then use Ctrl+Click to capture, Screenshot Captor will lock up if I use the Pop Up Choice dialog.  I then have to Alt+Tab to the Pop Up Choice dialog and hit Esc to cancel.  If I use the Minimized mode it works fine.

While I can't comment on the specifics of what Dell may or may not have known internally, this was an INDUSTRY WIDE problem at the time.

Here is more info on DailyTech: http://www.dailytech.com/article.aspx?newsid=18921

I dealt with the GX270 model in the field, and in my experience Dell was quite good about the issue.  They preemptively replaced all of the GX270 motherboards at one site before they had the chance to fail.

All of the major PC manufacturers had their models with bad caps.  The HP equivalent was the D530.

The previous two companies I worked for used Dell exclusively for their PCs, laptops and monitors and I found them to be very reliable overall, including OptiPlex GX270 after a motherboard replacement.  I own a Studio XPS 16 laptop and have no problems with it.

My current job uses Lenovo and I haven't been very impressed with their reliability so far.  It makes me wish we had some Dell PCs here...

tomos,

Sorry for my late reply...I haven't checked this post too much lately.

From what you posted, everything is working fine.  The log file only logs what is output when CHKDSK Assist sends its command to cmd.exe.  If you need to reboot first (required if you are checking the drive with the Windows install on it) you will see exactly what you posted in the log file.  I should probably make this more clear, and will do so in the documentation in the next release.

I'll also look into pulling the info from the Event Viewer into the script itself or at least adding a link so you can get to it quickly.