Once again the Firestorm Project is accepting applications for positions within the team!This invitation is for the Firestorm Gateway Volunteer Groups who work at the Firestorm Community Gateway regions. (This is NOT an application for the Firestorm Viewer or Viewer Support divisions of the project.) This invitation applies to the Firestorm Gateway where we on board tens of thousands of new Second Life Residents every month!This is a volunteer position. (but we do give virtual cookies) ?Do you:– Like to help others?– Want to be someone who makes a difference?– Want to share your talent and energy with a group of like-minded people? – Want to experience a sense of pride and accomplishment?– Have the patience to help new residents with basic fundamental skills or Roleplay?Read on if you are not tempted to run away at this point ? Firestorm Gateway for New ResidentsThe Firestorm Gateway is a Community Gateway for New Residents to Second Life.
![]()
Check that the 32-bit client has been installed. There are two options here. Install the client from the 32-bit Firebird installer. If the defaults are followed the path will be similar to that above c:Program Files (x86)firebirdfirebird21binfbclient.dll. Install the client from the 64-bit Firebird installer. With the Windows installer, it is easy to install Firebird as a service. Firebird 2.1, 2.5: Named Instances. Starting with Firebird 2.1 you can give your instance a name. The INSTSVC tool takes a -name parameter for that, so you can use. Instsvc install -name FB21. To install the service with the name 'Firebird Server - FB21'.
Gateway Helpers provide a welcoming learning environment within General rated regions and give basic fundamental help to residents on any viewer. This includes such things as tips on changing clothes, changing your avatar, getting around second life, finding personal interests and much more. Our prime objective and focus is the New Resident but we help both old and new alike when help is needed. If you are truly interested in donating some of your skills and knowledge to a worthwhile cause, then fill out an application and come see us.
![]()
Firestorm Gateway SciFi and RolePlay.We are looking for volunteers who are SciFi enthusiasts OR volunteers who are RolePlay enthusiasts (or both). There are many different ways a volunteer can be involved. Helping as a Roleplay regular or a RolePlay leader are two of them.
We also need volunteers to give tours of our space station and starship, volunteers to teach new residents to fly shuttles, volunteers to organize games and/or activities at Callahans (such as greedy or poker games), volunteers who like to chat SciFi with visitors, etc. If you would like to volunteer in Firestorm’s SciFi area, please fill out the application linked below.You are welcome to visit the Firestorm Gateway regions at any time if you have not already done so.Thank you for your interest!Firestorm Gateway Team. The Bakes on Mesh release from Firestorm has been long awaited; apologies for that.
This should be considered by all in SL a MAJOR UPDATE, and it is important that all our SL users upgrade to it. This update contains a lot of rendering-related changes from Linden Lab, without which you WILL be running into avatars that look badly broken to you. Even if you don’t intend to use or purchase anything with BoM, you will still need to be able to see BoM items in your viewer. Please take the update. I can assure you we have put this through a rigorous QA process; it’s a great build!Major updates from LL in this update include:– Bakes on Mesh!
See the, the, and the.– Love Me Render! See the on these rendering updates.– Umeshu, a group of bug fixes, tweaks and improvements.– Edit notecards from an external editor.– Ability to duplicate group roles.Firestorm goodies!There are a few new FS-specific features in this release as well like ability to sit on objects from Area search, New Discord Rich Presence, Ghosted attachments now automatically fix themselves after tp, but as usual there are too many to list here. The, and I highly encourage you to have a read of. She is always very thorough and we are grateful for her efforts!OPENSIM USERS: PLEASE READ!This build can not be offered to Opensim as it is right now.In my I said we would provide an “as-is” download of this release for Opensim.
However, I have been informed that this update will actually cause Opensim regions to crash upon login. Unfortunately, by the time we made the decision to reverse the split we were too far into our QA process to test or make changes & fixes.
This is why the “as-is” was mentioned. Because of the severity of the issue (crashing regions is about as bad as it gets) and having no time to fix it, I am forced to go back on my word on this one.We will continue to host Firestorm 6.0.2.56680 on our downloads page in the Opensim section until we are able to remedy the major issues. The SL version of this update will install separately, so you can use the 6.3.2 update for SL and continue to run 6.0.2 for Opensim.As part of our 3-version rule, we will be blocking version 5.1.7.55786 from accessing Second Life grid as of October 21st (3 weeks). It will continue to function for Opensim.Enjoy!Jessica Lyon and the Firestorm Team. Seemed like a good idea at the timeRecently, we announced that we would be separating our repository into two, one for Opensim and one for Second life. Splitting Opensim into its own repository made sense to us as it would allow the deviation of SL from Opensim with fewer development problems for us.
Most prominently, it would allow us to keep Windlight for Opensim yet replace it with LL’s Environmental Enhancement Project (EEP) for Second Life. But that announcement triggered many discussions with Opensim developers, grid owners and their users, who brought up some very strong arguments and points we hadn’t thought about—not the least of which was that Opensim can only adapt and adopt Second Life features if the features are present in the viewer first and are thus accessible in Opensim. For example, Ubit of Opensim is working on server-side support for Bakes on Mesh right now.It made sense to split, but your points changed our minds. I’m reversing that decision and we will be returning to the way things were. Our upcoming release of Bakes on Mesh for SL will have an Opensim variant, with the caveat that we haven’t had time to beta test for Opensim. It will be provided to Opensim AS IS.
Keep in mind, there have been several major SL features since your last Firestorm viewer. More details on those below under “Examples.”Let’s talk prioritiesLet me be clear: I am Opensim’s biggest advocate on the Firestorm team. I personally feel that continued Opensim compatibility is paramount for the EDUs, high schools, universities and colleges that moved to Opensim after LL removed their discounts a few years ago; and for the grid owners and their users.
There are enough of you to justify the effort. I consider many of you my friends. And I get it: You want Second Life without the cost overhead and constraints.
For some of you it’s even an ‘anti-establishment’ movement, while most just want the freedom to run your own grid the way you want to or want to be part of a grid that fits your personality, style and character. Some of you want more prims, cheaper regions, and the ability to teleport to other grids (hypergrid). I get all that.
As much as anything, I want Firestorm to continue to be usable for you. We are founded on the ethos of “improving the user experience” for as many as we can.
That includes Opensim.Big numbers and the real reasonsLet’s get this out of the way first: 542,967 unique users across 9.9 million sessions spending 17.7 million hours logged into Second Life on Firestorm over the last 30-day period.That is our most recent set of metrics regarding Firestorm usage in Second Life, directly from Linden Lab. Those are mind-blowing figures. Although we don’t have metrics for how many Opensim users run Firestorm, it is safe to say it isn’t anywhere near that. My estimate would be somewhere around 2,000 users. But still THAT’S NOT WHY!It is because of those numbers that we prioritize Second Life, but those numbers are NOT why we struggle with Opensim.We are struggling in large part because we do not have, and cannot find, a dedicated Opensim viewer developer with lots of time on their hands. I cannot simply crack my virtual whip and make our devs drop their Second Lives and move into Opensim.
Even if I could, it would be unfair of me to do so. I also cannot pull a dedicated Opensim viewer dev out of thin air, though it isn’t from lack of trying!We struggle because of human resources. Because of the complexity of cross-grid/cross-platform issues.
Multiple server versions in use. So many grids and no standard specification. Grid features that vary from grid to grid.
We fix an issue on one grid that breaks something on another. Compatibility with Opensim is vastly more difficult than it is with Second Life. Add to that the fact that we have to continue to merge upstream code from LL on a regular basis. We just don’t have the human resources.We struggle because of TIME! Human resources is about people and time, which are both scarce these days. Although Beq, one of our developers, has graciously stepped up to the task, she is only human and doesn’t have the time to do all the things on her own while balancing her real life responsibilities as well.So we have to declare here what is possible, even with the best of intentions.Managing expectations, impossibilities and some ground rules– Multiple server versions to be compatible with.
There are SO many server versions out there in Opensim-land that it is impossible for us to be compatible with all of them. Even with a dedicated OS viewer dev, we couldn’t do it. As mentioned above, we fix a bug on one grid and break something on another.
We cannot test on every grid out there.– We also cannot continue to keep old legacy protocols alive in Firestorm forever. This is not by choice, but by necessity. Every compatibility and legacy feature we retain means another set of checks and configuration options that have to be managed.
![]()
Not only do these impact viewer performance directly, they also create significant maintenance and merging workloads when taking in upstream innovations, features and bug fixes from Linden Lab.– Finally, we cannot adapt to new Opensim features without direct communication via viewer patch contributions, or better yet, some kind of reference viewer. In the past we have been criticized for not adopting a new feature or functionality that was implemented in Opensim.
But in reality no one told us what was changed, or how it worked, or even that it existed in the first place. No more of that! We can’t track LL AND Opensim developments without communications. I’m glad to say that communications have significantly improved with Opensim since our “split” announcement. Let’s keep that going!– Also, we can only adopt or implement new features based on the current server version being worked on.
We cannot do a feature that works on one grid one way, but differently on another or not at all.I can’t emphasize enough how important and useful a reference viewer would be, moving forward, but I’m also aware of how unlikely it is that one will materialize that all grids can agree on. Patches then, please!We WILL continue to do our very best to maintain compatibility with Opensim.As mentioned above, we have to focus on ONE server version to be compatible with and that will have to be whichever is most current. If you choose to fall back on an older server version with your grid, or disable certain features, that is of course your choice. I’m really sorry, but we can’t be compatible with all the custom grids and server versions out there. We will strive to be compatible with tip; this is the best we can reasonably do.The harsh reality is that Opensim is going to have to keep up with US now, at least when it concerns features, functionality and UI panels that we cannot make grid specific.
It’s the only choice left. We will continue to reach parity with Linden Lab as our first priority, then do our best to achieve backwards compatibility with Opensim. It will be very helpful to us, and beneficial to you, if you can adopt those SL features that we cannot separate between SL and OS.ExamplesHere are some things that in the near future will be impossible for us to separate:LL will be releasing the Environmental Enhancement Project (EEP). This will replace our Windlight interfaces and windlight overall. We’ve looked closely we’ve tried but we CANNOT keep Windlight for Opensim AND EEP for SL. That is what triggered us to do the split in the first place. Sadly, you are going to lose Windlight on your grids when the time comes, and there is nothing we can do about it.
It’s beyond our abilities to separate them. It is my hope that you will collectively find a way to integrate EEP into Opensim. It’s your only option for environment controls other than remaining on an older version of Firestorm.Another is estate management tools (EAM). You will notice with this upcoming BoM release that estate tools have changed. Some options will not be compatible with Opensim unless the server is adapted. Again, we cannot make separate UI panels for separate grids from the same repository and code base.Yet another is LL’s Love Me Render update.
No idea how that’s going to play out in Opensim.I could go on, but you get the gist of it. These are all things we cannot make reverse compatible and are why we initially wanted to make a split.
But splitting the viewer means splitting the already scarce resources, and SL evolution is not going to stop. Which brings me to my final pleaOPENSIM VIEWER DEVELOPER POSITIONS AVAILABLE!If you are an Opensim user AND you are a competent viewer developer familiar with Firestorm code (you will need to be), PLEASE APPLY WITHIN! You will be received as a HERO and super star by your Opensim community! Well, ok, I can’t promise that, but we have cookies and cake!We very much are in need of someone who can do viewer code and uses Opensim regularly if we are to be able to continue compatibility with Opensim long term. If you know someone poke them!SighIt has been painful and difficult for me to write the above.
I do wish I could provide lighter news for our Opensim friends. This is worse news for some of my closest Opensim friends. But these are the harsh realities that are being faced right now and it’s better that I be brutally honest than sugar-coat the situation. With any luck, maybe we’ll get an Opensim viewer developer on board soon and things will start looking up again!With LoveJessica LyonFounder/CEO/Project ManagerThe Phoenix Firestorm Project, Inc.
This is the technical paper from a talk given at the 12th Annual Borland Developer's ConferenceBy David R. Robinson Sage U.S. Holdings, Inc.David R.
Robinson works as the director of development for the Carpe Diem Electronic Time Sheet product line at Sage U.S. Holdings, Inc. David has 12 years' experience in software development and management. David lives in Texas with his wife and three children.Note: No portion of this paper may be distributed or reproduced by any means, or in any form, without the author's and/or Borland's prior written permission.This paper will discuss the various options available for installingInterBase.
I will discuss using the Installation API, the InterBaseExpress TIBInstall component, Borland's setup.exepackage and various other installation packages. This paper will also describewhat you need to know to be able to create your own installation scripts using Wise, InstallShield, MSI,etc.To be consistent with the, I decided to use some of the the same conventions used in thatdocument.The variable%SYSTEM32% is a reference to the Windowssystem folder. For Windows 95, Windows 98, and Windows Me, the defaultsystem folder is C:WindowsSystem. For Windows NT and Windows 2000,the default system folder is C:WinntSystem32.Most installation packages determine the Windows system folder for youautomatically.The variable%INTERBASE% is a reference to the folderwhere the user choose to install InterBase.
If an InterBase installationalready exists,%INTERBASE% should be the folder where InterBase is currentlyinstalled.I work for Sage U.S. Holdings, Inc. As the Director of Development for theproduct line.
I first started usingInterBase in 1995 when we were in the process of completely rewriting Carpe Diemusing Delphi 1.0 (it was originally written using Turbo/Borland Pascal).One of the main goals of the rewrite was to support multiple client/serverdatabase engines. We decided that we would support InterBase (even though wedidn't know of anyone other than Delphi programmers using it at that time),Oracle, Microsoft SQL Server, Informix and Sybase. We also supportedParadox-which is the reason we became InterBase an VAR. At that time we didn't really know much about InterBase, but afterwe installed the other database engines, we quickly discovered that it was theeasiest to install and configure.We shipped the client/server update for Carpe Diem in January 1997.
AsI mentioned, we supported Paradox as well the various client/serverdatabases. We knew that Paradox was not something that should be usedexcept for a relatively small number of users. We assumed that ourcustomers would not use Paradox when they had a large number of users.Since most of our customers had 75 or more users, we didn't expect many of themto use Paradox. Unfortunately, we ended up having the majority of ourcustomers use Paradox because it was FREE compared to the cost of installing aclient/server database server and purchasing client licenses for all of theirusers. We had customers with over 100 concurrent users trying to useParadox tables for their Carpe Diem database.
This became a major problemfor us because of how easy it is to corrupt Paradox tables.We had to come up with a low cost alternative to Paradox so that we could getall of our customers who were using Paradox to switch to a true client/serverdatabase engine. We looked at several alternatives and decided to go withInterBase.
In June 1997, we became InterBase VARs. We pre-paid for5,555 licenses so we could get a great price on InterBase. This wouldallow us to sell InterBase to our customers at a bargain price. We haveworked closely with InterBase since that time including participating in theInterBase VAR Advisory Council. We now have over 8,000 users usingInterBase as the database for their Carpe Diem installation.After InterBase was released as an open-source product in July 2000, Istarted seeing the same questions asked over and over. Most people werewanting to know how to install InterBase server with their application and howto install the InterBase client. There were also people asking if therewere scripts to install InterBase with their installation product such as Wiseor InstallShield.At Sage we use Wise InstallMaster from to install our software.
After we became an InterBase VAR, we created a Wise scriptto install InterBase. Once InterBase 6 was released, we updated ourscripts to support InterBase 6.
The Wise scripts were created based on our scripts that we had been using for InterBase 5.x andthe. Since there seemed to be a big demand for information oninstalling InterBase and we had a good script to install InterBase, we decided to contribute our Wise scripts to the InterBase community.We released both the script source and compiled scripts to the community.The demand for the scripts outgrew the bandwidth for the hosts where the scriptswere located. I needed to find a new home to host the InterBasescripts. I approached the people at (previously DelphiHost.com) about hosting the InterBase scripts forme. They were gracious enough to host the scripts for me free of charge(of course I help promote them on the site as well).I initially created the site as a source for Wise install scripts forinstalling InterBase.
However, I was still seeing the same questions askedabout how to install InterBase and if certain scripts for certain productsexisted. As an effort to try to meet the need forproviding information about how to install InterBase, I decide to change the Wise Installation Script site to a general InterBase InstallationInfo site. I have now expanded the site to include a FAQ on installingInterBase and several different installation script sources. The InterBaseInstall Info website can be found at.It is imperative that everyone installing InterBaseadhere to certain installation standards to prevent an installation ofInterBase from breaking an existing InterBase installation. One of thebiggest problems of the Borland Database Engine (BDE) is that most people donot properly install the BDE. Many software products (especially Corel)install an older version of the BDE on top of a more recent version or simplyoverwrite existing configuration settings. This frequently causesexisting applications to stop functioning after the new application has beeninstalled.For InterBase, having installation standards wasn't asimportant before InterBase became an open-source product because the chancesof someone having two products that used InterBase was pretty small.However, now that InterBase is an open-source product and you can deployInterBase for free, there appears to be a lot more people using InterBase as the databasefor their product.
If there are not some standards for installingInterBase, it may be difficult to use multiple products that use InterBase onthe same system without tweaking something after installation.I am basing the information contained in this paper onthe and the experiences that I've gained byinstalling software products such as Carpe Diem Electronic Time Sheet, the BDEand InterBase over the past several years.The simplest way to see what is required to installInterBase is to start by going over what is needed to do a basic (minimal)installation of InterBase. We'll cover the InterBase client first andthen describe what is needed for a basic server installation. Before wedo that, let's briefly discuss why it is important to reference count sharedfiles.Whenever you install a file that can be shared betweenapplications or multiple installations of the same application, you shouldmaintain a reference count in the registry. Even if you do not installa shared file because a newer version already exists, you should update thereference count for that file. This should prevent the removal ofanother application from deleting a file that you are depending on.To update the reference count for a shared file, youshould first check to see if the registry key for that file (i.e.C:WindowsSystemGDS32.DLL) exists under HKEYLOCALMACHINESOFTWAREMicrosoftWindowsCurrentVersionSharedDLLs.If the registry key for the file you are installingdoes not exist, you should create the registry key and set the data valuefor that key to 1. If the registry key for the file your areinstalling already exists, you should increment the data value by1.
When you uninstall the file, you should decrement the data value by1. Most installation programs will not remove a shared file until thereference count becomes zero.A minimal installation of the InterBase client may seemtrivial since all that is required for a client installation is three files(GDS32.DLL, INTERBASE.MSG, & MSVCRT.DLL). However, to properlyinstall these files, there are certain issues that you need to be awareof. We'll start with GDS32.DLL. Installing GDS32.DLLGDS32.DLL is the interface library used by clientapplications.
If you install GDS32.DLL, be sure that you installINTERBASE.MSG as well (see Installing INTERBASE.MSG below).Before you attempt to installGDS32.DLL you should be sure that it does not already exist on thesystem. Ib32.hlp,ib32.cnt- Master InterBase help fileibgloss.hlp,ibgloss.cnt- InterBase glossary &definitions help filesqlref.hlp,sqlref.cnt- InterBase SQL Reference help fileperform.hlp,perform.cnt- Performance Guidelines help fileRelease NotesThe InterBase Release Notes are contained in the fileReleaseNotes.pdf. You can install the Release Notes in the%INTERBASE%folder.In addition to the items described in the section above, you can installInterBase as an NT Service, and install several utility programs, help files,and tools as part of the InterBase server installation. These aredescribed below. Running InterBase as an NT serviceIf you are running on Windows NT or Windows 2000,you can run InterBase as an NT service. An NT service can run in thebackground even when there is no user logged into the NT system.
Irecommend that you run InterBase as an NT service if you are running onWindows NT or Windows 2000.To install the InterBase server as an NT service, youcan use the instsvc.exe program. This will create the necessary registryentries to configure InterBase as an NT service. You should callinstsvc.exe as follows:instsvc install '%INTERBASE%' -autoA program can be installed as a Windows NT service bycalling the CreateService Windows API call.
If you are installingInterBase using an installation program (such as Wise) that can createservices, I recommend that you create the service using the installationpackage rather than by calling instsvc.Note: If you install InterBase as an NT Serviceinto a folder that contains folder names with spaces, you may encounter thefollowing error:If you receive this error, click the link above forthe Borland Developer Support article describing theerror. The best way I have found to avoid this problem is to save thepath name for the service executable in 8.3 (short file name) format.Note: The problem can occur for the InterBase Guardian servicedescribed below. Installing the InterBase GuardianBefore you configure the InterBase Guardian as aservice, you should install the InterBase Guardian file, ibguard.exe, in the%INTERBASE%bin folder. Be sure that you update the (reference count) for IBGUARD.EXE.The InterBase Guardian is a process that can be run tomonitor the InterBase server. If the InterBase server terminatesabnormally, the Guardian process will automatically restart it. TheInterBase Guardian can also be run as an NT service on Windows NT and Windows2000. Unfortunately, the instsvc program does not install the InterBaseGuardian as an NT Service, so you must manually install the Guardian processas a Windows NT service.
See page 16 of the for an example of how to create the Guardian service. If theinstallation software that you use supports creation of NT Services, this isthe best way to install the InterBase Guardian Service.When you are running both the InterBase Guardian andInterBase Server as Windows NT Services, you should set the InterBase Serverservice to start manually and the InterBase Guardian service to startautomatically. Ib32.hlp,ib32.cnt- Master InterBase help fileibgloss.hlp,ibgloss.cnt- InterBase glossary &definitions help filesqlref.hlp,sqlref.cnt- InterBase SQL Reference help fileperform.hlp,perform.cnt- Performance Guidelines help fileibserver.hlp,ibserver.cnt- InterBase Server Properties helpfileInterBase licenseIf you are installing the Borland Open Edition orFirebird open-source version of InterBase, you do not need to install alicense file. The legal text for the iscontained in the file LICENSE.TXT. You should install the most recentversion of this file in%INTERBASE% whenever you install InterBase.If you are installing the Borland Certified version ofInterBase, you should install the LICENSE.TXT file that comes with thecertified version. You will also need to have license keys to allowaccess to your InterBase server. See the section below for an explanation of licensing in the Certifiedversion.
InterBase DocumentationCompleted InterBase 6 documentation is only availablewith the Certified Edition from Borland. The documentation is availableas part of your Certified Edition purchase and is also on the InterBase 6media kit. The documentation is in Adobe Acrobat format.You can download the InterBase 6 beta documentation fromthe website.InterBase 6 introduced a new Installation API that canbe used to install InterBase. You can find an example of how touse this new installation API at:InterBase Express is a set of Delphi/CBuilder componentsthat can be used to access InterBase natively (i.e. InterBaseExpress first shipped with Delphi 5. The version of InterBase Expressthat shipped with Delphi 5 does not work with InterBase 6 (InterBase 6 shippedafter Delphi 5). You can download the latest version of InterBase Express fromCode Central on.Once you have installed the package, you can use the TIBInstall Component toinstall InterBase.The Borland installer uses the new install API toinstallInterBase 6.
To use the Borland installer, you simply run setup.exefrom the client or server folder on the InterBase 6 media CD-ROM. TheBorland installer requires that you enter a license key during theinstallation process. If you do not have a license key, you can enter'eval' to create a temporary evaluation key that you can use untilyou have purchased your InterBase licenses.You can download Wise Installer script source and compiledinstallation scripts from the InterBase Installation Info website at.I have been using Wise to install our software since 1995 and InterBase since1997.Rob Schieck has created a process to do daily builds from the Borland OpenEdition CVS tree. You can download these builds from.You can also download a build of the latest tagged version of the Borland OpenEdition CVS tree from Rob's website.You can download Wise scripts of the the Firebird open-source build from theInterBase Installation Info website or from the Firebird website at.If you want to use the Microsoft Installer, you can download MSI Merge Modules from TonyWhyman's website atYou can use other installation packages (such asInstallShield, InnoSetup, etc.) to install InterBase. However some ofthese installation packages have limitations that will prevent you from doinga complete installation or even prevent you from doing a properinstallation. You should be sure that the product that you are using cando all of the installation steps that you need before using it.For example, InstallShield Express does not allow you toadd a line to a text file.
You need to do this to update the servicesfile. Another common problem is that some installation products do notprovide a way for your to update the reference counts for shared files.I have created the InterBase Installation Info websiteas a common place for information on installing InterBase. You can download scriptsthat have been created by other InterBase users for various installation packagesfrom the InterBase Installation Info website at.When it comes to installing InterBase, the differences between the BorlandCertified and Open Edition of InterBase are:.
If you are using the Certified version of InterBase, a license must bepurchased from Borland or an InterBase reseller. The license is savedin the iblicense.dat file. Generally speaking, you will want todeploy the Certified version without the iblicense.dat file and have yourend users enter the license keys in IBConsole to activate theirserver.If you are using the Open Edition or Firebird open-source version ofInterBase, InterBase is free to use based upon the. The Certified version includes the Easysoft ODBC driver.If you are using the Open Editon or Firebird open-source version ofInterBase, you can purchase the Easysoft ODBC driver from Easysoft at.There are several other ODBC drivers available. I have included a listof the ODBC drivers that I am aware of on the FAQ page of the InterBaseInstallation Info website at.This should give you plenty of information about the various options forinstalling InterBase.
I hope this paper has been beneficial in providinginformation for you on how to install InterBase.For more information or to keep up with any changes, see the InterBaseInstallation Info website ator you can reach me via email at.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |