On 02-Sep-01 oms101@freeuk.com wrote:
On 19-Aug-01 oms101@freeuk.com wrote:
I only have a small network at the moment a simple system as I am always about to leave town and the full system is lacking a bit of a perpose except to learn from.
Anway some of you may have read before (on the alug list) that I have an old pentium 166 which is dedicated to cd recording ( I know its over kill but it also rips mp3's) and I have writtern a nice little application which takes grips audio track listings and generates postscript files for printing out cd labels via the groff type setting language.
Well I was installing a 486 with 16MB ram ( Specification is thier so I dont get flamed ) with windows 3.1 for a friend as she her dad got this computer some years ago when he went blind and she wanted a simple box to do essays for the Open University and has no money since she is a single mum.
Any way along the line I deceded to burn an image of the dos/win 3.1 box I made for her so I dont have to setup win 3.1 again and ever since I have had a 70% fail rate on burning CD's now I decided today to figure out what was wrong and when I found out I was very supprised.
I now hava a fail rate that is very low for the first CD burnt but goes up if I burn more CD's, and I dont think its just random I feel that burning 3 CD in a row is more likely to fail than a gap of some hours after the first 2.
I got an error on Suse's boot up pages for insmod ide-scsi ( This A: led me to be very impressed with SuSe linux for haveing scripts reporting errors for l ines that I had added to the start up scripts and B: supprise as I dont remember deleting kernal modules since I first "played" (to destuction) with linux) Anyway I confirmed this by typing
insmod ide-scsi
insmod: ide-scsi: no module by that name found
anyway I reinstalled the default linux kernal and confirmed that all was well with,
insmod ide-scsi
Using /lib/modules/2.2.16/scsi/ide-scsi.o insmod: a module named ide-scsi already exists
and then burnt a test CD which worked I cant yet say its solved but it has yet to fail. What I dont understand is how it even tried to work with cdrecord which looked normal and
cdrecord -scanbus
worked and did occasionally work before, I am also curious as to what caused the problem. Could it be a series of switching off the maschine with out sending the box through a proper halt. I have done this as it has no monitor or keyboard and i hate booting my main box just to shutdown another box.
This has since been solved by fixing my scripts which remotely shut down this computer (I had not edited the script so it differed from the reboot script)
I will mail a follow up if I still get problems as this behaviour is so strange I am sure I am at falt and maybe misinforming you all.
Follow up 1: I am still getting problems but now belive these to be vibration related.
Some definatle where as I moved the CDrecorder and this reduced the errors
I think I have been playing with the computer to much, sorry for the spelling I cant even read this one.
I think I mean that vibration is a factor with failed cdrecording. I am still worried about the number of SCSI errors I get though.
Owen Synge
Date: 19-Aug-01 Time: 17:43:55
Date: 02-Sep-01 Time: 23:41:22 _______________________________________________ main@lists.alug.org.uk http://www.anglian.lug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
Date: 03-Sep-01 Time: 02:02:10