Installed program in XP Mode and no shortcut Windows 7

[Crewchief408]

Hello All,

I've got Virtual PC/Windows XP installed and working, but when I install a program in Windows XP mode and create a shortcut in the "All Users" folder I don't see it in the Windows 7 start menu.. as a matter of fact I don't even have the "Virtual Windows XP Applications" folder in the Win 7 start menu.

Any help would be appreciated, thanks in advance.

Regards,
Chris

 

[Crewchief408]

I've been trying to get an XP application to run in Win7 with no luck, that's why I got interested in using the XP Mode. The application is used in flight simming for FS2004, and called FSHotSFX. It does many things, but most importantly to me, it adds effects to the AI air traffic environment within FS2004.

When I installed it within XP Mode I couldn't see the shortcut in the Win7 start menu.. so I installed a different program as a test and I now have the "XP Mode Application" folder in my Win7 start menu. It took me a while to create a working shortcut but I managed to do so and the application now starts up and runs within Win7.. except, (isn't there always an except?) it still won't communicate with FS2004.

Many 3rd party addons for MS Flight Simulator make use of an application called FSUIPC to communicate with the Sim so custom joystick controls, instrument guages, real world weather, etc. can function, enrich and improve upon your flight sim experience.

So basically, I start the FSHotSFX program from my Win7 start menu, then I start MS Flight Simulator 2004 and then I get an error message telling me that the FSUIPC.INI can't open FSHotSFX. At this point I think it's a shortcut issue, but it may be that it won't work at all.

The shortcut for the FSHotSFX in the Win7 start menu looks like this:
%SystemRoot%\system32\rundll32.exe %SystemRoot%\system32\VMCPropertyHandler.dll,LaunchVMSal "Windows XP Mode" "||d917cbe6" "FSHotSfx.exe"
And the FSUIPC.ini wants to start the program from this path:
RUNIF1=CLOSE,"C:\Program Files\FSHotSFX\FSHotSfx.exe MINIZ"
Because FSUIPC is looking for a path that is actually in XP Mode and not Win7, I've been trying different shortcut combinations.. without any success I might add.

Since I've more or less solved my initial question in the first post, my new plee for help is basically this: Can anyone help me create a shortcut path that will allow FSUIPC (installed in Win7) to communicate with FSHotSFX (installed in XP Mode) ???

I really appreciate any help.. this one has me stumped pretty good!

Regards,
Chris

 

[logicearth]

If you don't get a shortcut, trying moving the shotcut in XP Mode to the all users start menu.

 

[Crewchief408]

The shortcut to start the FSHotSFX program within Win7 works great now, that's not the problem anymore.. what I need is a shortcut path that can be typed or copy/pasted into an .INI file, in this case the FSUIPC.ini file which allows the FSHotSFX program to communicate with FSUIPC.

Here's what the FSUIPC.ini file looks like:
[General]
TCASid=Type+
TCASRange=10
History=WUYO896AU4OFBJZ0GC5PW
WindSmoothing=No
AutoTaxiWind=No
WhiteMessages=No
ThrottleSyncAll=No
GraduatedVisibility=No
LowerVisAltitude=6000
UpperVisAltitude=25000
UpperVisibility=6000
GenerateCirrus=Yes
WindShearSharp=No
UpperWindGusts=No
ExtendMetarMaxVis=Yes
PatchSimApAlt=Yes
DisconnTrimForAP=No
AutoClearWeather=Yes
ExtendTopWind=Yes
WindSmoothness=5
SmoothPressure=No
PressureSmoothness=5
SmoothVisibility=No
VisibilitySmoothness=2
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
MinimumVisibility=0
MaximumVisibilityFewClouds=0
MaximumVisibility=0
MaximumVisibilityOvercast=0
MaximumVisibilityRainy=0
OneCloudLayer=No
ThinClouds=No
ThinThunderClouds=No
CloudThinness=1000
ThunderCloudThinness=10000
CloudTurbulence=No
CloudIcing=No
WindTurbulence=No
SuppressAllGusts=No
ExternalOptionControl=Yes
AutoTuneADF=No
KeepFS98CloudCover=No
ShowPMcontrols=No
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
TrapUserInterrupt=Yes
NavFreq50KHz=No
ClockSync=No
SmoothIAS=Yes
SetVisUpperAlt=No
VisUpperAltLimit=6000
MaxIce=3
WindSmoothingDelay=0
WindSmoothAirborneOnly=No
VisSmoothingDelay=0
VisSmoothAirborneOnly=No
SuppressCloudTurbulence=No
SuppressWindTurbulence=No
SpoilerIncrement=512
ShortAircraftNameOk=No
TrafficScanPerFrame=10
AxisCalibration=No
CentredDialogue=No
ClearWeatherDynamics=Yes
OwnWeatherChanges=No
FixWindows=No
FixControlAccel=No
WeatherReadInterval=4
MoveBGLvariables=Yes
MainMenu=&Modules
SubMenu=&FSUIPC ...
[JoystickCalibration]
FlapsSetControl=0
ReverserControl=66292
MaxThrottleForReverser=0
AileronTrimControl=0
RudderTrimControl=0
CowlFlaps1Control=0
CowlFlaps2Control=0
CowlFlaps3Control=0
CowlFlaps4Control=0
SlopeAileron=0
SlopeElevator=0
SlopeRudder=0
[Programs]
RUNIF1=CLOSE,"C:\Program Files\FSHotSFX\FSHotSfx.exe MINIZ" <------- I need a shortcut inserted here to tell FSUIPC where to find the FSHotSFX.exe.. this default shortcut doesn't take into account that your connecting from Win7 to XP Mode.

I hope I'm making sence, I know it sounds a bit confussing, so I appreciate any help or suggestions anyone may have.

Thanks,
Chris

 

[StevieM]

Going through this same thing myself, did you manage to get an answer ?

 

[severedsolo]

You won't get a XP Mode application to directly interact with a native Win 7 application. They are actually technically running on two seperate OS'es, although Windows 7 makes it look like they aren't.

If you're talking about FSUIPC in particular, then I have had no problems at all with Addons for FS2004, although I did have to install Net Framework 1.1 for some of them (Like EditVoicepack) which despite the information out there, DOES install on Windows 7 no problem.

 

[StevieM]

That makes a lot of sense as to why they do not communicate.

I have all my other add ons ( so far) working fine in Windows 7 it would be so nice if a genius out there could get FSHotSFX to run also. Only a small add on but the benefit of AIBlast really enhances the overall effect of FS9.

cheers
Steve

 

[severedsolo]

Hi Steve,

I've just had a thought on this.

Is it possible to set the path for AIBlast? or for that matter FSUIPC. If so, then this may help:

Close the VM (XP Mode) and go to the settings. (WIndows Virtual PC>Properties)
Under the "Network Adapter" Tab, change it from "Shared NAT" to your Network Adapters name. (In my case this is RT5780, obviously yours will differ)
This will cause the router to give your VM it's own IP address when you start it.
Then follow this tutorial: http://www.sevenforums.com/tutorials/53830-file-sharing-between-xp-w7-vice-versa.html to set up sharing between them.
Finally, set the path for AI Blast to \\<IP address>\<path>

 

[StevieM]

Ok I have set up the sharing and each folder is recognised on the other system (must admit bit beyond me but got there eventually). Problem is now finding where to put the paths, do I need one in Win7 from FS9 or FSUIPC and/or Win XP with FSHotSFX.

As I said this is somewhat technical for me but a good learning curve.

Thanks for the help

cheers
Steve

 

[severedsolo]

This is very much just a theory, there is a good chance that it won't work at all.

What I am hoping, is that there is a way in which you can input FS9's path into FSHotSFX, for instance if it can't find FS9. (I don't know why, but on my PC, I always have to find FS9 manually, programs never read it properly from the registry)

So it will look something like: <ip address of machine with FS9 on it>\Program Files\Microsoft Games\Flight Simulator 2004.

The easiest way to get the correct path, is to open the FS9 folder on the XP VM (which is being shared from Win 7) and copy/paste the path from the address bar.

As I said though, this all hinges on FsHotSFX having the ability to input a manual path.

Also, do you have to start FSHotSFX seperately? or is it supposed to automatically start with FS?

 

[StevieM]

Ok this is what you can do:-
On the first start of FSHot on XP you are asked to input the path to Flight Sim so it can pick up and register all the aircraft within the sim. I manually entered the path (before the file sharing) and it worked starting up FSHot.
This is where the problems start, when you boot Flight Sim when all software was on XP, FShot shows it is connected to the sim and also reads the FSUIPC version and displays the info on its front screen. However in windows 7 the booting of Flight Sim does not appear to be registered by FSHot although both programs are running happily all be it one in virtual XP the other in Win 7.
From this I can only assume there are some path registrys that require info to go from Win 7 (flight sim / fsuipc) to XP (FSHot).
The fact that both programs run correctly it can only be a path recognition problem ? Or am I being overly optimistic ?

 

[severedsolo]

That sounds promising. We may be in business here then.

Ok then:
From the XP virtual machine, open the shared FS directory. (the one which has your fs9.exe in it)
Click the address bar, and copy/paste the path into FsHot when it asks you for the path.
With a little bit of luck, it should then work. (fingers crossed)

 

[StevieM]

No luck

FSHotSFX runs under virtual XP and seems to recognise path to FS on Win7, reads all aircraft and adds lines into their config.

FS9 runs under Win7 but I cannot seem to get it to 'talk' to FSHotSFX on virtual, cannot seem to get the path right in FSUIPC. Path has been tested and opens ok.

FSHotSFX has the following text file and the lines highlighted seem the problem:-

5/23/2011 3:10:41 PM - FSHS_SYS
CPU: Intel Pentium
CPC: 1@3104 MHz
LDM: 40%
TRM: 511.5MB
ARM: 305.2MB
TVM: 2.00GB
AVM: 1.94GB
TPM: 1.22GB
APM: 1.06GB
OSP: Windows XP
OSV: 5.1
OSB: 2600
OSS: Service Pack 3
LAS: 1033
LAL: 1033
HSV: 1.1.61
CKS: DABDEF39DF87F35B01CEFA13940966A1
5/23/2011 3:10:41 PM - FSHS_DS1:C:\Documents and Settings\All Users\Start Menu\Programs\FSHotSFX\sound\splash.mp3/No Vendor Info Provided
5/23/2011 3:10:41 PM - FSHS_DS2:MPEG-I Stream Splitter/No Vendor Info Provided
5/23/2011 3:10:41 PM - FSHS_DS3:MPEG Layer-3 Decoder/No Vendor Info Provided
5/23/2011 3:10:41 PM - FSHS_DS4efault DirectSound Device/No Vendor Info Provided
5/23/2011 3:10:41 PM - FSHS_Primary Sound Driver,Sound Blaster 16/44100:1/0:0/0
5/23/2011 3:10:41 PM - FSHS_FLT=C:\Documents and Settings\XPMUser\My Documents\Flight Simulator Files
5/23/2011 3:10:41 PM - FSHS_CFG=C:\Documents and Settings\XPMUser\Application Data\Microsoft\FS9\FS9.cfg
5/23/2011 3:10:41 PM - FSHS_FSPath \\tsclient\C\Program Files (x86)\Microsoft Games\Flight Simulator 9
5/23/2011 3:10:41 PM - FSHS_ObjOk
5/23/2011 3:10:41 PM - FSHS_MainOk
5/23/2011 3:10:43 PM - FSHS_IPCvr_3.99
5/23/2011 3:10:43 PM - FSHS_IPCty_Type+
5/23/2011 3:10:43 PM - FSHS_IPCra_10
5/23/2011 3:10:43 PM - FSHS_IPCsc_10
5/23/2011 3:10:43 PM - FSHS_ACFol:273
5/23/2011 3:16:14 PM - FSHS_AIRd:331.7 3/270/267
5/23/2011 3:16:14 PM - FSHS_AIOk
5/23/2011 3:16:14 PM - FSHS_InitOk
5/23/2011 3:16:14 PM - FSHS_LdTm
5/23/2011 3:16:15 PM - FSHS_IPCwrn_Cannot link to FSUIPC or WideClient (FSState=False)
5/23/2011 3:20:44 PM - FSHS_P0 R0 A0
5/23/2011 3:20:44 PM - FSHS_AGA:0/0
5/23/2011 3:20:44 PM - FSHS_CPX: 0
5/23/2011 3:20:44 PM - FSHS_-1


I can manually change them in this text document but I think a CFG file is overwritting them back to default shown above. I am not sure where they get their info from but on an old pc I had the paths differently so I can only assume that FSUIPC or the fact WIn 7 puts things in different locations is affecting this.

 

[severedsolo]

Ah, I didn't think of that. It's looking for the FS saves and data on the VM rather than the main machine. Ok we can fix this (I hope)

From Windows 7:
Open C:\Users\<Your Username>
Press Alt>Tools>Folder Options
From the view tab make sure that "Show Hidden Files and Folders" is selected.
Share Appdata (and all sub folders) and My Documents with the XP Machine (tutorial I linked to before)
Get the shared path for My Documents and AppData from the XP Machine,

From XP:
Open C:\Documents and Settings\XPMUser.
Again, check "SHow hidden files and folders" is enabled.
Right Click My Documents, then click "Properties"
Find "Location" and copy and paste the "My Documents" shared path.
Repeat for AppData.

   Note

This will now cause ALL files/folders saved to My Documents or Appdata on either machine to be saved to the Windows 7 one. With Appdata this may/may not cause problems, (as 7 does it differently to XP) so just be warned.

Seriously, think about this carefully before doing it. I honestly have no idea what the effects will be of doing this. AppData in particular is worrying me, as XP has a different method. If you are using a XP Program that is looking for a XP path, Windows may not redirect it properly. In truth, I have no idea what will happen, but it may break some programs, although it is easily reversed.

 

[StevieM]

Ok now I'm worried, new pc cost fair amount of money that is not spare. I don't want to mess it up. Is it worth it for one piece of software ??

 

[severedsolo]

It won't break your PC, worst case scenario, you may have to just undo the XP bits, and delete the extra created folders.

I'm just pointing out to you the dangers and pitfalls. As you say, is it worth it for one piece of software?

I leave the decision in your hands, but it wouldn't sit right with me if I just said "yeah do this" without pointing out what could (potentially) go wrong.

This is new territory for me too, so I honestly have no idea whether it will work or not, or whether it will break anything, I'm just thinking ahead to a logical outcome.

 

[Tepid]

You might want to look into Symbolic Links and Junctions.
I have no idea if they will work, but that is what is redirectling Documents and Settings to Users in 7.

Just a thought.