BatmanYZFr1 wrote:
..and Im stuck at work on a laptop..
...ouch, how did that happen
Re the .cfg files, information and guides are available if you need them. I'd strongly suggest that you stick to the basics first if you're new at this.
I don't have to tell you to back up the originals before you start editing, do I?
Just some basics:
You have to grasp the concept of 'aliasing' which is used frequently to keep a/c downloads smaller. Good soundsets and panels take up a lot of space.
Have a look at your FSX default Boeings. You'll find that only the 737-800 has actual sound files inside the sound folder. The others, such as the 747 are 'aliased' to the 737-800.
All you have to remember is that if you download a freeware a/c and you find that after installing it you don't have sounds or there is no panel, open the sound- or panel folder and see what it says in the respective .cfg and edit it accordingly.
That's really the easy part.
What you'll have to spend more time on and IMO is an important part of the repainting process is the aircraft.cfg, namely the part that pertains to your own, new repaint. I won't permit myself to go into details here... not again.
If you wanna do the right thing and gain the respect of those who start downloading your textures, include a correct, tested by you, partial aircraft.cfg. In other words, before you upload one of your new creations, make sure you didn't make a mistake in the aircraft.cfg -- pretend you're someone who just downloaded your textures. Follow the Readme and insert the partial text (provided by you, of course 😉 ) and load the aircraft to see if the textures show up.
If they don't, you'll have to go back and make the necessary corrections in the aircraft.cfg.
The best way to learn what to do and what not, is to download textures by other repainters and install (just those textures) into an aircraft you already have. You'll be surprised what you'll find.
A good, basic guideline as to how the part of the .cfg which pertains to textures should look like is to look at the default FSX a/c. One is enough, say the 737 because it has several different textures.
The only thing you have to get used to is that Microsoft gives the various textures numbers instead of names... not a good idea: texture.1, texture.2, texture.3 etc.
Say you're doing an AA repaint, name the texture folder texture.aa --- a KLM would be called: texture.klm etc. Obviously that's what will have to show up in the aircraft.cfg in the end.
If or when you need a detailed guide to the aircraft.cfg, I'll dig one up. 
😀