Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.marketplace Subject: Re: Does Commodore really want to sell WB2.0? I Dont Think So. Keywords: Bugs... Message-ID: <17658@cbmvax.commodore.com> Date: 16 Jan 91 02:21:51 GMT References: <1991Jan11.003327.14423@IRO.UMontreal.CA> <242@coplex.UUCP> <12582@hubcap.clemson.edu> <1991Jan12.064328.411@news.iastate.edu> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 37 In article <1991Jan12.064328.411@news.iastate.edu> skank@iastate.edu (Skank George L) writes: >article <12582@hubcap.clemson.edu> ddyer@hubcap.clemson.edu (Doug Dyer) writes: >> >>Here's my favorite OS2.0 bug. At a root directory, type CD / > Try formatting a floppy from workbench and checking your hard drive for >bad blocks with HDToolbox at the same time. I locked up my machine... (I >also had commodities exchange, autopoint, and blanker running in the >background). Did you report it to bugs@cbmvax.commodore.com? Earlier versions of 2.0 (certainly 36.141/143 (2.0/2.01)) had a problem caused by assumptions about the state of the SIGF_SINGLE bit that could cause SCSI bus lockups, though it was only seen while hdtoolbox was scanning the bus for drives. It could be demonstrated by moving windows around (particularily if they had text being output) while hdtoolbox was starting up. It was quite reliable in the normal case of just starting it up, which was why it was not noticed before the very first release (also an earlier bug in another module had been hiding it until shortly before release). It think (fairly sure, I don't feel like checking the database right now) that bug was fixed before the 2.02 (36.207) release. Development of 2.0 is ongoing (witness 2.02, and developers have access to even newer, and better, versions). We work hard to fix all bugs that are reported to us; if they're not reported we may not notice them ourselves. Report bugs _RSN_ if you don't want to be stuck with them for quite a while to come. bugs@cbmvax.commodore.com is _not_ a black hole, it all goes into an internal database, and is priority and severity sorted and dealt with by the module owner. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup The compiler runs Like a swift-flowing river I wait in silence. (From "The Zen of Programming") ;-)