ZoneLab down, full-disk msg, DiskDoctor no go !


HOME ยป Hardware

'evening everyone,

Long time since my last post, I've been good and kept machine tidy with DaniWeb recommended tools. Daily and weekly updates and manual and auto scans with AdAware, Spyware Blaster, AVG, Spybot, Panda, all of them..outcome allways "0", PC has been cleaner than baby's fresh dipers.

I noticed above average decline in speed and overall performance lately, machine has been literally dragging itself through web, icons and frames diyplaying one by one sometimes. Days ago I got the firts warning about full-disk. Cleaned the excess and gained some 400MB. Next day the same story, cleaned another 200MB of apps, only having to repeat that two more times, with not mu


Related to : ZoneLab down, full-disk msg, DiskDoctor no go !
Disk Not Initialized Msg. Meaning Of ?
Hardware
Hello,
Trying to get an old external HD working.
Msg. that come up is that the Disk is not initialized.
Gives me the option of doing so.
What does not initialized mean, exactly, please ?
If I do, as the option suggests, will this wipe out everything on the HD, such as a re-format would do ?
Thanks,
Bob
Cloned disk results in msg "This copy of windows is not genuine"
Hardware
Hi,
I have a two-week old, custom built desktop with a genuine OEM version of Windows 7, operating Office 2010. The 'system' sits on an internal SSD and all my documents and files sit on a separate internal disk. One aspect of my backup and recovery strategy is to create a clone of both disks using Norton Ghost 15. These clone disks sit in one drawer each of my PC and can be easily removed and stored for emergency purposes. The idea is that if my PC is ever stolen etc., I have duplicate disks that I can use in a to-be-purchased PC, which will allow me to get back on board quickly. I have been using this strategy for years with my prior computer running XP (only one internal disk
Log engine does not show full msg body.watto do???
Hardware
hey, i have a problem.......
I want to write the content and other deatails of all incoming and outgoing msgs in a file. i am using the [B]Log Engine [/B]for this pupose.
But the problem is the Log engine does not contain the full msg body. So, i cant display full msg body using log engine. I gotta use the MTMs for the same.
There id something like an ID field in the Log engine which identifies each entry in the Log engine.
My question is, can i use this id to read the corresponding msg body using MTMs?
ZoneLab down, full-disk msg, DiskDoctor no go !
Hardware

'evening everyone,

Long time since my last post, I've been good and kept machine tidy with DaniWeb recommended tools. Daily and weekly updates and manual and auto scans with AdAware, Spyware Blaster, AVG, Spybot, Panda, all of them..outcome allways "0", PC has been cleaner than baby's fresh dipers.

I noticed above average decline in speed and overall performance lately, machine has been literally dragging itself through web, icons and frames diyplaying one by one sometimes. Days ago I got the firts warning about full-disk. Cleaned the excess and gained some 400MB. Next day the same story, cleaned another 200MB of apps, only having to repeat that two more times, with not mu

[ubuntu] Computer Crashed-Now will not Boot (full error msg below)
Hardware
I have a rebuilt compaq laptop. I installed ubuntu about a month ago and it worked fine until the other day.
Message below is what I get when I go to "edit" at the screen where it allows me to choose which version of Ubuntu to run (I get other errors when selecting any version listed....so I'm doing one thing at a time here.)
"recordfail
insmod part-msdos
insmod ext2
set root=' (hd0,msdos1)'
search --no-floppy --fs-uuid --set b5a79df1 -0fd3-4431-81ac-3898fe436/f37
linux /boot/vmlinuz-2.6.35-24-generic root=UUID=b5a79df1-0fd3-4431-8/1ac-3898fe436f37 ro quiet splash
initrd /boot/initrd.img-2.6.35-24-generic"
Can't get rid of disk error msg on boot
Hardware
When I boot Ubuntu (10.04) I get an error message at the Ubuntu splash screen telling me there are disk errors on /boot (/dev/sda1) and /home (/dev/sda7). I'm ask to enter "F" to fix, "C" to continue and so forth. I always hit "F" and the drives are then checked and Ubuntu continues to boot normally. However, when I boot the system the next time, I get the same error message on the same drives. This is been going on for a couple of weeks now.
Today, I booted into recovery mode and dropped to a root terminal where I ran "fsck -f -v -c" on both drives but fsck didn't appear to discover any errors. When I rebooted into regular mode, I go

HD Wallpapers
3D
3D Abstract
City
Celebrities
Indian Celebrities
Cars
Travel
Girls
Animals Birds
Movies
Sports
Black White
Nature
Planes
Anime
Food Drink
Dreamy Fantasy
Architecture
Games
Space
Holidays
Flowers
Love
Artistic
Baby
Beach
Bikes Motorcycles
Macro
Computers
Vector
Funny
Army
Textures
Brands
Misc
Music
Other
Privacy Policy - Copyrights Notice - Feedback - Report Violation - RSS 2017 © bighow.org All Rights Reserved .