If you're looking for something less technical, check out the User's Guide.

IF YOU ARE NOT A SERVER ADMIN, DO NOT BOTHER WITH THIS PART OF D2. Clients will be getting their own programs to use.

Features include the following items, each of which may or may not be working during the development/testing phase of the application. Unimplemented features are marked with and asterisk:

• DeMONS/2 supports BOTH NR4 servers *and* NR2K2 servers running simultaneously (as of v0.0.2.0).

Windows 9x users should check out the special section I've written just for them (a couple sections below this one).

NOTE: D2Scrub needs to be done for both NR4 *AND* NR2K2.

• When I attempt to add a race to the schedule, there are no tracks to select. Why?

  You have to run D2Scrub.EXE to massage the track INI files. Refer to the section titled "For Windows 9x/ME Users".

• In the Launcher, when I hit the START or START ALL button, the schedule goes immediately from a blue flag to a checkered flag. Why?

  There are any number of reasons this could occur. Check the following items:

  • If you're using the specific date/time timing loop, the race's start date/time may have already passed. D2 skips late races.
  • Make sure you ran D2Scrub before runing D2Config.
  • If you're registering your server on WON, make sure you have specified a userID and password for WON for the player.

• Client Name -- This is the name you want to assign the *machine*. This name will eventually be what everyone sees if your client machine is connected to a nanny server (like RaceServer.net). If you have multiple installations of Nascar Racing, each installation of Nascar Racing needs its own copy of D2 running, and therefore, each copy of D2 should have a different machine name.

• Path to NR4 -- This field contains the path to NR4. You will notice that there's a button with an ellipse ("...") on it. This button will allow you to browse around your system to find the sim path. If you want to take the easy way out, click the REGISTRY button next to this field. It will attempt to pull the sim path from the registry - NR4 must have been installed from the CD for this to give you the correct path. If after clicking the REGISTRY button, you get the path "C:\\", you must use the browse button to find the sim, because D2 couldn't find the required registry key.

• Path to NR2K2 -- Same as the path to NR4, except pertaiuning to NR2K2 (new feature in v0.0.1.5).

• Current Hosts -- This is a list box that contains all of the hosts currently configured for this client machine. Up to ten hosts can be supported by a given client machine (D2 installation).

• ADD button -- Adds a new host to this machine. This buttons displays the Host Configuration dialog box and populates it with default data. As of v0.0.1.2, the previous limitation of 10 hosts has been removed.

• DELETE button -- Deletes the selected host from this machine

• Favored checkbox -- This checkbox is checked if the currently selected host is a favored host. Refer to the Host Availablility tab for more info on this setting.

• CONFIGURE button -- Configures the selected host. This buttons displays the Host Configuration dialog box and populates it with previously entered data for the host.

• SCHEDULE button -- Creates a schedule for the selected host. This button displays the Host Scheduler dialog box.

• Default Sim -- This radio button group allows you to specify whcih sim will be the default sim for all newly created hosts. Once you've begun configuring your new host, you will be given an opportunity to pick the sim whenever you choose to do so (new feature in v0.0.1.5).

• Allow Remote Admin -- Allows the server admin to remotely configure this machine (not yet implemented).

• Admin password -- The password is needed to be able to admin the machine remotely

• Admin port -- This is a base port value. To admin the *machine* the port value entered here is used for communications. To administer individual hosts, this value is incremented by 1-10.

• Allow public setup -- Permit "the public at large" to setup hosts remotely. One one race at a time will be permitted if a host is configured this way.

• Public setup password -- The password is needed to be able to setup a race (or schedule) on the host remotely.

• Public setup port -- This is a base port value. When setting up hosts, this value is incremented by 1-10.

• Connect To Nanny Server -- Connects to a nanny server (like RaceServer.net). A nanny server is a server that receives results and statistics, as well as managing the race list that public users see.

• IP Address -- IP address of the nanny server

• Port -- Port used to communicate with the nanny server

• Processor -- If you're running D2 on a multi-processor machine, you can choose which processor all of the D2 components will run on. If you change this value, you may have to shutdown and restart D2 for it to take effect. To see if it works, use Task Manager to see what CPU the D2Config.exe process is running on.

• CORE.INI SETTINGS button -- I may allow the server admin to change some CORE.INI settings. At this time, this may not be available remotely.

• FRESH START button -- This button allows you to manually delete all D2 ini files.

Server Settings tab

This tab contains administrative settings for the host. The available fields are as follows:

• Host Name -- This is the host name that appears in the D2 Configuration dialog box, as well as on remote drivers' machines in their race list. This is a required field. It defaults to "New Host" if this is a new host being added to the client machine. This field can be up to 15 characters long.

• Server Location -- This field contains the server location info (example: "San Antonio, TX"). There is no default value.

• Connection Type -- This field is used to describe the type of connection this host is using on the internet (example: "Cable modem/256k up"). This is not a required field, and there is not default value. Maybe this field should be moved to the first dialog box (since it can be assumed that the same connection is used for all hosts on this client machine).

• Boss Password -- This field allows you to specify a password that can be used to send commands during a race. Beginning with NR2K2, boss passwords allow less comprehensive control over the server. This was done to curb the tendancy for some butt-holes to perform a hostile takeover of a server. See the NR2K2 README.TXT file and/or SERVER.TXT file for more information on the new capabilities of bosses and admins.

• WON User ID -- This field allows the server to log into WON. I *think* this user ID also determines the player folder name. Anyone know for sure? At this time, I think this will only need to be entered if you want the host to shjow up on WON.

• WON Password -- This field is part of the WON logon. At this time, I think this will only need to be entered if you want the host to shjow up on SIERRA.

• Admin Password -- This field allows the server admin to specify an admin password. Beginning with NR2K2, boss passwords allow less comprehensive control over the server. This was done to curb the tendancy for some butt-holes to perform a hostile takeover of a server. See the NR2K2 README.TXT file and/or SERVER.TXT file for more information on the new capabilities of bosses and admins.

• Processor -- This field allows you select a processor on which to run this host's instance of Nascar Racing. This field is only available if you're running on a multi-processor machine under Windows NT or Windows 2000.

• Nascar Racing runs in normal priority mode -- This option causes Nascar Racing to run with the "-kh0" parameter, and forces the sim to run with normal system priority. You should use this option with caution as it could degrade your ability to support a higeher number of drivers. If more than one host is displayed in the D2Launcher window, this setting will be automatically overriden to be ON for each host. This will allow each host an equal share of CPU cycles, and is necessary when running multiple hosts.

• Run minimized -- This checkbox will allow you to start Nascar Racing in a minimized state.

• Selected Sim -- This radio button group allows you to select the sim with which to run this host. If you select a different sim, you MUST re-specify your player folder. If D2Config detects that only one sim is installed, it will automatically select that sim and this radio group will be grayed out. (new feature in v0.0.1.5). If you change sims in a host that has a schedule already built, the schedule will be cleared out and you'll have to start the schedule from scratch. You will be given an opportunity to change your mind before D2 cleans the schedule. You are also forced to re-select a player folder.

• Player Folder -- This is the player folder that is associated with this host. Each host should have its own player folder unless you’re going to be testing the Host Availability feature. See "Selected Sim" item above. This is a required field.

• Create Alternative Results File -- This checkbox will make DeMONS import the Nascar Racing-generated results file and convert it to a format of your choice (based on a template file that you provide).

• TEST button -- This button allows you to test your template file against a file I created by exporting results after an Nascar Racing race. This makes it much easier to make sure your template file is going to result in correct output.

• Additional Commandline Parameters -- This field allows you to add commandline parameters that might come up in future revisions of the sim. This gives you the opportunity to work around new features that D2 does not yet support until I can update D2.

• Invite Lists -- I plan on giving the admin the opportunity to choose a source for invite lists. This is all tentative.

               Host-specific - a list contained in the player folder for this host.

               Local master - the list contained in the Nascar Racing folder.

               Remote Nanny - allows the nanny server to control the invite list.

               The same options are available for the muzzle list.

• Weekly Host Schedules -- On the right side of this tab, you will find this button. Clicking it will cause D2Config to display a dialog box that presents a graphical representation of the weeks usage by all currently configured hosts. This is done so that you can detect possible overlaps of usage by the same host on the same day.

Connections tab

This tab contains connection information for the current host. The following fields are available:

• Server Port -- This is the port that this host uses allowing remote connections by drivers. Make sure you read the info on the dialog box concerning this setting. All hosts are keyed off the assigned player folder. If you create multiple hosts that use the same user ID, each of these hosts can use the same net server port value as long as each host uses the player folder on DIFFERENT DAYS. DeMONS makes no attempt to ensure that you haven't screwed up your scheduling somehow, so tread carefully.

• Connect To Nanny Server -- This allows you to omit/include this host in the Nanny server race lists. If unchcekd, you have essentially elected to create a private host that people must know the IP address of the port.

• Log Sim Communications Errors -- Logs sim communications errors (connection problems for drivers)

• Log Sim Connection Errors -- Logs TCP/IP errors

• Log DeMONS Errors -- Logs D2 functional errors

• Max connections -- Maximum number of connections allowed (includes AI cars if allowed)

• Max latency -- If checked, the latency is restricted

• Latency ms -- Max acceptable latency millisecs

• Allow IPX -- Allows IPX connections

• IPX Cars -- Number of connections allowed through IPX.

• Allow TCP/IP -- Allows TCP/IP (non-WON) connections

• TCP/IP cars -- Number of connections allowed through TCP/IP.

• Use WON Servers -- Registers the server on SIERRA - may disallow other connections (IPX and TCP/IP), but I'm not sure.

• Allow AI Cars -- Checking this box allows you to specify opponent strength and how many AI cars to allow in all races on this host. If you specify AI cars, the maximum number of connections may need to be adjusted so that the number of connections realized does not exceed your bandwidth limits. Nascar Racing doesn't automatically reduce the number of AI cars as more people join the race (I consider this to be a deficiency within Nascar Racing).

Lists tab

This tab allows you to build this host's invite and muzzle lists. there are two parts to this tab, the invite side (on the left), and the muzzle side (on the right). Both sides work identically to each other.

• Invite List (or Muzzle List) -- Shows a list of people that are currently in your invite (or muzzle) list for this host.

• ADD button -- Adds the name that is currently typed in the edit field above the button.

• DELETE Button -- Deletes the name that is currently selected in the list box.

• Use Invite List checkbox -- Currently disabled because I don't know if I'm even going to make use of it.

• Use Muzzle List checkbox -- Currently disabled because I don't know if I'm even going to make use of it.

Host Availability Tab

This tab allows you to specify what day(s) of the week that the host will run. The settings on this tab have NO EFFECT of hosts that run with the specific date/time timing style. The default value is "Every Day". To select specific days, de-select "Every Day" and select the desired day(s). In order to completely turn on a day, you MUST specify a remote admin password. I assume that if you use this feature, it’s for the benefit of specific leagues or groups.

The addition of this feature eliminated the restriction on using the same player folder for more than one host. It is COMPLETELY UP TO YOU to make sure that the same player folder is not in use at the same time on the same day. With that in mind, I added a method for you to identify possible conflicts.

• Favored Host -- A "favored host" is a host that will cause all other currently running hosts to stop running so that the Nascar Racing session associated with the favored host can use all available bandwidth. If any other Nascar Racing sessions are running, they will be terminated by the launcher. If any hosts are runnning (waiting for their next race to start), they will be paused. All of this happens one minute prior to the favored host running, and happens with NO WARNING to the people that might be driving in the races that are terminated. Once the favored host's race is over, all hosts that were paused are restarted. Any hosts that were not running at the time the favored host kicked in will not automatically be started. Checking this checlbox makes a host "favored" by the launcher.

Timing tab

This tab allows you to set schedule timing information for the current host.

• Continuous Loop -- Runs the next event x minutes after the previous event ends.

• Daily Time -- Runs the next race at the time specified on the next calendar day. Consecutive runs are not available with this timing, and the field will be disabled on any data entry tab in which it appears.

• Specific Date/Time -- Runs races at specific dates/times. The date and time must be specified for EVERY race. Consecutive runs are not available with this timing style, and the field will be disabled on any data entry tab in which it appears.

• Limit Schedule -- This section allows you to specify the time frame in which to run races, and is only available when "Continuous Loop" is selected as your timing style.

• Stop At End -- Terminates the schedule after the last event has been run.

• Shutdown At End -- Shuts down D2 at the end of the schedule (this will probably be deleted).

• Start Schedule At Startup -- Automatically starts all host schedules when the launcher is started up.

• Remember Last Race -- Remembers the last race run in this schedule (this might be deleted in the future).

Default Race tab

This tab allows you to set default race settings for this host. Default settings used to populate this tab are the way *I* would configure a league race (more realism than you see in pickup races on Sierra).

I'm not going to go into specifics on this tab right now, because I'm assuming most of you know what these settings do. Some specific issues are as follows:

• There is currently no "CTS" add-on, but I'm assuming it will be coming sometime in the future. This assumption is not based on fact or even rumor that Papyrus will be producing a CTS add-on. I'm simply assuming they will, and I'm preparing for it, so please don't ask me for the status of it.

• Fixed Setups -- If you specify that an event uses a fixed setup, you MUST select a setup file when you add a new event to your schedule.

Read Me tab

This tab explains some theories I have about bandwidth and hardware requirements when running an Nascar Racing host. No data is requested here.

Other Host Info

At first, the program created a file called D2SCHEDULE.INI in each player folder (this file contained schedule info for the host). However, the implementation of the Host Availability feature forced a re-design. The problem is that each player can now be used by multiple D2 hosts, and having a single schedule file would cause conflicts. The obvious solution was to provide a different schedule file for each host. This obviously forced me to consider ways to come up with file names that were guaranteed to be unique.

Beginning with DeMONS/2 version 0.0.1.2, each schedule filename is made up of a "universally unique identifier". Called UUID's in programmer speak, these objects are programatically determined through a single function call to the Windows API. Enough people complained about this that I changed the file naming beginning with v0.0.1.5, so that the date and time the file was created would be used for the name.

• ADD button -- This button allows you to add one or more races to the schedule. All newly added races start out with the track as Atlanta, and with whatever default settngs you specified for the current host. When you click the Add button, you will automatically be taken to the Race Setup dialog box.

• Quick Schedule button -- This button allows you to add tracks in specific groups. A new dialog is displayed allowing you to select either All tracks, specific types of tracks (speedways, road courses, etc). If you selected a type of track to install, when you click the OK button in that dialog, D2Config will automagically add all of the selected tracks to the current schedule without you having to lift a finger. Of course, all tracks added this way assume the default race settings, so you'll have to edit each race that doesnn't meet your requirements. (new in v0.0.2.3)

• Configure/View button -- This button allows you to configure (or view the settings for) the currently selected race.

• Move Up button -- This button allows you to move the selected race up in the list box. (new in v0.0.2.3)

• Configure/View button -- This button allows you to move the selected race down in the list box. (new in v0.0.2.3)

• Delete button -- Allows you to delete the currently selected race from the schedule.

• Delete All button -- Allows you to delete the all of the existing races from the schedule.

General tab

This tab allows you to configure settings that are not directly related to "racing". At the top of this dialog box, you'll notice several static fields which show information about the selected track. Beyond that, the following fields are provided:

• Track List -- This is a list of tracks that are currently recognized by Nascar Racing. If you add a track to Nascar Racing, it will automatically show up in this list. If this list is empty, read the section entitled Windows 9x/ME Users.

• Vehicle Type -- This setting allows you to select what type of vehicle to use in the race. If/when papyrus releases a CTS expansion pack, I will enable this setting.

• Skill Ranking -- This setting allows you to restrict entry according to a driver's current rank. This setting is applied to ALL track types, regardless of what track type is selected. To disable rankings, make both values 0.

  In addition to the ranking requirements, NR2K2 allows the server admin to restrict acces to the server according to the driver's LPI (laps per incident). I haven't seen anything regarding the valid upper range for this field, so I set an arbitrary limit of 100 as the maximum possible value. If anyone knows the true maximum, I'll be happy to make the necessary adjustments to the code.

• Timing -- If you elected "specific timing" during host configuration, these fields will be enabled, and you are required to specify a date and time to run the race. Caution should be used because D2 does not verify that events won't overlap. However, D2 will ignore late events and wait for the next one. Further, D2 expects races to occur (in time) consecutively, but doesn't ensure that you specified correct dates and times in relation to existing events. In other words, it's up to you to keep the dates and times straight in your head.

• Weather -- If you check the "Realistic Weather" box, the four fields in this group will be disabled (and the settings in those will be ignored by Nascar Racing). If the "Realistic Weather" box is not checked, you will be able to specify each setting.

• Consecutive runs -- You can tell D2 to run a given event over again up to 99 times. This field is disabled when you have selected the "daily" or "specific time" timing styles.

Environment tab

• Race Settings / Race length -- Enter the desired race length (percentage). I was considering calculating the number of laps as well. Comments?

• Race Settings / Race password -- This is the password everyone will need to know in order to enter the race.

• Race Settings / Run practice session only -- This checkbox allows you to specify that this event does not progress beyond the practice session. The way this is determined is by the duration entered in Session Duration / Practice Time field. One minute before the practice session time has expired, the Launcher will send chat messages warning the drivers that the session is about to end. These warnings come 1 minute, 30 seconds,and 10 seconds before the sim is forced to shutdown.

• Session Durations / Practice time -- This is the number of minutes to allow for practice.

• Session Durations / Warmup time -- This is the number of minutes to allow for the warmup session.

• Session Durations / Post-race time -- This is the number of minutes to wait before shutting down the sim after a race is over.

• Damage -- Select one of the three settings for the damage model.

• Realism -- This section contains numerous settings that affect the realism of the race. I think they're all self-explanatory, so I won't go into detail on each setting.

• Administrative / Save race results -- Tells Nascar Racing to save race results. As of the latest patch, Nascar Racing has problems with saved results (times not saved correctly and double saving of information.

• Administrative / Save replay -- Tells Nascar Racing to save the replay. Make sure you have adjusted your replay settings in the CORE.INI file to allow for longer replays.

• Administrative / Save chat log -- Tells Nascar Racing to save the chat log from the race.

• Administrative / Use invite list -- Tells Nascar Racing to use your invite list.

• Administrative / Use muzzle list -- Tells Nascar Racing to use your muzzle list.

• Fixed Setups -- If you specify that an event uses a fixed setup, you will be allowed (and in fact are REQUIRED) to select a setup file. The combo box will contain all setups (in alphabetical order) that exist in the Nascar Racing\tracks\track_name folder, as well as all the setup files found in the players\player_name\setups\track_name folder. The tracks found in the Nascar Racing tracks directory are displayed between the "<>" brackets like so:

      <fast.cup.sim>

  Setups found in the player setup track folder will appear without the brackets as shown in the sample below:

      My Special Setup.cup.sim

  If this is the first time you've specified a fixed setup file name for this race, D2 will try to default to one of the three default race setups in the following order:

      <fast.cup.sim>

      <intermediate.cup.sim>

      <easy.cup.sim>

      <qualifying.cup.sim>

  If none of those files are found in the combo box, it selects the first file listed. If no setup files are found, D2 will not allow you to used fixed setups for that track on that host (the checkbox and combo box will/should be disabled).

Experimental tab

This tab contains settings that are of an experimental nature. As of v0.0.0.16, these settings don't do anything, but they might in a later release.

• EDIT HOST button -- Allows you to re-configure a host while the launcher is running. You can only edit one host at a time, and while that host is being edited, it's schedule is shut-down (if it was previously running). It's schedule will be re-started automatically after you have finished edit it (if it's schedule was running previously). (new feature in v0.0.1.5)

• START button -- Starts the select schedule.

• STOP button -- Stops the selected schedule. You will be asked if you also want to stop the sim session (if running) associated with the host.

• START ALL button -- Starts all of the listed schedules.

• STOP ALL button -- Stops all of the listed schedules. You will be asked if you also want to stop all currently running the sim sessions associated with the hosts.

• CLOSE button -- Closes the launcher. You will be asked if you also want to stop all currently running the sim sessions associated with the hosts.

The Flags in the Host Schedule List

The launcher dialog shows all hosts in a list. Each host has a flag icon next to the host name to signify its current state. Here's what they mean:

• Blue Flag -- Indicates that the host's schedule is not currently running.

• Yellow Flag -- Indicates that the host's schedule is running, and that it's waiting for the time at which it should start the next race in the schedule. The 3rd column indicates the approximate time at which the race will start.

• Black Flag -- The host doesn't have a schedule to run. In this case, the track and start time columns will reflect appropriate info.

• Red Flag -- There was an error in the launcher associated with the host.

• Green Flag -- A race is currently running for the host.

• Checkered Flag -- The schedule has completed and there are no more races to run. This flag also appears when you manually stop a schedule using one of the buttons.

• Blue Flag with Yellow Stripe -- Indicates that the host/schedule was shutdown in order to allow a favored host to run a race. (new in v0.0.1.4)

This component is not yet available.

This component is not yet available.

This component is not yet available.

Lastly, D2League does not strict you to using the Nascar points system. You can use F1's weird little points schedule, or you can even make up your own. Instructions appear below.

• Original Results File Location -- This group of radio buttons allows you to selecte from one of three possible locations that could contain results files exported by NR4 and/or NR2002. The first two selections will probably be used most often and are self-explanatory.

  The third option allows you to manually specify a directory that contains exported results files.

• Points Schedule -- This option allows you to select what kind of points schedule to use when scoring races. Refer to the section "The Points.INI File (below) for more details.

• Delimiter Character -- Use caution if specifying a different delimiter characetr. Some of the user ID's I've seen on Sierra contain some off-the-wall characters. I can't remember ever seeing a "^" so unless your database importing utility just absolutely cannot handle it's probably that character as a delimiter, I suggest that you leave this value alone.

• Delimited File Extension -- This field allows you to specify the file extension for the delimited text file.

• Delimited Files Destination Folder -- This field allows you to specify a folder in which to place delimited text files created by D2League.

• Results Files Destination Folder -- This field allows you to specify a folder in which to place new results files created by D2League.

• Original Results File -- This is a drop-down list which shows all currently available exported results files. If this list is empty, you must click the Configure button to specify a path which contains the expected files.

• TRANSFER TO NEW button -- This button takes the name of the selected exported results file, changes the extension to .txt and .html, and changes the new file names (lower in the dialog to the same name (but with the appropriate extension, of course). This is intended as a time-saving feature in that you don't have to re-type the file name if you don't want to.

• Create Delimited Text File checkbox -- Check this box if you want to create a delimited text file.

• File Name (delimited text file) -- Use this field to specify the name of the newly created delimited text file. DO NOT include the path in this field.

• Template File (delimited text) -- This file allows you to format the delimited text file to include as much (or as little) driver data from the exported file. A sample file (D2Sample.DDT) is provided with the program. While you could go ahead and edit this file yourself, I suggest that you create a whole new file so you can use the sample as a, um..., errr..., sample.

  For details regarding how this file is expected to be used, refer to the appropriate section below.

• Create New Results File checkbox -- Check this box if you want to create a new (massaged) html results file.

• -- Use this field to specify the name of the newly created results html file. DO NOT include the path in this field.

• -- This file allows you to format the html file to include as much (or as little) desired race data from the exported file. A sample file (D2Sample.DRT) is provided with the program. While you could go ahead and edit this file yourself, I suggest that you create a whole new file so you can use the sample as a sample.

  For details regarding how this file is expected to be used, refer to the appropriate section below.

		[SCHEDULES]
		List=NASCAR,FORMULA1,CUSTOM1
		

		[NASCAR]
		SchedID=0
		Name=NASCAR (Official)
		1-10=175,170,165,160,155,150,146,142,138,134
		11-20=130,127,124,121,118,115,112,109,106,103
		21-30=100,97,94,91,88,85,82,79,76,73
		31-40=70,67,64,61,58,55,52,49,46,43
		41-43=40,37,34
		Bonus=5,5,0,0,0,0
		Penalty=0,0,0,0,0
		

• [NASCAR] -- This is the "section name", and the text between the "[" and "]" characters MUST match one of the listed schedules. In this case, it's "NASCAR".

• SchedID -- This ID tells D2League where in the schedule list this schedule is. Notice in the List= line above that "NASCAR" is the first item in the list. Since all lists in programming start with item 0, that's how I do it here. This is referred to as a "zero-based" list. This is CRITICAL to remember when assigning a SchedID to a new schedule section.

• Name -- This is the english name of the points schedule, and is used in several parts of D2League. Put something meaningful here, but don't go nuts typing some long-ass name.

• 1-10 -- This line should contain a comma-delimited string of numeric values. These values are used to award points for finishing positions 1 through 10.

  There are four additional (and similar) fields allowing for points awards for finishing positions 11-20, 21-30, 31-40, and finally 41-43. All of these fields must exist for each schedule section.

• Bonus -- Like the position points discussed above, this is a comma-delimited string of points. The order is important because each position in this string is for a specific bonus item, as described in the order below (from left-to-right):

        Leading a lap
        Leading the most laps
        Pole (fastest qualifier)
        Fstest practice speed/time
        Fastest warmup speed/time
        Most positions gained (hard charger)

  So, if you wanted to have (along with the standard Nascar lap leading bonuses) a 3-point bonus for fast qualifier, and a 5-point bonus for hard charger, your "Bonus=" line would look like this:

  		Bonus=5,5,3,0,0,5

• Penalty -- This is a comma-delimited list of penalty point deductions. It is similar to the bonus points in that the position of the point value indicates a specific penalty, as illustrated below:

        Passing under yellow
        Speeding on pit entry
        Speeding on pit exit
        Unsafe pit exit
        Reckless driving

  Since the sim is notorius for penalizing people at sometimes bizarre and random times, I would recommend that you be cautious in your use of penalty awards.

Note: All template files must reside in the same folder where you've copied D2League.EXE. Further, all Results template files must have a ".DRT" extension.

		D_RACE_DRIVERNAME
		D_RACE_CARNUMBER
		D_RACE_STARTPOS
		D_RACE_FINISHPOS
		

Note: All template files must reside in the same folder where you've copied D2League.EXE. Further, all Delimited text template files must have a ".DDT" extension.

This component is only needed by server admins that are not running Windows 2000. It massages the track-related INI files shipped with the Nascar Racing so that Windows9x/ME can read the files. This program only has to be run once, or immediately after installing Nascar Racing (or a Nascar Racing patch).

But Why Do We Need It?

A little background is probably in order. In order to read INI files, Microsoft was kind enough to provide API functions that can get and set data within these files. When you use these API functions as intended, section names look like this:

		[SectionName]
		

		MyNumberValue=123
		

		[ SectionName ]
		MyNumberValue = 123
		

I originally had no reason to suspect that the INI file API functions that read the data would not be able to read the track files that came with N4. Since I develop and test on a Windows 2000 machine, I was really surprised when problems were reported in this area of the program.

Since N4 can read these files in their "natural state", and since both N4 and DeMONS are both Windows programs, why doesn't DeMONS read it, too?

My only guess (and this is purely speculation) is that the program they used to create the track INI files also has a facility (in the form of a linkable static library or DLL) for reading the files it creates. This means that they are probably not using the Windows API functions to read these files inside N4, because they would have had the very same problems I had.

Your next question is why is Windows 2000 different?

Beginning with Windows 2000, I think they changed the GetPrivateProfileString API function so that it (properly?) handles section names and key values that contain spaces. This version of krnl32.dll is only compatible with Win2K, and won't work on win98 or WinNT (I don't think).

How Does D2Scrub work?

It reads the files in as plain ASCII text, parses the data (removing the undesirable space characters), and re-writes the files using the Windows INI API functions. This makes the INI files compatible with Windows 95/98/ME (and all other versions of Windows as well).

It's not at all necessary to run D2Scrub on Windows 2000, but it won't hurt anything to do so. You can even run it repeatedly and it won't hurt anything.

Why didn't I just make it parse the files on the fly and hide this crap from the user?

Well, I was testing this possibility on my 1.2ghz Athlon 512mb ATA100 machine, and it took a little over 90 seconds to parse all of the files. And I would had to have done that EVERY TIME the files had to be accessed (quite often actually). The way I have it figured is that it's much more reasonable to have the user run this utility one time than to force them to endure a larger memory footprint and longer load times when they're doing something much more important (like running a schedule).

Final Comments

I don't know if Papyrus chose to read/write these files like this, or if it was just an unexpected side-effect of their track development tools, but it sure does annoy the hell outa me.