Mandrake Update kills Gcombust? (how to get a find a log of what changes were made?)
Hello all, last evening, I recalled that I had not run mandrake update in a while to get the latest security updates for my system. I did so and then proceeded to fire up Gcombust to burn some vacation pictures to CD.
Gcombust had worked nicely in the past (a few days ago), but when I ran it this time, my computer froze hard when the status window indicated that the burn was 4% done. The LEDs on my keyboard were flashing and gkrellm was no longer updating. Nothing to do but hard reboot, I guessed..
So now my system is a bit rogered, but I don't remember what all list of packages I downloaded/installed, so I have not even clue 1 as to where to begin trying to fix things. I have tried googling for rpmdrake logs and other things, but nothing seemed helpful.. :scratch:
I'm confused and frustrated. If you can help with the first problem of Gcombust locking up my computer now, I'd be grateful. If you can help me better track what the heck rpmdrake did to screw it up, I'd be grateful and maybe a smidge wiser..
Thanks much for your help..
well.. gcombust is no longer freezing my computer (after doing it 4 or 5 times in a row..)
now it seems to be down to just a cdrecord problem (maybe it was all along..)
running cdrecord from the command line on an .iso, I get the following output:
curioser and curioser.. I tried a different brand of blank cdr and it worked.. But I've made about 10 coasters out of the first spindle pack trying to make this work.. could the entier batch be bad? guess I'll check if there are special options to cdrecord to use if it's not a 650 meg cdr... :study: :scratch:
|All times are GMT -5. The time now is 10:37 AM.|