Safely Remove Hardware (Wireless)

[mewi]

Thanks for the new download file and post but: no, no, no!

I don't think you're reading what i'm trying to write.

You're still jumping into the middle of the install process. I don't know how program A fits to program B. (A software developer could pick any number of different ways) For example: guessing at how programs A and B communicate with each other as you must configure it for them to run. Maybe guess configured to use TCP/IP to communicate amongst them. Oh wait, maybe they use pipes instead. Oh, wrong again... they talk through shared memory and i have to pass all the semaphore names in that empty registry key i found.

Like i said, this approach can be like trying to find that proverbial needle in a haystack. Not saying it's impossible to find that needle this way but it's far too much work for a lower chance of getting maybe/only/sometimes something to work

So i'll state again: Rather then jumping into the middle you start at the beginning. You try to learn the install process is doing, what its configuring, which set of files it uses along its build/install path, look for clues as to the data it uses for setup, might find some of the variable and values you need to so it all makes sense. and most important are the "artefacts" left behind (e.g. you're not curious to see if that log file i pointed out still exists on your drive? Maybe find the logfile info is minimal, sometimes its a landmine and tells all.. and sometimes it only STARTS minimal until you see something in an ini file like LOGLEVEL= and get lucky after a few guesses and and learn how to simply assign LOGLEVEL different values to capture detailed program trace info. Might even tell u about variable/values used..

Bottom line: Can see if we possibly find anything trying to walk through installer process / steps... I may make an observation. direct you at the legwork

Oh. one more thing. The time you put into figuing out installers can be alot of time and not always pay off on the product you're lookin for. BUT whatever you learn is reusable and can help the next time where you start with a little more knowledge on figuring out installers.

With your current method, i think in spite of all hte time you have to invest to maybe solve questions, it's all THROWAWAY doest no gurantee any of the details on the program are reusable for next program

I was listening, and I already tried looking for AiRemote.log or that setup file, they do not exist because the installer cancels at 13%, I tried looking for them while the installer was initiated, even when the error message was open during the installer.

How about for the sake of argument, that the error messages have nothing to do with how the thing was installed, what next?

 

[LookinAround]

I don't have time now to go further.. but here;s some homework <g>

OH. and Don’t hold back data. I’m not going to assume you did something because you never said you did or did not (e.g. you already looked for the .log file but hadn't indicated you had followed up on anything)

Next step for you is expanding your “bag of tricks” / toolkits

Click for SysExporter
- Advise you get familiar with it / very handy to have and use
- You will often want to pull text from a window you can’t copy. (Save it, search it, etc. )
- Especially with XP . Get familiar with it

Use Process Explorer not Task Manager

• Install Process Explorer
• Click Options and set Hide when Minimized, Allow Only One Instance, Confirm Kill, CPU History in Tray Icon
• just fyi..Whenever PE is open, you can click CPU column header to see processes sorted by CPU usage. When usage high, check top of the list, OR
• Minimize PE. Note the red and green waves through its system tray icon
  • Green indicates total CPU usage
  • Red indicates the process using most the most the CPU time
  Hover cursor over the icon to get the info

Run the install shield (use it for practice) Let it hang at error message when it get there. Now you can find process in Process Explorer I’ll point out some things but plenty for you to find out on your own

• Click Process column to change views between alpha A-Z, alpha Z-A, or Parent-Child
  ===> Note the order of things parent-child also. Everything under Explorer is your desktop
  ====> Before that is system startup
  ===> Parent-child can be very useful knowing where a program came from / related to when yur looking at ProgramX.. and can find ProgramA calls ProgramB which calls X
• Click View->Show Lower Pane, Lower Pane DLLs
  Now click install shield. Note all the .dlls’s and librarys it relies on you can see in
• Click View->Show Lower Pane, Lower Pane Handles
  Now see all the “handles” (i/o descriptors) it has open.. you can also get hits to registry keys , files it writes or reads, etc.
• Back to processes, Rt click Install Shield->Properties
  => Image tab .. shows where executable came from and any special command to start it
  - See who the parent process is (if explorer it was kicked off from Desktop)
  => TCP/IP know if the process has any communication associated with it
  => Environment variables defining the environment its in (some of these looked at by Install Shield)
  => Strings. Note radio buttons at bottom. Image and Memory. To see all the hardcoded strings in the InstallShield when on disk vs. now in memory

Use Sysexporter to capture Strings (even tho its there)
Use those / search for other tools if need be to find which of the install files actually contains your error message string (and making this up so do it or not is up to you but you should get familiar with other tools)

You can also see if you can find surfing online any indication of how to turn on that logfile u couldn't find on your desktop. If it’s defined but nothing on disk.. it’s probably a switch or variable value yu can change in a file and try to generate it yourself

This stuff so far may not sound exciting or near and dear to the software you want to debug but like i said
- time you put in now is reusable as just about all programs use the installer and similar commands, etc
- much better odds at figuring out to get a program work if you figure out what the installer would have / did do

 

[LookinAround]

1.) Is there a specific part number or hardware model or other for your AI remote?

2.) Download and run Everest Home. From top of Everest window:

• Click File->Preferences
  • Check English
  • Still under Preferences click Report, uncheck Include Debug Information
  • Close Preferences window
• Click Reports->Report Wizard. Get a Custom Report in plain text. Check items
  • Computer
  • Motherboard
• Please attach to a TechSpot post

/**** EDIT ****/
And which version of the driver did you end up using?

 

[LookinAround]

Like i said. you have to start at the top....

I looked at the ASUS Product pages

AI Remote is only supported on M2N32-SLI Premium Vista Edition
..not M2N32-SLI Deluxe/Wireless Edition

i think you're out of luck