beta net2hipsend

[dvasco]

all fixed...uploaded and replaced outdated ones...now they should work at least..

yea, i'm gonna have to make a new page...the instructions there aren't even correct..
it's all presetup...
mine leverages the preset files to make it more universal..
and i have the repeat fix to add...

p.s. found out how to add wiki page so n/m...

I started my previous post before I saw this one.

and that info isn't quite correct, net2hipsend can be used with *any* blaster HIP..within
setup is same for all...
and same can be said for hipsend...

Where is the statement I need to correct?

[pBS]

http://gbpvr.com/pmwiki/pmwiki.php/Hardw...nelChanger
the mce section...
btw, hip can use almost all those blasters, [hauppauge hardware plugin was discontinued i think] thru plugins..
and since net2hipsend is a general HIP util, it can be used to trigger any hardware blaster hip can handle..
it has no knowledge of the hardware used to blast..just sends cmds to hip..
[but much much faster than hipsend]

[pBS]

added pics to the wiki page you made, so can link all to there now...
i'll go make a new,concise hip/mce setup guide with full pics as i can and when it's done we can replace the existing one...
i'll be stealing some of the text from it and updating where necessary..

plus i have the 'no software' mce modability stuff to add to a new page..
http://forums.nextpvr.com/showthread.php?p=344872

from what i've heard hip works fine in win7 to so i like it as an all in one remote solution..
and i bet the cheapest good blaster/remote available..

oh and the part about hip needing the alternate driver is completely erroneous...
i use any remote i want with the regular ms driver and hip..
most of that stuff was made for gbpvr 95.x..gbpvr.exe

[dvasco]

http://gbpvr.com/pmwiki/pmwiki.php/Hardw...nelChanger
the mce section...
btw, hip can use almost all those blasters, [hauppauge hardware plugin was discontinued i think] thru plugins..
and since net2hipsend is a general HIP util, it can be used to trigger any hardware blaster hip can handle..
it has no knowledge of the hardware used to blast..just sends cmds to hip..
[but much much faster than hipsend]

I am not sure how it needs to be reworded. I don't see anything that says HIP can't be used with all those blasters.

added pics to the wiki page you made, so can link all to there now...
i'll go make a new,concise hip/mce setup guide with full pics as i can and when it's done we can replace the existing one...
i'll be stealing some of the text from it and updating where necessary..

That would be nice.

plus i have the 'no software' mce modability stuff to add to a new page..
http://forums.nextpvr.com/showthread.php?p=344872

I have seen that thread but the blasting portion of that was confusing and without direct links to files referenced so I didn't even try it since I already had HIP and net2hipsend set up.

from what i've heard hip works fine in win7 to so i like it as an all in one remote solution..
and i bet the cheapest good blaster/remote available..

Did you mean to mention a certain piece of hardware when you said cheapest good blaster/remote available?

oh and the part about hip needing the alternate driver is completely erroneous...
i use any remote i want with the regular ms driver and hip..
most of that stuff was made for gbpvr 95.x..gbpvr.exe

Where is the statement of having to use an alternate driver?

[pBS]

it was just kinda implied since net2hipsend was only in mce section..
should probably be mentioned with hip, more than with hardware...
["For MCE 2005 remotes two options are 1. Net2hipsend "]

as far as the 'no software' section, it doesn't do blasting, you have to use built-in blasting facilities in config.exe...no software only refers to remote input..
[and there should be external links to reference files there,maybe in later posts]

yea, mce hardware is one of the cheapest, most easily available...
i got a vfd,remote and mce dongle for 24$ and have seen them as low as 15$ for remote and dongle..

alternate driver mention in hip guide
http://gbpvr.com/pmwiki/pmwiki.php/Tips/HipGuide
"Assumes:
2) You’ve installed the ‘standard’ package of HIP along with the MCE plugin, and gone though the procedure at the following page to install the alternative driver for the MCE remote. http://www.byremote.com.au/Hip/mce_remote_faq.htm"

[dvasco]

it was just kinda implied since net2hipsend was only in mce section..
should probably be mentioned with hip, more than with hardware...
["For MCE 2005 remotes two options are 1. Net2hipsend "]

That page already existed and I just added a few lines. I have been more concerned with adding info, especially for Hauppauge and MCE remotes and blasters since these can come with Hauppauge cards. Which is why I have been trying to add nethip2send to the Wiki. I'll leave it to others to add info about HIP and other remotes and blasters.

as far as the 'no software' section, it doesn't do blasting, you have to use built-in blasting facilities in config.exe...no software only refers to remote input..
[and there should be external links to reference files there,maybe in later posts]

I didn't understand this, other than what I already understood which is, blasters do blasting and software is needed to control the blaster. I don't know where anything is said to the contrary.

yea, mce hardware is one of the cheapest, most easily available...
i got a vfd,remote and mce dongle for 24$ and have seen them as low as 15$ for remote and dongle..

Was it a MCE 2005 remote and dongle you got for $15? I think they have been discontinued and can't be had easily anywhere anymore. Someone building a new system is limited in choices for WinXP now. This is the main reason I had been wanting to edit the Wiki.

alternate driver mention in hip guide
http://gbpvr.com/pmwiki/pmwiki.php/Tips/HipGuide
"Assumes:
2) You’ve installed the ‘standard’ package of HIP along with the MCE plugin, and gone though the procedure at the following page to install the alternative driver for the MCE remote. http://www.byremote.com.au/Hip/mce_remote_faq.htm"

Ok, I had skipped over that. That was entered February 16, 2006, at 06:54 AM by ricklous. Can you edit that to point to what needs to be done. I don't know because I also use the alternative driver.

[pBS]

mce remotes are still available, they just call them vistamce remotes now, there's a couple new hardware devices, but most use the same old dongle with a new 'vista compatible' remote...so same drive and setup..[i've got both kinds]
and new win7 mce remotes are same from what i've seen..just more buttons on the remote...i should look at the driver .inf's to see if any new buttons codes are mentioned...
so these will be available as long as they have a mce in windows...

i'll be putting together a replacement page for hip setup guide so i guess most of the corrections will be made when the page is replaced...
it's really much easier than it looks now with fewer steps and simpler explanation..
from reading the wiki, i wouldn't think half of the stuff i know works...
plus things have improved in hip and it's driver...

basically what i was trying to say was, they should be grouped by hardware, then software...
most of the software programs can handle several types of hardware, often overlapping eachother...
so i expect users would go to page where their hardware is, then see what programs they can use to control it..following link to sw page..
usually setup for diff hardware is similar within a program...
then just mention net2hipsend on the blasting section of hip setup..
plus most programs don't allow other programs to control the input while they blast with same hardware..eg. to use hip blasting you still have to install the whole program,etc..and either let it control the input part as well or don't use it...

[dvasco]

mce remotes are still available, they just call them vistamce remotes now, there's a couple new hardware devices, but most use the same old dongle with a new 'vista compatible' remote...so same drive and setup..[i've got both kinds]
and new win7 mce remotes are same from what i've seen..just more buttons on the remote...i should look at the driver .inf's to see if any new buttons codes are mentioned...
so these will be available as long as they have a mce in windows...

Correct me if I'm wrong but I thought I read somewhere that the Vista MCE remotes and blaster aren't compatible with WinXP. I know one of the items on Newegg specifically say it isn't. http://www.newegg.com/Product/Product.as...-_-Product

i'll be putting together a replacement page for hip setup guide so i guess most of the corrections will be made when the page is replaced...
it's really much easier than it looks now with fewer steps and simpler explanation..
from reading the wiki, i wouldn't think half of the stuff i know works...
plus things have improved in hip and it's driver...

That's great to hear.

[pBS]

yea, the hardware id isn't in the xp drivers, but can be added easily, i had to for mine..
or just use the vista .inf on xp...i think there's only 2 or 3 new id's added total...
they have been added to the alternate driver, but that one has drawbacks.
i can attach an updated .inf and instructions on adding new ones too..
[driver itself is same]

i'm pretty sure that guy was mentioning the old haupp. style 45 button remote...
[i have one of those 1600's with old remote]
and info is wrong in both cases, both remotes are mce compatible..old one is just not a mce hardware remote...[no dongle,built into card] but it does run mce fine..

[dvasco]

yea, the hardware id isn't in the xp drivers, but can be added easily, i had to for mine..
or just use the vista .inf on xp...i think there's only 2 or 3 new id's added total...
they have been added to the alternate driver, but that one has drawbacks.
i can attach an updated .inf and instructions on adding new ones too..
[driver itself is same]

Info on how to get the Vista MCE remotes to work in WinXP would be great.

i'm pretty sure that guy was mentioning the old haupp. style 45 button remote...
[i have one of those 1600's with old remote]
and info is wrong in both cases, both remotes are mce compatible..old one is just not a mce hardware remote...[no dongle,built into card] but it does run mce fine..

I'm confused again. The card I had linked has an MCE remote and beanbag. Which 1600 were you mentioning?