Mailing List Archive

Ben Bucksch wrote:
> Mark Cooper wrote:
<CUT>
>> This all falls under the rating and comments section I think.
>
>
> I disagree. This is essential information, in fact exactly the kind of
> information I would expect from such a database (what's the use to know
> that somebody uses an Duron 800 for encoding, if he has serious quality
> problems which I don't want to tolerate? How could I know?), and
> explicitly asking for it makes people fill it out, while they may not
> even think of it in the comments section.
>
> In fact, many or most comments are completely empty.

I moved all data collected on the old website into the new database. The
old website didn't have a field for comments, hence none exist for the
old entries.



>>> * Which software was used - distro, drivers, xfree, mythtv, version
>>> of each
>>
>>
>> Already in the database.
>
>
> No, not in that detail. It doesn't even say, if MythTV or FreeVo was
> used, much less the xfree version. Most have just "tuner driver: bttv,
> gfx driver: nvidia, Audio driver: alsa". That's not very helpful,
> because the gotchas are in the details.

Each entry *specifically* states if the software is MythTV or Freevo and
now also includes the exact version.


>>> * which config used (linux kernel config, modules.conf, xfree
>>> config, any other compile parameters, anything else in /etc/)
>>
>>
>> This is outside the spec of something you can put in database fields
>> and is what the comments section is intended for.
>
>
> Look at the actual comments made. Nothing.

See above. The majority of the entries have not been updated since the
comment field was introduced.


> You *can* provide fields for "relevant modules.conf lines", "relevant
> kernel config options necessary (if you compiled your own kernel)",
> "device driver section of /etc/X11/XF86Config" etc.
>
>>> I didn't know that you're listening at all, much less willing to
>>> improve it.
>>
>>
>> Where did you get that impression??
>
>
> I didn't have any impression at all. It was just a random site on the
> internet for me, which happens to be linked.

*sigh*

--

Mark Cooper
http://netmangler.sourceforge.net - Network Management with Attitude
http://pvrhw.goldfish.org - Open Source PVR Hardware Database

Mark,

I guess I had not seen the latest incarnation of the pvr database. All I
can say is ... wow. Talk about a change. Last time I looked at it (if
this is the same pvr hardware database site I am thinking if), it was
one table about 3 pages long with about 5 times too much granular
information. This is absolutely fantastic. Consider my offer of a php
write officially retracted. =)

Thanks for all your hard work in compiling and maintaining this site.
(this'll teach me to refresh my browser!)

Cheers,

Scott

-----Original Message-----
From: Mark Cooper [mailto:mythtv-users@mcooper.demon.co.uk]
Sent: Tuesday, June 03, 2003 2:18 AM
To: Discussion about mythtv
Subject: Re: [mythtv-users] Sell mythtv "set-top" boxes

Scott Blomfield wrote:
> Ben Bucksch Wrote:
<CUT>
> So I was thinking of something like the following...
>
> A place to maintain a list of TV tuner cards:
> Stereo/mono, linux driver, common problems, common solutions, whether
> you can use more than 1 in a machine, hardware MPEG encoding/decoding,
> expected retail cost (and date cost was entered)
>
> A place to maintain a list of graphics cards:
> AGP/PCI, tv out?, quality of said tv-out, linux driver, resolution
> supported, cost
>
> A place to maintain a list of CPU/Motherboard combinations:
> On board sound, On board video, ram speed, cpu model + speed, # of
MPEG
> streams (at constant resolution) via software encoding, pci slots, agp
> slots
>
>
> Of course, the biggest problem with a list like this is maintenance...
a
> few months ago the PVR-250/350 wasn't supported on linux, now it is.
Who
> on earth would/could keep track of all this information?

Well that is the idea of the PVR Hardware database :) I'm open to
suggestions on how to make it better?

--

Mark Cooper
http://netmangler.sourceforge.net - Network Management with Attitude
http://pvrhw.goldfish.org - Open Source PVR Hardware Database

_______________________________________________
mythtv-users mailing list
mythtv-users@snowman.net
http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users

Mark Cooper wrote:

>> * Which *exact* model each, ideally including exact tuner model and
>> purchase date, because the vendors change models without changing
>> their name.
>
>
> From experience, not everyone has been able to fill in the tuner field
> with 100% accuracy :) Asking people to open up their PC and look for the
> chip revision isn't practical. Some people *have* included this
> information however.

Couldn't you get this from lspci, dmesg and which drivers are loaded?

--
__ ____
/ / / __/ Brian Lalor
/ _ \/__ \ blalor@bravo5.org
/_.__/____/ http://bravo5.org/

At 07:48 AM 6/3/2003 -0500, Pete Hartman wrote:
[...]
>my main point was not that the existing database is bad, but that it is
>not the same thing as a particular "recommended" configuration that is
>documented in detail. If that configuration is documented in its entirety
>(mb, memory config, cpu, etc.--all the usual system variables, as well as
>some outline of setup steps that is more detailed than the main docs,
>including the steps to set up things that myth relies on but rightly
>aren't really part of myth) it will be a good guideline for those who are
>less interested in the science project aspects of setting this up and are
>looking for something that they can just put in place to be an OSS
>PVR. People could then choose how much they wanted to deviate from that
>config based on how much they wanted to wander off in their own directions.

How specific do you really want to be? Your starting list is "mb, memory
config, cpu, etc.". These strike me as the least useful things to specify
specifically ... especially the motherboard. (I'm reminded of old Consumer
Reports product-review articles, in which the top-rated choice had a very
exact model number, a model that in practice proved to be unfindable ...
leaving the reader unsure how similar other models from the same
manufacturer were. Mobos come and go way too fast for a recommended
configuration to suggest a particular one.) Much better, I think, would be
to specify minimum CPU and memory requirements for a standard 1-tuner
combined system ... but I think the HowTo already does that.

Specifying minimums (rather then specifically "recommended" hardware) also
helps because price/performance tradeoffs are central to decisions. I could
imagine the recommended configuration being finalized by somebody with a
"price is no object attitude", so calling for parts that priced Myth out of
most users' range.

In contrast, where people really need very specific hardware advice is in
these areas:

1. Tuner-card selection. This is an ongoing effort, not something someone
can do once and put on the shelf. The quick example of why is the recent,
slipstreamed change in the Hauppauge WinTV Go vidcap card. I'd recommend
this card with enthusiasm, but today's users would be sandbagged by the
fact that the card that is on the shelves today is not the one I use (And I
don't even know how to tell the two variants apart without opening the box
and examining the chipset on the card itself). Another example is these
ivtv cards ... they are bleeding edge right now, but I'd guess that in 3
months (6 at the outside) they will be very conventional.

2. Video card selection, especially video for TV-out. The only cards I
would personally recommend unequivocally are the nVidias that are supported
by the proprietary nvidia X driver. I haven't been able to make any other
card work to my satisfaction (though there are a couple of candidates I
have not tried).

Whether we could come to a consensus even on recommended hardware for these
2 uses is unclear to me. A couple of months ago, I drafted some
minimum-spec guidelines, and the response they got suggests to me that we'd
have trouble agreeing about anything involving hardware. (That's the
problem a database approach avoids.)

Marc's database does offer some help, and the suggestions Ben and others
are making would, if impplemented, improve it. But I think it will always
have two limitations:

1. It is not specific to MythTV. Marc says this is by design, and I respect
that, but it still limits the usefulness of the datbase to prospective
MythTV users.

2. It is structured. A structure encourages respondents to answer the
questions that are asked, while omitting information that is not
specifically requested. (Yes, I know there is a comments field; I'm
predicting that it will not collect the unstructured information beginners
need to supplement the specific questions.)

From time to time, we see on this list postings of particular
configurations, along with discussions of what the problems were and what
special considerations were involved. That, I suspect, is what beginners
really need ... well-written descriptions of particular approaches that
succeeded. Several of these would, in the end, help newcomers more than a
generic "recommended" configuration ... which in practice will be
recommended by nobody in particular and runs the risk of being a
portmanteau configuration incorporating components that no one has actually
used in combination.

Ray Olszewski wrote:

> From time to time, we see on this list postings of particular
> configurations, along with discussions of what the problems were and
> what special considerations were involved. That, I suspect, is what
> beginners really need ... well-written descriptions of particular
> approaches that succeeded. Several of these would, in the end, help
> newcomers

Maybe, but just having them in the newsgroup archive does not make them
accessible to the target group. I wouldn't have known that these are
discussed here at all (thinking that hardware configs are offtopic on
such a list) and even now that I know, I wouldn't know what keywords to
search for to get specifically these "well-written descriptions".
Searching for "Athlon" or "WinTV" would turn up way too much, eh,
"discussion". So, if you have some particular posts in mind, maybe you
could relocate them and post them on the website somewhere?

At 05:17 PM 6/3/2003 +0200, Ben Bucksch wrote:
>Ray Olszewski wrote:
>
>> From time to time, we see on this list postings of particular
>> configurations, along with discussions of what the problems were and
>> what special considerations were involved. That, I suspect, is what
>> beginners really need ... well-written descriptions of particular
>> approaches that succeeded. Several of these would, in the end, help newcomers
>
>Maybe, but just having them in the newsgroup archive does not make them
>accessible to the target group. I wouldn't have known that these are
>discussed here at all (thinking that hardware configs are offtopic on such
>a list) and even now that I know, I wouldn't know what keywords to search
>for to get specifically these "well-written descriptions". Searching for
>"Athlon" or "WinTV" would turn up way too much, eh, "discussion". So, if
>you have some particular posts in mind, maybe you could relocate them and
>post them on the website somewhere?


I think this is a great idea, Ben. You are certainly correct that searching
the list for these posts is laborious ... I cannot think fo a good search
strategy either. But as you may not realize, I do not have write access to
the Myth Website. So someone who does (Isaac? Robert?) will need to do this
... assuming, of course, that he or she agrees with us that it is a
worthwhile activity.

Related to this ... it occurs to me that the closest thing to a definitive
"recommended hardware" list would be Isaac's own configuration. Since he
tests his work on it (I presume), it is the one configuration we know to
work, at least tolerably well, with current CVS, and probably with the
prepacks of Myth as well. Perhaps a detailed description of that
configuration (or a more prominent pointer to it, if it already exists)
would provide a lot of the base that newcomers want and need.

>>>>> Pete Hartman writes:

> my main point was not that the existing database is bad, but that it
> is not the same thing as a particular "recommended" configuration
> that is documented in detail.

Absolutely. I've run an analagous website for printers for years, and
I have both detailed per-printer data and a single summary page that
flat out tells people what to go buy if they are shopping. The world
needs both, for myth hardware even more than printers.

As an aside, I suggest that you sign up with Amazon, buy.com, etc as
an "affiliate"; this way you can maybe get a few dollars for the
considerable trouble of maintaining a support website like this.

--
Grant Taylor - gtaylor<at>picante.com - http://www.picante.com/~gtaylor/
Linux Printing Website and HOWTO: http://www.linuxprinting.org/

At 01:05 PM 6/3/2003 +0200, Ben Bucksch wrote:
>Mark Cooper wrote:
>
>>Thanks for the 'constructive' critisim Ben!
>
>Well, it wasn't meant as critisism at all, I just wanted to say that the
>"solution" Ray offered was none in my eyes. I am sorry, if I hurt you.

Ah well, not all "solutions" are solutions. Some are just help. Since I
suggested vaguely that I saw ways in which the database could be improved,
I thought I should take the time to offer some specifics.

(Background: I've viewing the database on a Win2K host running Netscape
4.something. I normally operate it with ALL "advanced" features -- Java,
Javascript, cookies -- disabled, for privacy reasons. The database I am
viewing is the one that the MythTV HowTo's hardware section links to.)

1. Warn the user that the database display expects Javascript to be
enabled. With Javascript disabled, my browser still displays the data, but
in an almost unreadable format. With Javascript on, the format is merely
hard to read (see next item).

2. Hard to read elements in the Javascript view:

A. The display has some text at the very top that is white print
on light gray. I cannot read what it says.

B. The bluish-gray "header" boxes to not match the text ... some
of the text bleeds off the right side, and the boxes bleed down into the
first row of data.

C. Header and data boxes/text bleed over to the Login and other
sections on the right.

D. The print is very small. (Side gripe: why do so many Web sites
insist on preventing the user from adjusting the type size? Are they all
written by young people with good eyesight, who don't realize the problem
that older folks with failing vision have?)

3. Entries often show up in the wrong field. A common problem is that the
"Rating" number appears in the "Audio" column (this probably happens most
because it is the rightmost pair of fields, so all errors propagate to it).
I'm guessing from this that either the database itself or the Javascript
display manager does not handle empty fields properly, since the errors all
seem to be shifts to the left. (The presence of separate fields for "CPU"
and "CPU type" seems to occasion a lot of omitted data ... understandably
to my eye, since I can't figure out the difference between the two.)

4. Although early entries (page 1) in the database take me to displays of
the complete entry, similar clicking on later entries (page 16) 404 with:

Bad Request

Your browser sent a request that this server could not understand.

The request line contained invalid characters following the
protocol string.

(An actual URL that generates this result is
http://pvrhw.goldfish.org/tiki-view_pvrent.php?systemid=Gabe
Ghearing&PHPSESSID=643a9757786fff46c0e052859aa20ae9 ).

5. Ben suggested a lot of things the absence of which hurts usability. I
suggest these in addition:

A. Date the entry was made (helps identify recommendations made
obsolete due to slipstreaming).
B. Display (even just monitor vs. TV would help.)

6. Your responses to Ben refer to a "comments" section. I'm not seeing this
displayed (not even as an empty field), either on the database "grid" page
or (for the early ones I can access) on the individual-entry page. Where
should I be finding this?

7. More generally, I think you rely excessively on the comments section to
remedy gaps in the specific questions. Ben covered the specifics of this
pretty well, so I won't repeat them here.

8. Navigation: the only way I saw to read through the database is page by
page, starting at page 1 (which I'm guessing is the oldest entries). At a
minimum, I'd like to see a "jump to last page" option ... the most recent
entries are, in my opinion, likely to be the most useful.

OK. Those comments are based on reading the database. Now I tried to enter
my data.

9. First, I pressed "Add entry" and was told I could not post ne because I
was not logged in.

10. I registered, and was told I'd receive an e-mail with instructions. It
came about 10 minutes later. Following the link it provided, I tried to log
in twice. Both times, I was returned to the login page with no explanation,
and when I tried to enter data, I was told I am not logged in. (This may
have been a cookies problem ... if it is, the response page really should
say so ... but after the first failure, I turned on cookies to the
originating server.) The third time I tried -- going back to the URL in the
e-mail message -- I got this message: "Invalid username or password Return
to home page". At that point, I gave up.

Oh well ... at least you know why my data are not in the database.

Hope these comments help you in your effort to make the database more
useful. Good luck.

At 07:34 AM 6/3/03 -0700, Ray Olszewski wrote:
> From time to time, we see on this list postings of particular
> configurations, along with discussions of what the problems were and what
> special considerations were involved. That, I suspect, is what beginners
> really need ... well-written descriptions of particular approaches that
> succeeded.

Which is exactly what I was trying to describe, but apparently failed
miserably at :-)

At 08:52 AM 6/3/03 -0700, Ray Olszewski wrote:
>>Maybe, but just having them in the newsgroup archive does not make them
>>accessible to the target group. I wouldn't have known that these are
>>discussed here at all (thinking that hardware configs are offtopic on
>>such a list) and even now that I know, I wouldn't know what keywords to
>>search for to get specifically these "well-written descriptions".
>>Searching for "Athlon" or "WinTV" would turn up way too much, eh,
>>"discussion". So, if you have some particular posts in mind, maybe you
>>could relocate them and post them on the website somewhere?
>
>
>I think this is a great idea, Ben. You are certainly correct that
>searching the list for these posts is laborious ... I cannot think fo a
>good search strategy either. But as you may not realize, I do not have
>write access to the Myth Website. So someone who does (Isaac? Robert?)
>will need to do this ... assuming, of course, that he or she agrees with
>us that it is a worthwhile activity.

I don't think we necessarily need ongoing write access. I think someone
could volunteer to host the information and make a link to the main website
just once. I would volunteer myself if no one else does, though I'm on the
far end of a not necessarily speedilicious DSL line.

As for the effort to search, perhaps those of us interested in this effort
could split the archives up and each of us search a specific date
range. I'm all ready to sign on for that too.

> Van: Ray Olszewski <ray@comarre.com>
>
> BTW, Jason, plenty of people know how to make custom distros,
> ..snip.. and figuring out a way to support the
> non-free software (e.g., the proprietary nVidia X driver) such a distro
> would need.

You need to stay tuned before saying things like these :-)

Morphix (Knoppix clone) includes the nVidia drivers. The guy contacted
nVidia, and there seem to be a Linux redistribution clause in their
EULA/license. You can find more about it on the Knoppix forum and Morphix
site

Henk Poley <><

A group of friends here in spain we do have already a domain and a hosted in
us that we bought a few months ago. we planned to setup a site for a spanish
user community interested in things related to set-top issues, not
restricted to mythtv, however we still had no time for doing so. So right
now is not being used, and even if it will be, that doesn't means that have
to create any conflict.
Since it's hosted, there is no problem on availability, etc. Has about of
400Mb of free space, 1 mysql database, phpnuke, forum... already
installed...
I've seen also similar offers, so more than having a place to setup the
site... its a matter of having a webmaster isn't?

If someone wants, we have no problem on providing the acces.

Ramon.
----- Original Message -----
From: "Pete Hartman" <mythtv@elmegil.net>
To: "Discussion about mythtv" <mythtv-users@snowman.net>
Sent: Wednesday, June 04, 2003 2:38 AM
Subject: Re: [mythtv-users] Sell mythtv "set-top" boxes


> At 08:52 AM 6/3/03 -0700, Ray Olszewski wrote:
> >>Maybe, but just having them in the newsgroup archive does not make them
> >>accessible to the target group. I wouldn't have known that these are
> >>discussed here at all (thinking that hardware configs are offtopic on
> >>such a list) and even now that I know, I wouldn't know what keywords to
> >>search for to get specifically these "well-written descriptions".
> >>Searching for "Athlon" or "WinTV" would turn up way too much, eh,
> >>"discussion". So, if you have some particular posts in mind, maybe you
> >>could relocate them and post them on the website somewhere?
> >
> >
> >I think this is a great idea, Ben. You are certainly correct that
> >searching the list for these posts is laborious ... I cannot think fo a
> >good search strategy either. But as you may not realize, I do not have
> >write access to the Myth Website. So someone who does (Isaac? Robert?)
> >will need to do this ... assuming, of course, that he or she agrees with
> >us that it is a worthwhile activity.
>
> I don't think we necessarily need ongoing write access. I think someone
> could volunteer to host the information and make a link to the main
website
> just once. I would volunteer myself if no one else does, though I'm on
the
> far end of a not necessarily speedilicious DSL line.
>
> As for the effort to search, perhaps those of us interested in this effort
> could split the archives up and each of us search a specific date
> range. I'm all ready to sign on for that too.
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@snowman.net
> http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users
>
>
>

Pete Hartman wrote:
> I don't think we necessarily need ongoing write access. I think someone
> could volunteer to host the information and make a link to the main
> website just once. I would volunteer myself if no one else does, though
> I'm on the far end of a not necessarily speedilicious DSL line.
>
> As for the effort to search, perhaps those of us interested in this
> effort could split the archives up and each of us search a specific date
> range. I'm all ready to sign on for that too.

I've added a page to the Hardware database with some of the install
guides/How I did It stories that have been posted to the mailing list
linked to. Let me know if I've missed any.

http://pvrhw.goldfish.org/tiki-page.php?pageName=install_guides

HTH

--

Mark Cooper
http://netmangler.sourceforge.net - Network Management with Attitude
http://pvrhw.goldfish.org - Open Source PVR Hardware Database

Ray Olszewski wrote:
> (Background: I've viewing the database on a Win2K host running Netscape
> 4.something. I normally operate it with ALL "advanced" features -- Java,
> Javascript, cookies -- disabled, for privacy reasons. The database I am
> viewing is the one that the MythTV HowTo's hardware section links to.)
>
> 1. Warn the user that the database display expects Javascript to be
> enabled. With Javascript disabled, my browser still displays the data,
> but in an almost unreadable format. With Javascript on, the format is
> merely hard to read (see next item).
>
> 2. Hard to read elements in the Javascript view:
>
> A. The display has some text at the very top that is white print
> on light gray. I cannot read what it says.
>
> B. The bluish-gray "header" boxes to not match the text ... some
> of the text bleeds off the right side, and the boxes bleed down into the
> first row of data.
>
> C. Header and data boxes/text bleed over to the Login and other
> sections on the right.
>
> D. The print is very small. (Side gripe: why do so many Web
> sites insist on preventing the user from adjusting the type size? Are
> they all written by young people with good eyesight, who don't realize
> the problem that older folks with failing vision have?)

Most of the above comes down to the CMS I choose to use - Tiki (
http://tikiwiki.sf.net/ ). I've been actively bug hunting and submitting
patches to their project, so I'll bear all the above in mind :)


> 3. Entries often show up in the wrong field. A common problem is that
> the "Rating" number appears in the "Audio" column (this probably happens
> most because it is the rightmost pair of fields, so all errors propagate
> to it). I'm guessing from this that either the database itself or the
> Javascript display manager does not handle empty fields properly, since
> the errors all seem to be shifts to the left. (The presence of separate
> fields for "CPU" and "CPU type" seems to occasion a lot of omitted data
> ... understandably to my eye, since I can't figure out the difference
> between the two.)

Hmm, not seen or come across this. Bear in mind that alot of the entries
come from the old database that had far less fields and so have been
left blank.


> 4. Although early entries (page 1) in the database take me to displays
> of the complete entry, similar clicking on later entries (page 16) 404
> with:
>
> Bad Request
>
> Your browser sent a request that this server could not understand.
>
> The request line contained invalid characters following the
> protocol string.
>
> (An actual URL that generates this result is
> http://pvrhw.goldfish.org/tiki-view_pvrent.php?systemid=Gabe
> Ghearing&PHPSESSID=643a9757786fff46c0e052859aa20ae9 ).

Works fine for me. Not sure what that is.


> 5. Ben suggested a lot of things the absence of which hurts usability. I
> suggest these in addition:
>
> A. Date the entry was made (helps identify recommendations made
> obsolete due to slipstreaming).

This *IS* included in every entry, although entries moved over from the
old database will not have it.


> B. Display (even just monitor vs. TV would help.)

OK, good point.


> 6. Your responses to Ben refer to a "comments" section. I'm not seeing
> this displayed (not even as an empty field), either on the database
> "grid" page or (for the early ones I can access) on the individual-entry
> page. Where should I be finding this?

The Comments section is below the software settings fields and before
the last modified field.


> 7. More generally, I think you rely excessively on the comments section
> to remedy gaps in the specific questions. Ben covered the specifics of
> this pretty well, so I won't repeat them here.

As I tried to explain to Ben, its a case of where do you draw the line?
The database was initially designed to allow people to compare hardware
setups, as the software set-up comes down to your level of experience
with GNU/Linux.


> 8. Navigation: the only way I saw to read through the database is page
> by page, starting at page 1 (which I'm guessing is the oldest entries).
> At a minimum, I'd like to see a "jump to last page" option ... the most
> recent entries are, in my opinion, likely to be the most useful.

OK, good point.


> OK. Those comments are based on reading the database. Now I tried to
> enter my data.
>
> 9. First, I pressed "Add entry" and was told I could not post ne because
> I was not logged in.
>
> 10. I registered, and was told I'd receive an e-mail with instructions.
> It came about 10 minutes later. Following the link it provided, I tried
> to log in twice. Both times, I was returned to the login page with no
> explanation, and when I tried to enter data, I was told I am not logged
> in. (This may have been a cookies problem ... if it is, the response
> page really should say so ... but after the first failure, I turned on
> cookies to the originating server.) The third time I tried -- going back
> to the URL in the e-mail message -- I got this message: "Invalid
> username or password Return to home page". At that point, I gave up.

Again, Tiki issues. Tiki is Open Source, anyone can submit patches,
improvements. I'll look into it.


> Oh well ... at least you know why my data are not in the database.
>
> Hope these comments help you in your effort to make the database more
> useful. Good luck.

Thanks for the feedback.

--

Mark Cooper
http://netmangler.sourceforge.net - Network Management with Attitude
http://pvrhw.goldfish.org - Open Source PVR Hardware Database

oooops! i didn't know this site ;-)

----- Original Message -----
From: "Mark Cooper" <mythtv-users@mcooper.demon.co.uk>
To: "Discussion about mythtv" <mythtv-users@snowman.net>
Sent: Wednesday, June 04, 2003 11:56 AM
Subject: Re: [mythtv-users] Sell mythtv "set-top" boxes


> Pete Hartman wrote:
> > I don't think we necessarily need ongoing write access. I think someone
> > could volunteer to host the information and make a link to the main
> > website just once. I would volunteer myself if no one else does, though
> > I'm on the far end of a not necessarily speedilicious DSL line.
> >
> > As for the effort to search, perhaps those of us interested in this
> > effort could split the archives up and each of us search a specific date
> > range. I'm all ready to sign on for that too.
>
> I've added a page to the Hardware database with some of the install
> guides/How I did It stories that have been posted to the mailing list
> linked to. Let me know if I've missed any.
>
> http://pvrhw.goldfish.org/tiki-page.php?pageName=install_guides
>
> HTH
>
> --
>
> Mark Cooper
> http://netmangler.sourceforge.net - Network Management with Attitude
> http://pvrhw.goldfish.org - Open Source PVR Hardware Database
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@snowman.net
> http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users
>
>
>

> -----Original Message-----
> From: mythtv-users-bounces@snowman.net
> [mailto:mythtv-users-bounces@snowman.net]On Behalf Of Mark Cooper
> Sent: 04 June 2003 10:57
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] Sell mythtv "set-top" boxes
>
>
> Pete Hartman wrote:
> > I don't think we necessarily need ongoing write access. I
> think someone
> > could volunteer to host the information and make a link to the main
> > website just once. I would volunteer myself if no one else
> does, though
> > I'm on the far end of a not necessarily speedilicious DSL line.
> >
> > As for the effort to search, perhaps those of us interested in this
> > effort could split the archives up and each of us search a
> specific date
> > range. I'm all ready to sign on for that too.
>
> I've added a page to the Hardware database with some of the install
> guides/How I did It stories that have been posted to the mailing list
> linked to. Let me know if I've missed any.
>
> http://pvrhw.goldfish.org/tiki-page.php?pageName=install_guides
>
> HTH

http://www.bubber.com/pundit/

Robert Munro

At 10:56 AM 6/4/03 +0100, Mark Cooper wrote:
>Pete Hartman wrote:
>>I don't think we necessarily need ongoing write access. I think someone
>>could volunteer to host the information and make a link to the main
>>website just once. I would volunteer myself if no one else does, though
>>I'm on the far end of a not necessarily speedilicious DSL line.
>>As for the effort to search, perhaps those of us interested in this
>>effort could split the archives up and each of us search a specific date
>>range. I'm all ready to sign on for that too.
>
>I've added a page to the Hardware database with some of the install
>guides/How I did It stories that have been posted to the mailing list
>linked to. Let me know if I've missed any.
>
>http://pvrhw.goldfish.org/tiki-page.php?pageName=install_guides

Exactly what I was looking for, thanks very much!