Mugsy323

Member
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Mugsy323

  1. A quick check of my RW settings in Win7x64 shows nothing unusual. Primarily, I have it set to "One set for all features" (right-click tray icon and click Properties). And make sure you have the plugin DLL's I note above installed. While I don't have RW in my "Startup" folder, if it keeps disabling on every reboot, try puting a shortcut in there so it reloads with each boot.
  2. I had the same problem with the remote not restoring between boots, but I found that once I set the Properties from the Tray icon, it stays. (I'm not in Win7 at the moment to report my settings. I still use XP32 primarily.) But it is possible to keep it working. I probably did get that info on v1.4 from you, as I scoured the Net for over a week looking for leads on getting it to work and forgot exactly where I found everything. I replaced a dead ATI HDTV Wonder with a Hauppauge WinTV USB hdtv adapter (which does not come with a remote), and use it to watch HDTV on my PC (on my widescreen LCD). The standard WinTV software doesn't work in Win7 x64, but Win Media Center supports it. I still use the remote from my HDWonder in XP, and now I can use it in Win7 as well to change the channel/volume/etc as well. Very cool. Regarding the speed of Win7, it depends on your CPU and the app. I have a quad-core Phenom II and ran some benchmarks. Win7 x64 runs 32bit apps about the same speed (slightly slower as it converts every instruction), but software that takes advantage of the 64bit architecture and multiple cores run almost twice as fast (FutureMark 3D Bench 2005 runs 41% faster!) Once 64bit software becomes more common, the advantage of a 64bit OS will become more apparent. MS really needs to abandon the 32bit platform (add 32bit legacy driver support and dump 32bit OS's entirely). As long as they continue to drag that dead weight around, the platform will die a slow painful death.
  3. Took me a while, but I finally got my old Remote Wonder to work under Win7 (including mousepad). While I'm not sure if it's a necessary step, I had just upgraded to the "leaked" 7048 release of Windows 7 (I had been using 7000 previously). I did notice that 7048 found a driver for my old printer that 7000 could not, so maybe that tells us something (though 7000 claimed to have found & installed a working driver for RW as well). These are the steps I used that eventually got Remote Wonder working in Windows7 Beta (including mousepad). Most steps are probably unnecessary, but it eventually worked after doing them: (If already plugged in, Unplug Remote Wonder.) Download Remote Wonder software version 1.4 (search google for "remote-wonder-1-40-0-0.exe"). Supposedly, only this version works right. Download ftp.x10.com/pub/applications/drivers/x10drivers_x64.exe (x10 drivers). Download Remote Wonder 64bit Vista driver from ATI website. Download Remote Wonder 32bit XP driver v3.04 from ATI website. Download Remote Wonder plugin for "Windows Media Player 10" Download Remote Wonder plugin "MLRmtPgn.dll 3.04" (for Windows Media Center). ...Sit on them for the time being... Install RW-1.4. Reboot. After rebooting, plug Remote Wonder into USB port. The Driver Wizard will search, find, and correctly install drivers. (after each step, check the tray's "Hidden Icons" (up arrow) for the Remote Wonder icon. Once you see it, you can probably skip to the last step.) Run "x10drivers_x64.exe." Reboot. Install RW's 64bit Vista driver. Reboot. Install the XP 3.04 software. Reboot. The Remote Wonder icon should now be among the hidden tray icons. *** LAST STEP *** Right-click and click Properties. On the first tab, select "One set for all features". On the "Plug-Ins" tab, import the "Media Center Library" ("MLRmtPgn.dll") and "Windows Media Player 10" ("WMP10.dll") plugins. Click OK. Remote should now work, including mousepad. Let me know if you find certain steps to be unnecessary. I just listed everything I did before it finally worked. - Mugsy
  4. This is my very first time trying to do this, so bear with me. I've had a VERY rough four days trying to recover a crashed system. I have a Raid-0 setup, When I install Windows (XP, sp2), I must hit F6 to install my Raid drivers and load them from floppy. I need to install XP on a PC with no floppy drive. I used nLite to add my SilImg 3114 drivers to an autobooting CD. And everything SEEMS to work just fine... up to a point, with the system loading the drivers without my needing to hit F6. When I go to install Windows, it sees my Raid drive(s), so I know the drivers loaded. Then a funny thing happens. In the early stage when the installer is copying all the Windows files from the CD, at the very end (99%), I get a message that it "cannot find" any of my raid driver files (prompting me to hit ENTER to try again or F3 to skip. Skipping the files results in Windows being installed to my non-raid IDE drive). I tried putting a 2nd copy of all the driver files (7 of them) in the root of the CD, but it still says it can't find them. I'm certain it must be looking is some path specified somewhere (like in the "TXTSETUP.SIF" file?) that needs to be edited, but I have no clue what to change. Shouldn't nLite of done this for me? I crawled the Net for an answer, but nothing applies to my situation. Many talk of an "$oem$" folder that I don't have. Others describe inserting info that doesn't pertain to my situation (like "Intel Raid drivers). I'm at my wits end. I've been out-of-commission since last Wednesday. I had to canabalize an old PC for it's 10GB drive and then install Windows on it just to get online to do all this. Please help.