Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[SAS~Malone]

huh? say what, walter?! where? how? 
d'you have any info for me, mate, because i hate having that extra Gig of RAM sitting doing nothing in the corner, while the other 3 are all hard at play...

[Whiskey_Sierra_972]

I had it on my PC some times ago!

The guy who have assembled my PC the first time told me that there is such memory extension if I like it (and I like at the moment) but I don't know how do it!

Additionaly at the moment , after a reinstallation of the OS it is gone....

I'll try to keep more information in the next future!

All the best!

walter

[SAS~Tom2]

Malone and walter-solito: Thanks!
I know that XP uses only 3 Gigs max, but since my mainboard is 'dual channel' capable, means able to use e.g. 2x identical sticks of RAM up to 4 Gigs for XP 32 Bit more effectively, that might help nevertheless. I was advised that 3 Gigs of RAM are used more effectively when 2x 2 Gigs of the same type and manufact. are used instead 1x 2 Gigs and 1x 1 Gig of RAM. Still not 4 Gigs are used, but the system-that was what friends told me-might run smoother nevertheless. Hope at least..

I would like to hear about a 4 Gig extension code for XP as well.

(I will try the utility presented here with my next system install, need to reinstall everything next month.)

Cheers..

Tom

[SAS~Sani]

Switch to 64bit OS..no extensions needed then

[No457_Squog]

I didn't know specifically who from No.457 was the author, now that you told me I'm going to credit you properly.

Don't worry about it mate I made the icons for HSFX anyways!

Regarding your question, I only took the icons as resources, nothing else from your .exe and in fact I don't know what extra function does it have. Could you detail them please for me to know.

For HSFX4.11 I added in a little registry tweak and a .dll with a few of my icons to be put in the %windir%\System32 folder. The end result should have been .SFS files with a nice IL-2 logo on them (as opposed to the generic "unknown file" icon that windows uses...) and a modified IL-2 folder icon.

I can send you the icons and registry tweaks etc... that were included in HSFX4.11 if you would like?

[cgagan]

Thanks benitomuso, it's a fantastic idea, I'm waiting for modified versions of  il2fb.exe, I use of 512 MB.

+1 (...please!)

[SAS~Tom2]

Switch to 64bit OS..no extensions needed then

If I had a copy-would sure do. More likely to buy a Win 7 retail copy next year.

Cheers

[benitomuso]

I didn't know specifically who from No.457 was the author, now that you told me I'm going to credit you properly.

Don't worry about it mate I made the icons for HSFX anyways!

Regarding your question, I only took the icons as resources, nothing else from your .exe and in fact I don't know what extra function does it have. Could you detail them please for me to know.

For HSFX4.11 I added in a little registry tweak and a .dll with a few of my icons to be put in the %windir%\System32 folder. The end result should have been .SFS files with a nice IL-2 logo on them (as opposed to the generic "unknown file" icon that windows uses...) and a modified IL-2 folder icon.

I can send you the icons and registry tweaks etc... that were included in HSFX4.11 if you would like?

Squog,

              please, I will appreciate if you can send that to me. I think I know how to make an association of a file type to a .exe. For one side it's OK to make them seem as if they were IL-2 files, but the Shell function of Windows will try to open the musing il2fb.exe and for sure, the .exe doesn't have anything to do with them, so it's only to depict them with some icon and that's all.

  But I would like to take a look at what you did.

  Thanks,
                       Pablo

[No457_Squog]

Ok - I've uploaded the il2icons .dll resource (here);

What you need to do is extract the .dll to your Windows\System32 directory and then run the accompanying il2icons.reg file. That should give you a nice icon for your .SFS files.

[benitomuso]

Ok - I've uploaded the il2icons .dll resource (here);

What you need to do is extract the .dll to your Windows\System32 directory and then run the accompanying il2icons.reg file. That should give you a nice icon for your .SFS files.

OK Sqoug.

  I thought that you solved it in a different way. It's easier to make the same that your .reg does, directly in C++ code calling the Windows Shell extensions when the wrapper (in this case my version il2fbPAL.dll) starts. It could point to the new .exe I made so it isn't needed to copy anything to the system32 as in your case, etc.

  Thanks anyway. Regards,
                                          Pablo

[No457_Squog]

No worries matey - there's also an 'IL-2 folder' icon in that .dll too - you can use it as you see fit

[benitomuso]

Gerax,
           is good to see that you have experimented a lot with it and you have arrived to many interesting conclusions.
 
  By the way (and this is just a personal preference), I consider that contents which are only loaded at the beginning of the Mission and not "pre-loaded" we would say, don't have any real need of being splitted. What I mean? The Maps could perfectly be in a single Files\Maps folder (kind of what you suggest), with only different all.ini files loaded through differnet MODS folders, to make only a sub-set of maps available in the corresponding case. Regarding sounds, PaintSchemes, etc., all will be shared and there's no problem, because they are used "on-demand" by the program.
 
  As a general strategy I adopted a slightly different one of yours, but again: this is only a matter of taste. I have a clean UP2.01 Files folder with all the extra 3DO for cockpits, etc., plus all the maps I could gather, etc, etc. From there I have set up different MODS folders (here it's kind of your system), and everything special is loaded from there, ini files, general MODs, planes MODs, etc.
 
  I was thinking apart of having the typical structure we have first loading Files and later loading MODS over it, to make a new version of the wrapper with this structure: Files / CoreMODS / MODS. I think that it will make loading clearer and will avoid some kind of troubles we typically have. For troubleshooting it will be good too.
 
  Regards,
                        Pablo