CONFIG LS 3.0 -- News of changes and additions. Version 1.00 Changes from CNFGLS13 There are a lot of these. 1. Additional questions on page 1 are included so some tuning can be done depending on whether you have the Advanced or the Entry server. #3 asks which you are using -- easy enough -- but watch out for #3a! #3a asks if FAT files are shared (if you are using the Advanced server) or it asks if HPFS files are shared if your are installing the Entry server. Caching (CONFIG.SYS) statements change depending on your answers, so be carefull of the changing question! #3b asks if you are configuring a Domain Controller or an Additional Server. A DC takes a bit more RAM with 3.0 than the AS. #11 While we are on memory requirements, the new OS/2 RIPL feature takes more server RAM than the DOS RIPL we have had in the past. So, question #11 has been Cloned! 11a wants to know if you have any DOS RIPL requesters, and 11b wants to know about any OS/2 RIPL requesters. That is all the new stuff on page 1. 2. The second screen of questions is new and asks for information about your LAN adapter(s). You may have none (and use the loopback driver) or you may have up to 4. If you have adapters, they may be Token-Ring or EtherNet. If they are Token-Ring, they may be 4Mbps 16/4Mbps or Busmaster adapters. If they are EtherNet, they may be from any of the manufacturers whose cards are supported. Answer the questions and review the generated parameter recommendations. These appear in Column D - to the right of the questions (the same place all those pesky error messages show up.) 3. Screen 4 has more error messages than before, but you still need to ensure you have a string of OK's displayed here before going on to the results. OK, I know the last entry will say "None" if there are no warnings. The OK's are the important things. 4. There are several new error checks and error messages. These should not make use of the tool harder, though. 5. Note that some new fields are calculated. Primary/ALTERNATE adapter, adapter buffer size and some NTS/2 parameters to name some. 6. The Transmit Buffer Size recommendation changes depending on your adapter type. Don't worry, it is not an error. 7. I tried to include the new memory requirements, but these are taken from the documentation, and are not something I've tried out myself, so I don't swear by them. You shouldn't either. Use of this tool to find a minimum system is dangerous! It will give minimum performance, and it may not run at all. 8. You might notice that there are fewer assumptions made now. One that is important is that if you have a Busmaster TRN adapter, I assume it is the 32 bit adapter. If you have the 24 bit version, you might have a problem. The 24 bit adapter will not support memory over 16MB, but the spreadsheet might try to allocate cache there. Your generated configuration won't work right. 9. As indicated, the Work Area and the Error messages areas have grown. 10. There may be some blank lines at the bottom of the INI file that could make you think you have seen all the generated stuff. Don't be fooled! Page down through them until you see the END OF DATA message. The blank lines would be used for configuring adapter cards (NIC's) you do not have. 11. At he very end (bottom) of the spreadsheet are the cache recommendations. THESE REQUIRE MODIFICATIONS BY YOU. This may be just changing them to add the correct drive letters, but if you have other work to do, there will be messages that appear to tell you (123 users) what it is -- so read the messages! It is possible to use CNFGLS13 on a 3.0 server, but use of CNFGLS30 will probably give a better performing system. Using CNFGLS13 can also waste some memory. Will run, though. ------------------- Well, I intended to update this, but maybe not quite so soon. If you know somebody who has the package but may not have subscribed to it on MKTTOOLS, please let them know Version 1.01 is now current. Two changes. 1. The IBMLAN.INI file's 'netx' line had 'lm10' specified. This must be capitalized (LM10). Now, all alpha characters in the 'NETx' line(s) will be caps. 2. The 'netbeui_nif' Sessions, Commands and Names in the PROTOCOL.INI file must be at least one greater than the IBMLAN.INI NETx line specifies. Now, they will be. ------------------- Well, another week and another set of changes. I need to thank Ken Whitfield and all the folks he got together with me so we could get the input of the LAN Server and NTS development teams. A few days in a conference room generated a lot of detailed changes -- to many to itemize here. You'll see the differences, though, if you inspect the results of a run at all. This should give better performance than other, earlier, versions of CNFGLS30, so make sure folks know about it! So, here is Version 1.02 4/9/93 -------------------- Made it two weeks without an update! Must be getting better at this. These changes are all from user feedback on Prodigy and the OS2LAN CFORUM so I thank you folks for the help! After all, we're all in this together and I sure DO need the help! 1) I had an erro in calculating the 802.2 storage requirements that might have given you a message about not enough work area that you should not have gotten -- fixed. 2) 'Other NetBIOS Apps' resource requirements got added in to the LS NETx line(s). Opps. 3) I was only allowing 5 802.2 users. Now, you can have 12. 4) The multiple adapter area was not fully cleaned up when you set up for several adapters and then decided to see what would happen with fewer. Now, I think everything you don't want to see disappears. 5) One user reported that the large number of maxsearches generated when DLR's were supported gave problems with printing. Dunno, but I set the generated value down, and sent the note on to the developers who suggested the higher value. Maybe we'll see a fix to LS30 someday and be able to increase it for those DOS apps that need higher values. If your apps need the bigger number (it will be 700 now), just change it in your INI file. No other parameters are affected. 4/23/93 ----------------------------------------------------- Well, looks like it is time for 1.04. Only a couple of things to change, but there are over a thousand users of this tool that I know about, and I certainly want to keep it as up-to-date as possible! 6 weeks with no problems, but now I have 3 changes to make. 1. You could get a recommendation for additional RAM when you had enough. A bug calculated a bad cache size which was detected as being too small and (bingo) the recommendation popped out. Adding the recommended RAM would make everything work out fine. Looks like CNFGLS30 was trying to fix its own bug here, I dunno. 2. The 123 version omitted the RUN= statement in the CONFIG.SYS recommendations to run the OS/2 Standard Edition (SE) cache. It has now been added. 3. The Excel version specified this same cache should be loaded off the C drive. Meant to say 'c' so you'd know to specify the drive where OS/2 was installed. Finger check! Changed it. Had a request to make FAT DISKCACHE optional, but that generates several problems. Therefore, the recommendation is still there, but you can just ignore it and add its value to the HPFS cache. This only applies to Entry server configurations using OS/2 SE HPFS on all drives. FAT (and DISKCACHE) is optional for Advanced server configurations. 6/8/93 ----------------------------------------------------- As always, your notes and comments are welcome -- suggestions, too. I can be reached on PRODIGY (BCJS75A or JUMP COMPUTER CLUB, see OS/2 topic, ASK IBM LAN subject.) Or TOMGORDY at AUSVM1 for PROFS users. Internet TOMG@VNET.IBM.COM TomG