[openbeos] Re: Initial patch20020213
- From: "Michael Phipps" <mphipps1@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sat, 16 Feb 2002 02:16:28 -0500
The opentracker, I want to point out, was straight off of opentracker.org. :-)
And I want to take this time to point out to any and all who are testing this,
please,
provide very specific details.
Big crash is not specific details.
Something like
"Mouse pointer would not move. Keyboard led's ceased to function." is pretty
specific.
Better yet (fictional):
"I installed R5.0.3 on my machine (Dell Dimension 400, Pentium II 400 mhz, 128
meg ram, 40 gig hd with
> 5 gig free, 1 beos partition over the whole thing). I installed the patch and
> rebooted. On startup, the
boot screen did all of the normal things, but when the screen cleared to start
tracker, it cycled red, green
and blue screen colors. The speakers emitted strange noises. Tracker did start,
after several minutes, but everything
was backwards, as if read in a mirror. I opened the Fonts preferences panel
using the preferences menu from the
deskbar. Instead of the standard string, it said "(*@*(#@)*()#@". When I cycled
the fonts by clicking "Cycle", the machine
shut down."
While that is my worst nightmare for a release, it is specific enough to help
the develop track down the dozen or so bugs described.
>Ho!
>
>Since nobody yet mentioned it: Thanks for that first OBOS patch!
>Eventually the non-coders can actively participate by testing.
>
>One thing to remember when releasing the next patch is to state in the
>README.1st file that this is an alpha patch that may harm your system.
>While that is explicitly said on the OBOS website, not everybody who
>downloads the package visits it. Plus, IIRC the news about the patch
>appeared first on other BeOS news sites (without a warning), before it
>was up at the OBOS site...
>Quite a few apparently fell into the OpenTracker bug and were left with
>an unbootable system (but it still comes up in Safe Mode).
>
>Thanks again
>J.Seemer
>
>
Other related posts:
