Problem registering 4.955 in P3D V3

[NickATC]

MOVED TO SUPPORT FORUM !!

Hello to all.

I have been using FSUIPC for some time with FSX.  No problems.  Awesome program.  It allows me to use all the switches and levers in my CH set (Yoke, Quadrant and pedals).

 

However, I'm migrating slowly to P3D V3, and of course, FSUIPC is a must.

 

The problem is that I can't make the registration of the product in P3D, but in FSX it is perfectly registered.  I will  explain what I do:

1.  Right click on the 4.955 install. Execute as admin.

2.  Installation is successful for FSX and P3D V3.  See the FSUIPC4 Install.log for FSX and FSUIPC4 Install.log for P3DV3. I leave registration 

3.  I checked on the MODULES folder of P3D V3... and everything is in the right place.  

4.  Start P3D.  FSUIPC is correctly installed.  Of course not a registered copy, so I close P3D and copy and paste the FSUIPC4.key in the MODULES folder for P3D.

5.  Right clicked an the 4.955 install, and at the end of installation, as I have done many times, I get the possibilty to register my FSUIPC.  I click on CHECK SELECTED EXISTING REGISTRATION and then GO AHEAD.  The small window disappears... and then nothing.  I thought it was ok... so I opened P3D, but still FSUIPC says it is not a registered copy.

6.  I start over, but this time I want to ENTER A NEW REGISTRATION.  GO AHEAD, my name and mail are on the blanks, I just copy the code, and then OK or something like that... CONFIRM at the end.  The small window disappears... and I think that FSUIPC is working.  Nope!  still a non registered copy.

7.  I start over, but this time DELETE the registration and then again, step 6.  Still no luck. Not a registered copy

 

So, what am I doing wrong? What am I missing?

 

Thanks in advanced.

 

Nick

Edited June 22, 2016 by Thomas Richter
Moved to main Forum

[Thomas Richter]

Hi,

nothing wrong with what you do.

Check your PC Date is current.

Thomas

[Pete Dowson]

6 hours ago, NickATC said:

1.  Right click on the 4.955 install. Execute as admin.

2.  Installation is successful for FSX and P3D V3.  See the FSUIPC4 Install.log for FSX and FSUIPC4 Install.log for P3DV3. I leave registration 

You should register in the Installer. It will apply to both FSX and P3D.

6 hours ago, NickATC said:

So, what am I doing wrong? What am I missing

The FSUIPC4 Install log file is produced for a purpose. It will show me what you are doing and what happened. That is what it is for. Why not paste its contents here so I can see it?

Pete

 

[NickATC]

Thanks for your reply, gentlemen.

 

@Thomas.  I already checked the date and time and both are current.

@Pete Dowson, in my original post I attached the 2 logs (for FSX and for P3D), that's why I mentioned them in the second step of my post. Not a big deal, here they are:

 

For FSX:

Installer for FSUIPC4.DLL version 4.955c

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=E:\FSX\

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX
     Parameter"AppPath"
Not there, so looking in:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
... >>>  OK! FOUND Prepar3D v3!  <<< ...
     SetupPath=E:\P3D\
===========================================================

INSTALLATION FOR FSX:
SetupPath="E:\FSX\"
Checking version of the FSX EXE:
... Version 10.0.61637.0  (Need at least 10.0.60905.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       E:\FSX\Modules\FSUIPC4.DLL
... Version 4.955c found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "E:\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\uario\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\uario\AppData\Roaming"
Found FSX.CFG in "C:\Users\uario\AppData\Roaming\Microsoft\FSX\FSX.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... There is a SimConnect.XML, checking for "local" section.
... "local" section already exists, file not modified.
Looking in "C:\Users\UpdatusUser\AppData\Roaming"
 ... No FSX.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX and P3D controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
Failed to install "FSUIPC4_Loader.dll"
   Error 32 reported ("El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso. ")
===========================================================

INSTALLATION FOR Prepar3D v3:
SetupPath="E:\P3D\"
Checking version of the Prepar3D v3 EXE:
... Version 3.2.3.16769  (Need at least 1.0.677.0)
Checking compatibility with installed SimConnect:
Checking if there's already a version of FSUIPC4 installed in:
       E:\P3D\Modules\FSUIPC4.DLL
... Version 4.955c found.
Prepar3D v3 Modules folder already exists.
Okay -- installed FSUIPC4 into "E:\P3D\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\uario\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v3\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\uario\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\uario\AppData\Roaming\Lockheed Martin\Prepar3D v3\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\UpdatusUser\AppData\Roaming"
 ... No Prepar3D.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
   Installed "SimConnectP3D3.dll" okay
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX and P3D controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC4_Loader.dll" okay
===========================================================

All installer tasks completed.
Registration dialog exit: selected  FSUIPC DELETE
Deleted previous registration ...
Providing FSUIPC registration dialogue ...
Registration for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************
 

 

 

 

 

 

 

 

and for P3D:

Installer for FSUIPC4.DLL version 4.955c

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=E:\FSX\

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX
     Parameter"AppPath"
Not there, so looking in:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
... >>>  OK! FOUND Prepar3D v3!  <<< ...
     SetupPath=E:\P3D\
===========================================================

INSTALLATION FOR FSX:
SetupPath="E:\FSX\"
Checking version of the FSX EXE:
... Version 10.0.61637.0  (Need at least 10.0.60905.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       E:\FSX\Modules\FSUIPC4.DLL
... Version 4.955c found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "E:\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\uario\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\uario\AppData\Roaming"
Found FSX.CFG in "C:\Users\uario\AppData\Roaming\Microsoft\FSX\FSX.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... There is a SimConnect.XML, checking for "local" section.
... "local" section already exists, file not modified.
Looking in "C:\Users\UpdatusUser\AppData\Roaming"
 ... No FSX.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX and P3D controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
Failed to install "FSUIPC4_Loader.dll"
   Error 32 reported ("El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso. ")
===========================================================

INSTALLATION FOR Prepar3D v3:
SetupPath="E:\P3D\"
Checking version of the Prepar3D v3 EXE:
... Version 3.2.3.16769  (Need at least 1.0.677.0)
Checking compatibility with installed SimConnect:
Checking if there's already a version of FSUIPC4 installed in:
       E:\P3D\Modules\FSUIPC4.DLL
... Version 4.955c found.
Prepar3D v3 Modules folder already exists.
Okay -- installed FSUIPC4 into "E:\P3D\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\uario\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v3\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\uario\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\uario\AppData\Roaming\Lockheed Martin\Prepar3D v3\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\UpdatusUser\AppData\Roaming"
 ... No Prepar3D.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
   Installed "SimConnectP3D3.dll" okay
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX and P3D controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC4_Loader.dll" okay
===========================================================

All installer tasks completed.
Registration dialog exit: selected  FSUIPC DELETE
Deleted previous registration ...
Providing FSUIPC registration dialogue ...
Registration for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************
 

 

 

Thanks again.

Edited June 22, 2016 by NickATC
Typos

[Pete Dowson]

29 minutes ago, NickATC said:

@Pete Dowson, in my original post I attached the 2 logs (for FSX and for P3D),

Oh, sorry, I didn't realise they were links -- folks never seem to do that here. They either paste them in or attach them. I thought they were just underlined and coloured for emphasis.

BTW both logs are of course identical. The installer places the same log in its own folder and in each installed copy of FS it encounters. It performs all of the installer actions in one session and produces just one log.

Note: in the last install log, the one you pasted just above, it says:

Registration dialog exit: selected  FSUIPC DELETE
Deleted previous registration ...

What were you doing there? It is not the same as the log you linked to originally. Also it contains this strange error

Failed to install "FSUIPC4_Loader.dll"
   Error 32 reported ("El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso. ")

in the FSX install section, which the linked one did not. The error is " The process can not access the file because it is being used by another process. " -- what was using a DLL installed in the FSUIPC Documents subfolder? What other processes were you running at the time?

I see you are still using P3D3.2. Any reason for sticking with that? I think 3.3 offers more stability and of course other improvements.

Anyway, the installer log shows nothing else wrong, only those two oddities. The same registration would have been automatically placed in both sims.

So it must be a run-time thing. For that I need to see the FSUIPC4.LOG file, from the P3D Modules folder, please. Don't enable any looging options or click "New Log", just run P3D, get to a "ready to fly" point, see that FSUIPC says unregistered, then close P3D down. When completely closed, get that Log file.

Pete

 

 

[NickATC]

Thanks Pete

 

I made a search to see if this problem was already solved, and realized that those files were always asked... so I attached them.  I saw that the computer time was also another common problem, and I checked it was correct ;)

 

I'm sticking with this version beacuse I'm planning to format my computer in the next week, and I bought and installed that P3D version... just to test several things.  As I said I'm planning to move to P3D, so I needed to test if it could work with IVAO (That's why the P3D.exe was renamed FSX.exe, but it did the trick), with FSUIPC (it will work), TrackIR5 (I made a small change and worked!), and other addons.  Once I see it works, I'll format my computer and update to the latest version available.

 

As for the files, I deleted previous registration because I wanted to start over... perhaps a file was corrupt or something else.  Anyway, I entered the information again, and still didn't work.  No other programs were running, so not sure why the  "El proceso no tiene acceso al archivo porque está siendo utilizado por otro proceso."  appeared.

 

So, Pete, what do you want me to try?? I have tried many things... so give me one path and I'll follow it.

 

Thanks

[Pete Dowson]

13 minutes ago, NickATC said:

That's why the P3D.exe was renamed FSX.exe

Er ... that would certain mess FSUIPC's installer up! But if that was the case how come

Checking version of the Prepar3D v3 EXE:
... Version 3.2.3.16769  (Need at least 1.0.677.0)

was logged by the installer? It can't do that if you change the EXE name. In fact that would mess the run-time actions as well!

13 minutes ago, NickATC said:

So, Pete, what do you want me to try?? I have tried many things... so give me one path and I'll follow it.

For now EXACTLY as I asked in my last message here! Did you not read to the end?

Pete

 

[NickATC]

37 minutes ago, Pete Dowson said:

 

50 minutes ago, NickATC said:

That's why the P3D.exe was renamed FSX.exe

Er ... that would certain mess FSUIPC's installer up! But if that was the case how come

Checking version of the Prepar3D v3 EXE:
... Version 3.2.3.16769  (Need at least 1.0.677.0)

was logged by the installer? It can't do that if you change the EXE name. In fact that would mess the run-time actions as well!

 

Gee... I found the solution to the 'mystery' :/

To install IVAp (the IVAO pilot software) I had to make a copy the original P3D.exe and then rename it to FSX.  It was like a small trick suggested on their forum to make a succuessful install of their software.  And it worked!   So, within the main P3D  folder, I have two executables:  FSX and P3D.  Which are the same file, but with different names... and the executable I was activating was the FSX.exe 

 

After reading your post, I tried the P3D.exe and then tested everything... included FSUIPC... and with this exe FSUIPC is perfectly activated and the other addons work flawlesly.

However, if I execute the FSX.exe, everything works, BUT  the FSUIPC!!  All other addons work perfectly.  

 

What a silly mistake... well an inocent one.

 

The solution?  create the FSX.exe to install everything, and then execute the P3D.exe.  This way, everything is ok.

 

Thanks for the help, Pete.  Sorry to bother with such a silly mistake.

 

Nick

 

Keep up the great work you've done for this comunity!

[Pete Dowson]

18 minutes ago, NickATC said:

However, if I execute the FSX.exe, everything works, BUT  the FSUIPC!!  All other addons work perfectly.  

You can use renamed EXEs with FSUIPC, but you have to rename its files too -- including the Registration file, and the INI file with your settings. You should have noticed that the LOG and INI files it made were not "FSUIPC4.LOG" and "FSUIPC4.INI". That would have pointed immediately to the problem.

This is all part of a facility to allow the use of different settings for different purposes and is explained in the section Multiple INI files on page 49 of the FSUIPC4 Advanced Users guide. That section talks only about FSX, but most of it applies to P3D too, though perhaps not the part about renamed P3D CFG files. L-M may not have implemented that facility, I haven't checked.

Pete

 

[NickATC]

Thanks

 

I never thought I would use advanced feautures, but I will read the advanced user guide.