farber@UDEL-HUEY.ARPA (Dave Farber) (05/18/85)
When I initialize the badtrack on an IBM At with /etc/badtrack and then install Xenix when I boot it up it complains about another track bad. So I rerun the badtrack and tell it that Cyl/track is bad. I then reinstall and reboot and the damn thing still says it has an error during booting on that track. It seems in the bad track table. Why the hell is Xenix touching that and how can I stop it!!!! Friendly systems indeed. Dave
doug@cornell.UUCP (Douglas Campbell) (05/20/85)
> When I initialize the badtrack on an IBM At with /etc/badtrack > and then install Xenix when I boot it up it complains about > another track bad. So I rerun the badtrack and tell it that Cyl/track > is bad. I then reinstall and reboot and the damn thing still says it > has an error during booting on that track. It seems in the bad > track table. Why the hell is Xenix touching that and how can I > stop it!!!! My AT has twice recently reported errors on a disk track that it had previously recorded as bad in the table created by /etc/badtrack. An interesting thing to note regarding this problem is the listing of bad tracks printed out by the badtrack program. Mine first prints out those that were bad when I first got the machine, in increasing numerical order. Then, it prints out those that have gone bad since, in increasing chronological order. One possibility is that some Xenix program expects the bad tracks to be sorted by number, thus doesn't find the ones out of order. The track I am having trouble with is such a track. Anyone having track troubles with correctly sorted tracks? Doug Campbell doug@cornell.{UUCP|ARPA}