Updated Holloman AFB?

[Bone184]

I was just wondering if there is plans for an updated Holloman AFB Package with F-22's & QF-4's?

[MIKE JG]

I'm sure we'll get to it one of these days but for now, there's nothing in the immediate pipeline.

[timbob1]

[djnocturnal]

I have done all but one of the 7th FS F-22's. you can get them here:
http://marksfsrepaints.jimdo.com/

[Bone184]

Can anyone send me the original Holloman Package? I tried to DL & install it but I get an error code....djnocturnal I was thinking of changing the F-117's for F-22's. Does anyone have repaints of the AI F-4E as a QF-4E from Holloman? I have the FP's installed for the AI F-4C/D repainted as QF-4's.

[Firebird]

Hi Bone, just a quick check to rule out the obvious, but you did use the WoAI installer to install it and if so you have got .Net 2.0 Framework installed haven't you?

[Bone184]

Hi Bone, just a quick check to rule out the obvious, but you did use the WoAI installer to install it and if so you have got .Net 2.0 Framework installed haven't you?

I've done that as there's only a total of 3 that I can't get to install....

Respectfully,

[Firebird]

OK. So it would sound like a corrupt package but I am sure you've tried to re-download. What error do you get and how far into the install?

[Bone184]

Here's the error I get when trying to install the Holloman T-38 Package.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.IOException: Could not complete operation on some files and directories. See the Data property of the exception for more details.
at Microsoft.VisualBasic.FileIO.FileSystem.FxCopyOrMoveDirectory(CopyOrMove operation, String sourceDirectoryPath, String targetDirectoryPath, Boolean overwrite)
at Microsoft.VisualBasic.FileIO.FileSystem.CopyOrMoveDirectory(CopyOrMove operation, String sourceDirectoryName, String destinationDirectoryName, Boolean overwrite, UIOptionInternal showUI, UICancelOption onUserCancel)
at Microsoft.VisualBasic.MyServices.FileSystemProxy.CopyDirectory(String sourceDirectoryName, String destinationDirectoryName, Boolean overwrite)
at WOAI_Installer.frmMain.InstallPackage()
at WOAI_Installer.frmMain.btnNext_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
WOAI Installer
Assembly Version: 2.4.0.0
Win32 Version: 2.4
CodeBase: file:///E:/Program%20Files/Microsoft%20Games/FS9%20DL's/WOAI%20Installer/WOAI%20Installer.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
ICSharpCode.SharpZipLib
Assembly Version: 0.84.0.0
Win32 Version: 0.84.0.0
CodeBase: file:///E:/Program%20Files/Microsoft%20Games/FS9%20DL's/WOAI%20Installer/ICSharpCode.SharpZipLib.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Good news is I did get all but the T-38 Package...can someone send it to me?

[Firebird]

OK, I think that I might have an idea here and I think its why we ran into problems using the WoAI installer, although this part is my suspicion and not anything proven.
I think that the problem is to do with the OS limit on filename length. I first came up against this when I first started beta testing MAIW packages and found that a large number of files were not unzipped due to finlename length, as this includes pathname as well. This was using the builtin zip/unzip feature of the OS.
Winzip and Winrar worked fine as they have a larger filename limit than the OS, strange but true.

I think that if you were to do a manual install to a relatively short named folder it might work. For example all mine I install to F:\WoAI and then manually copy across. Yes, I know this means that you can't use the automatic uninstall feature.

See if this works for you. Of course if you still get the same error then feel free to ignore everything I have just mentioned.

[Bone184]

OK, I think that I might have an idea here and I think its why we ran into problems using the WoAI installer, although this part is my suspicion and not anything proven.
I think that the problem is to do with the OS limit on filename length. I first came up against this when I first started beta testing MAIW packages and found that a large number of files were not unzipped due to finlename length, as this includes pathname as well. This was using the builtin zip/unzip feature of the OS.
Winzip and Winrar worked fine as they have a larger filename limit than the OS, strange but true.

I think that if you were to do a manual install to a relatively short named folder it might work. For example all mine I install to F:\WoAI and then manually copy across. Yes, I know this means that you can't use the automatic uninstall feature.

See if this works for you. Of course if you still get the same error then feel free to ignore everything I have just mentioned.

Firebird, still a no-go, can someone please send me the T-38 Holloman Packages, please.

[Bone184]

I got the T-38's installed.....I went ahead & replaced the F-117's with djnocturnal's F-22's, added the old F-4C/D repaints of Holloman's Drone to the scenery. Thanks for all of the help....

[djnocturnal]

Don't foget to update your afcad, the 22's have different parking codes and radius

[Bone184]

Don't foget to update your afcad, the 22's have different parking codes and radius

I went to do this today, but the AFCAD I have for Holloman doesn't have parking codes for the 7th FS, is mine an old version? I made an area for the QF-4's.....

[djnocturnal]

yeah, if u want those raptors to park in the hangers where the f-117's used to park, you will need to change thos parking spaces designated for the 8th & 9th FS to 7FS, and the proper raidus. Technically the 8th FS has 2 raptors, and is active again, but I havn't done those paints yet.

[kungfuman]

Here is an UPDATED Holloman AFB, with codes as suggested by DJNocturnal:

MAIW_ADE_KHMN_UPDATE_DF.BGL

(53.2 KiB) Downloaded 102 times

(The original file was by Duncan MacKellar. Thanks )

This file was created with ADE, so you will lose data (buildings, taxi-signs, approaches etc.) if you edit it with AFCAD.


The original MAIW file contained a number of errors including:

Incorrect runway designation of 04/22, which de-activated some approach code - making Holloman a VFR only airfield.

Duplicate/additional ILS, which rendered some of the ILS channels and equipment inoperable.


Fixes included in my file:
I have aligned both visual and functional ILS equipment with the runway centrelines, so you will now approach correctly lined up with the runways. I have deleted the erronious ILS equipment, so the correct equipment now works. I corrected the designation of Rwy 03/21 back to Rwy 04/22, and re-linked the approach code so you will now hear "cleared for the ILS Approach..." where appropriate. I updated some of the approach code and adjusted some scenery objects, including taxiway signs. I have also moved some of the default buildings to better match the original afcad.

Please pm me if you find a problem and I will gladly fix it and re-upload.


PLEASE NOTE:
This file is NOT COMPATIBLE with the following MAIW package:

USAF F-117 Nighthawk.

I have another file which is compatible with the original MAIW Nighthawk package here:

http://www.militaryaiworks.com/newforum ... 191#p80191

[Bone184]

Here is an UPDATED Holloman AFB, with codes as suggested by DJNocturnal:

MAIW_ADE_KHMN_UPDATE_DF.BGL

(The original file was by Duncan MacKellar. Thanks )

This file was created with ADE, so you will lose data (buildings, taxi-signs, approaches etc.) if you edit it with AFCAD.


The original MAIW file contained a number of errors including:

Incorrect runway designation of 04/22, which de-activated some approach code - making Holloman a VFR only airfield.

Duplicate/additional ILS, which rendered some of the ILS channels and equipment inoperable.


Fixes included in my file:
I have aligned both visual and functional ILS equipment with the runway centrelines, so you will now approach correctly lined up with the runways. I have deleted the erronious ILS equipment, so the correct equipment now works. I corrected the designation of Rwy 03/21 back to Rwy 04/22, and re-linked the approach code so you will now hear "cleared for the ILS Approach..." where appropriate. I updated some of the approach code and adjusted some scenery objects, including taxiway signs. I have also moved some of the default buildings to better match the original afcad.

Please pm me if you find a problem and I will gladly fix it and re-upload.


PLEASE NOTE:
This file is NOT COMPATIBLE with the following MAIW package:

USAF F-117 Nighthawk.

I have another file which is compatible with the original MAIW Nighthawk package here:

http://www.militaryaiworks.com/newforum ... 191#p80191

kungfuman, does this have the parking for the German AF as well as the QF-4's?

[kungfuman]

Yes, it is compatible with all MAIW packages apart from the USAF Nighthawk package (which is now a retro package). So that includes the German Tornadoes.

If you still have the F-117 Nighthawks active, you can use the other file I provided (follow the link).

Both files provide dedicated parking for upto 18 QF-4s, provided they are coded "QF4" in the "aircraft.cfg" file. They can actually handle a greater number of QF-4s in the nearby overflow parking if necessary.