2.0
Nintendo 64 Developers Newsletters will be published periodically, as needed. These feature software and hardware system anomalies, which have been discovered, and their solutions and/or work-arounds. Development tips will also be included.
We have discovered that some of the development disks (blue disks) included with the N64DD Development System have been formatted incorrectly. Disks with this problem will operate differently from normal disks when they are read while not being used. Error 23 will occur when normal disks are read while not being used, but problem disks will hang up an application.
The problem disks work the same as normal disks, and once they are written using the development tools, they will work without problems as long as they are used normally.
However, some disks can have unused portions different from normal disks, even once they have been used. Problems may arise when you attempt to use this portion in the future.
To counter this problem, determine whether your disks have the problem, and if so, use the dn (disk normalizer) tool to correct the formatting. We apologize for the inconvenience.
The dn tool rewrites portions of the disk that are unrelated to the user area. If you use it on a disk that contains important programs or data, the contents will not be deleted. Please use the tool freely.
Normal and problem disks can be identified by the number printed on the front of the disk (where the index label is attached). Disks with the following numbers were formatted incorrectly:
dn operates on the N64 and is stored in /usr/lib/PR/ when Development Environment 2.0J is installed. Because it is a N64 program, it can be executed by transferring it to the emulation ROM using a tool such as PARTNER, or by burning it into the flash ROM.
The procedure for executing dn with PARTNER-PC is shown below (for the Partner-NW version, substitute /usr/lib/PR/dn for c:\ultra\usr\PR\lib\dn)
Q1. I can't tell if the disks I've got are normal.
A1. If the inserted disk is normal, dn won't do anything. Consequently, if you're not sure whether the disk is normal or not, try running dn with the disk.
Q2. I have a problem disk, but I can't remember if I've already run dn or not.
A2. dn can be executed any number of times. If you don't know whether or not you've already done it, run dn again just to make sure. If dn has already been run for that disk, it will be determined to be normal on the second and subsequent tries, and dn will complete processing without doing anything.
Q3. I have a disk on which I've already written important programs and data. Won't they be deleted if I run dn?
A3. It's OK! Since dn rewrites the portions which are unrelated to the user area, none of your content will be deleted, even if you run dn on a disk that has already been used.
Q4. Does this mean that I could run dn on all of my disks just to make sure?
A4. Yes. It only takes a moment to run dn and you can process multiple disks, one right after the other. It can be used on normal disks without any problem, and important programs and data which have already been written will not be deleted. If it is difficult to tell the normal disks from the problem disks, don't hesitate to run dn on all of your disks.