|
|
|
BETA RELEASE ——————————— INSTALLATION NOTES
You can install the NB10 beta on either a 64-bit or a 32-bit version of Windows, whether XP, Vista, or Windows 7. If you earlier installed the “alpha” version of NB 10, see the note at the end of this page.
NB 10 ONLY If installing Nota Bene on a machine on which no earlier version of NB is installed, the only decision you need to make is the name of the folder in which NB 10 should be installed. Our default, as with earlier versions of NB, is \NBWIN, but you can install into the Program Files or other folder if you prefer, subject to the qualification below.
If you have an earlier version of NB installed on another machine, and want to access files and Ibidem databases from it as you move to your new computer, you can:
If you cannot copy the folder from the old system to the identical location on the new system, you need to do a regular install (simply choosing the folder where you want NB 10 to installed) and then:
FULL INTEGRATION OF NB 10 & NB 9 SAME INSTALLATION FOLDER, AND SAME DATA FOLDERS If you want to start using NB 10 in such a way that you can (a) access your existing files and databases without needing to either move or copy them, or do other setup, while at the same time (b) retain the option of using NB 9 for these same files and databases, you can do so by installing NB 10 into your current \NBWIN folder (or the folder in which NB 9 is already installed if you chose to install it into a different folder). After having done so, you can, based on needs or preferences, simply select which version you want to be using at a given time by clicking on the appropriate shortcut: • The NB 9 shortcut already on your desktop starts NOTABENE.EXE • The NB 10 shortcut created during the NB 10 installation starts NB10.EXE (if for any reason this is not created automatically, you can create it as you would any shortcut, pointing it to this NB10.EXE program) Note that the default icons for these shortcuts are different, so you can easily distinguish between them. (The NB 10 icon is a black “NB” on a red LED circle.) This is the simplest installation, and the most versatile, since all of your existing files, along with the Ibidem and Archiva databases, will be immediately accessible, without requiring any additional configuration. And you’ll be able to run either NB 10 or NB 9 interchangeably, sometimes using one, and sometimes using the other, depending on your needs and preferences. If your version of NB 9 is installed on a virtual machine (for example, XP Mode under Virtual PC), installation into the same folder is not an option (well, technically it is, but it would waste to run the version of NB that runs natively on 64-bit Windows in a virtual box). But you can still achieve the same benefits (accessing the same files, and running either one or the other) by following the steps under “Option 3: Linked Integration” below.
SEPARATE NB 10 & NB 9 DIFFERENT INSTALLATION AND DIFFERENT DATA FOLDERS If you want, for whatever reason, to have a completely separate installation of NB 10, you can install it into a different folder entirely, and have it access different files. To retain such full separation, you will need to make copies of your files, and your Ibidem databases, in new folders either underneath, or independent of, the NB 10 installation folder, and access them from this new location. (You will need, however, to tell NB 10 where the Ibidem databases reside, by going to File, New Database, and then clicking the Add Existing button.) This option might be of interest to you if you knew that you wanted to work in NB 9 for a while longer, but also wanted to have NB 10 around to experiment with. (You could also do this by choosing Option 1, but this second option keeps your data files totally separate, letting you experiment with the beta while leaving your working documents intact.) But the most common reason to choose a separate installation is because (a) your version of NB 9 is installed in a virtual machine, and you want to install NB 10 on the main, host, operating system, without (b) having to think about how the two systems interact, and without needing to reconfigure NB 9 in any way, both of which are required (but only during the setup stage) with the “Linked” option that is described next. If you are running in this mixed environment, the first step is to choose the NB 10 installation folder on the host machine. This can be anything you like. Indeed, it could even be \NBWIN on the host machine, since this is different than the \NBWIN folder on the virtual machine that runs NB 9. (If you are used to, and prefer, NB’s default setup in which the program is installed in its own folder — and not under the “Program Files” equivalent used by most other programs — and the NB data files are stored under that program folder, you might find this to be the best option, since it won’t require reconfiguration when you reach the point where you are using NB 10 for all of your work. Or you may find this too confusing, or simply prefer to install NB where other programs are installed.)
LINKED INSTALLATION OF NB 10 AND NB 9 DIFFERENT INSTALLATION FOLDER WITH SHARED DATA FOLDERS There’s another option between full integration and full separation, and that is to install the programs into different folders, but set them up so that they access the same data. This is easily done since version 10 lets you open files from anywhere, including from network drives (without requiring, as in version 9, that you first map them to a drive letter). This means that you can, even with an installation of NB 10 into a different folder, simply access those files from their version 9 location, without needing to make copies of them. The same is true of your Ibidem databases, although you will need to first add them to the NB 10 Ibidem menu by going to File, New Database, and then clicking the Add Existing button and filling in the requested information. This setup may be only a preference if your current version of NB 9 is running directly in the host operating system, but it becomes a virtual necessity (although option 2 above is still available, of course) if (a) NB 9 is running in a virtual system, and (b) you don’t want to also install NB 10 in that same virtual system. (You can certainly do even this, to be sure, but this would defeat one of the main advantages of NB 10,namely its ability to run outside of virtual mode; if you nonetheless do decide to install NB 10 on the virtual system, both options 1 and 2 above are available.) If this linked installation involves NB 10 and NB 9 on the same operating system, you’re largely ready to go after adding your Ibidem databases to the Ibidem menu, as described above. But if this installation involves versions of NB installed on what are effectively different machines (with a virtual machine running NB 9), some additional steps are required. The superficially simplest solution is to leave the data on the virtual machine, and have NB 10 point to that data. However, there are significant drawbacks to this: Not only (a) can it be difficult to configure the network settings on the virtual machine to enable the host machine to access the C: drive of that machine (if you want to do this, you will need to consult some IT specialist rather than asking us for help), this solution (b) means that you always need to start the virtual machine simply to run NB 10, something that you’ll probably not want to do. The alternative, while it takes more time initially, is a much better option, both in the short-run, and even more so in the long-run. This involves (a) moving all your NB 9 data from the virtual machine to the host machine, (b) configuring NB 10 on the host, and (c) reconfiguring NB 9 so that it can access the moved data. Here’s how to proceed: 1. Copy the entire Nota Bene folder (normally, \NBWIN) on the virtual machine to the same location on the host machine (this will normally be in the root of the host machine’s C: drive) 2. Then install (or, if you already did so earlier, reinstall) NB 10 into that same folder on the host These two simple steps will let you start using NB 10 with the same system defaults that you set on your version of NB 9, now updated with new NB 10 features. The last set of steps involves updating the NB 9 configuration to account for the moved files. You can still use NB 9 without making any of the following changes, but if you don’t, NB 9 will continue to operate on the files on the virtual machine, rather than the new copies on the host machine. There’s nothing wrong with that, but it does mean that NB 10 and NB 9 will be working with different data. To integrate the data of the two versions: 3.1. If you have not already done so, the first step is to make the host machine C: drive visible to the virtual machine. To do so, go to My Computer in the virtual machine, select Tools, and then Map Network Drive. In the “Drive” box, select a drive letter to be used for the C: drive on the host (the main 64-bit Windows machine), such as “H” for host or “X” for Extended (you cannot select C:, since that is the name of the main drive on the virtual system). In the “Folder” box, type “\\tsclient\c” (without the quotes). Once you click “Finish” to accept the new settings, you will be able to access the main C: drive on the host computer by using that drive letter. 3.2. Next, start NB 9, and go to Ibidem, and click File, Maintain Database. Select the first database that you regularly use, make a note of its data (Short Name, Description, Filename, etc.), and then Remove it. Close this dialog (confirming acceptance of your changes), and go to File, New Database, click Add Existing, and add the same information for the database, changing only the drive letter of the location from the earlier C: to the drive letter you selected as the name of the C: drive on the host machine (for example, H: or X:). Repeat these steps for all databases that you use — if you don’t ever modify or really use the shipping Tutor, Samples, or Ex Libris databases, you can continue to access them from their location on the virtual drive, and thus not change them. (Alternatively, if you can remember all the data for all the databases, you can Remove all of the existing databases at one time, and then re-add them in sequence. In NB 10, by the way, this process is much easier — there’s a new “Update Location” button right on the File, Maintain Database screen which lets you change the location without removing and re-adding databases —, but this is not available in version 9.) In any case, after these changes, you will be able to access the version of the database that has been moved to the C: drive of the host from NB 9 in the virtual machine. Note that you should not simply add another copy of the database with the new location, but should replace the existing entry in the Ibidem menu with the updated one. If you don’t do so, and retain both, papers that reference the database will continue to use the existing version on the virtual drive. 3.3. If you want to work on the same files in both NB 10 and NB 9, you’ll need to start calling files in the latter program (NB 9) from the host drive, rather than from the virtual drive — as long as you point the NB 9 File, Open dialog to the new host drive, you can open the same files that are you can open in NB10 using NB 9. However, when using NB 9, until the list of recently opened files on the main File menu (those opened by using File, followed by a number from 1 to 9) is updated with files from the new location, you will need to open them using the File, Open dialog (or via the command line), making sure you are selecting them from the new mapped drive. (There’s no harm in opening files from the old location, but you’ll be working on a different version than you will when opening those same files in NB 10.) 3.4. There is one other issue related to opening files: Any time there is a list of files saved within the program, such as in the list of files shown on the File menu (Alt+F, followed by a number), or in the Quick Open dialog, or elsewhere, the two programs need to keep separate lists. This is necessitated by the fact that NB 9 could handle long file names only by utilizing Windows “8.3” short file name routines behind-the-scenes, as it were, whereas NB 10 manages them without such conversion. As such, NB 10 does not save the 8.3 information when it writes out the respective lists, thus rendering the lists that it writes inaccessible to NB 9. Among other things: • Files opened in NB 9 (even if they are retrieved from their new host-drive location, as noted above) whose names are then saved in the most-recently-used file list will not show up in the list of files opened in NB 10, and vice versa. • NB 10 and NB 9 keep fully independent Quick Open files lists. • Similarly, NB 10 and NB 9 have separate Log and Resume lists. • Separate versions of manuscript control files need to be created for each version, both because (a) manuscript files in NB 9 now need to point to the shared files on the host drive (again, if you don’t do so, you’ll be incorporating the versions only on the virtual machine, and thus miss out on any edits made in the versions that are edited in NB 10), and (b) because NB 10’s manuscript control files utilizes long file names. You’ll find other places where similar issues are in play. 3.5. A special note about Orbis is in order. As long as Orbis is not supported in the beta (this is true of the first release, but we hope that this won’t be true in subsequent releases), and as long as you are not making edits to the files that are included in the textbase, there is no need to immediately rebuild them using the version of the files on the mapped host drive. However, if you do edit the Nota Bene files, then you should probably rebuild the textbase using the files from the new location. (You can save the management files on the virtual drive, or choose a folder on the mapped host machine drive, since when Orbis is incorporated in NB 10, you’ll probably need to rebuild the textbases in any case). While these and other adjustments will need to be made to NB 9 to fully integrate it with NB 10 (although, as noted above, you can certainly use option 2 instead, and not worry about any of this), the steps are relatively straight-forward, and should not be difficult. By implementing them now, you will (a) be able to choose, on a case-by-case basis, which version of NB (10 or 9) you want to use at a particular time, and (b) have done all the work in advance, so that when you finally start doing all your work in NB 10, you should find that there’s no additional setup required.
If you want to run both NB 10 and an older version of NB at the same time, please contact sales@notabene.com, and they can give you access to a copy of NB 9 which you can install over the earlier version that you are running. This would let you choose any of the three options in the preceding section.
However, it should also be possible to run both versions at the same time, as long as you understand that files open (and Ibidem records being edited) in one version cannot be opened in the other version until they are closed in the first one. (For example, trying to open a file in NB 9 that is already open in NB 10 should give you a “Sharing Violation” error in version 9. Until you close the version in NB 10, you can only open it as Read-Only in NB 9.) In order to run both versions at the same time, however, one minor adjustment needs to be made. In order to understand this, it’s important to learn how NB works: While there are lots of supporting modules, the core of both NB 9 and NB 10 involve two basic programs: 1. A “launcher,” which starts Archiva, checks for updates, and otherwise manages the program 2. The actual program that does all the things that Nota Bene does In NB 10, the launcher is named NB10.EXE, and the program proper is NB10ED.EXE. In version 9, the launcher is NOTABENE.EXE, and the program itself is NBEDITOR.EXE. The shortcuts created during installation always reference the launcher (that is, either NB10.EXE or NOTABENE.EXE), not the program proper (NB10ED.EXE or NBEDITOR.EXE). As noted, this is to allow Archiva to load and updates to be checked. Among other things, the launcher also checks to see if Nota Bene is already running; if it is, it goes to the already open version, rather than loading a separate instance. This means that the only way to start another version of Nota Bene is for the subsequent version (the second one that is invoked) to start the program proper, bypassing the launcher. In short:
• If NB 10 is already running, you need to start NBEDITOR.EXE to run NB 9 Note, however, that you may encounter some minor oddities when running the two programs at the same time. For example, if you create a file in NB 10, and don’t save it regularly, so that it creates an autosave version that is more recent than the named version, and then open NB 9, you may be presented with the dialog that informs you that there is a more recent version of the file that is still open in NB 10.
Alternatively, of course, you can install the beta over the existing alpha — the beta will work fine even if installed in the \NB10ALPHA folder.
|
