DSSAT Archives

DSSAT - Crop Models and Applications

DSSAT@LISTSERV.UGA.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Gabriel A. Angella" <[log in to unmask]>
Reply To:
Gabriel A. Angella
Date:
Tue, 23 Feb 2010 10:40:12 -0300
Content-Type:
text/plain
Parts/Attachments:
text/plain (231 lines)
Hello Cheryl,

thank you very much for your help.

Gabriel Angella

---- Original Message -----
From: "Porter, Cheryl H" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, February 23, 2010 9:44 AM
Subject: Re: installable ISAM


> Here is what the DSSAT Readme file says about the ISAM error:
>
> Problem:
>
> Couldn't Find Installable ISAM
>
> This problem may occur on a computer by computer basis,. The ISAM error
> means that the path to the ISAM driver (Indexed Sequential Access Method
> driver for some files) in your Windows Registry is not valid, or that the
> ISAM driver does not exist. This problem may be caused by different
> reasons,
>
> Microsoft has confirmed that this is a bug in the Microsoft products. We
> have encountered some cases that are difficult or impractical to solve.
> The main example of this is that some French Windows systems (i.e. Win
> 2000, ME) are configured with system files that are incompatible with the
> programs that are written in Visual Basic in DSSAT v4.0 (i.e. the *Build
> programs). We will continue to try to find the solution to the problem,
> but for now these steps below are all that we know about. These steps that
> you can take will solve the problem in many cases. The steps are:
>
> 1. For Windows ALL computers, please to go to www.windowsupdate.com to
> scan for updates.
>
> It is advisable to update your system with the most recent update for your
> Windows OS (operation system). We have found that some of the "ISAM
> problems" have been due to non-updated Windows OS.
>
> 2. Install the latest Service Pack 4 for Windows 2000 on the target
> compute
>
> Windows 2000 Service Pack 4 (SP4) provides the latest updates to the
> Windows 2000 operating systems. These updates are a collection of fixes in
> the following areas: security, application compatibility, operating system
> reliability, and setup There are two ways to get Windows 2000 SP4. You can
> download it, or you can order the Windows 2000 SP4 CD. The SP4 is
> available on the following website:
> http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/default.asp
>
> 3. For Windows XP, ME, NT Download the appropriate Jet 4.0 SP8 update for
> your computer. http://support.microsoft.com/?KBID=829558
>
> The ISAM drivers are all included in the Microsoft JET, which are used for
> database management operations and other functions. We think that the
> "ISAM problem" is related to database management operation.
>
> The Microsoft Office Setup program only update system files in certain
> situations and to a certain level. Therefore, you may not have the latest
> version of the Microsoft Jet 4.0 database engine. To obtain the latest
> update for the Jet 4.0 database engine, you can download and then install
> Microsoft Jet 4.0 Service Pack 8 (SP8).
>
>       1) In Windows Explorer, double-click the file that you downloaded in
> step 1 to start the Jet 4.0 SP8 Setup.
>
>       2) Restart your computer.
>
> 4. "Could Not Find Installable ISAM" Error Message continues. The
> Microsoft article http://support.microsoft.com/?id=283881 will find the
> problem files:
>
> The problem files could be the next:
>
> Msexch40.dll        Microsoft Exchange
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Exchange
>
> Msrd2x40.dll        Microsoft Jet 2.x
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 2.x
>
> Msrd3x40.dll        Microsoft Jet 3.x
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 3.x
>
> Mstext40.dll        Text
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Text
>
>       1)  Use Windows Explorer to search for the file.
>
>       2)  If the file is found, record its path name; if it is not found,
> proceed to step 9.
>
>       3) Start Registry Editor (Regsv32a.exe).
>
> WARNING: If you use Registry Editor incorrectly, you may cause serious
> problems that may require you to reinstall your operating system.
> Microsoft cannot guarantee that you can solve problems that result from
> using Registry Editor incorrectly. Use Registry Editor at your own risk.
>
>       4) Browse to the registry subkey described in the table, and check
> the path name against the actual path name.
>
>       5) Correct the path name if it is incorrect; proceed with these
> steps if it is correct.
>
>       6) Quit Registry Editor. If you changed the path name, repeat the
> process that produced the original error.
>
>       7) If the error persists, or if the path name was correct in step 5,
> rename the file.
>
>       8) Start the Add/Remove Programs tool.
>
>       9) Start the Office Setup program by clicking Change button against
> its entry in Add/Remove Programs and select the option to Repair or
> Reinstall Office
>
> 5. If you update your OS using the steps 1-4 above and still have the
> "ISAM problem", you can try to diagnose the problem with the Windows
> diagnostic programs, Filemon and Regmon:
>
>       Regmon:
>
>       a. Download regmon from
> http://www.sysinternals.com/files/ntregmon.zip
>
>       b. Close all other unnecessary programs. Run one of the Build
> programs.
>
>       c. Start Regmon. Before you start the capture, please clear the Log
> first. There is an icon to click to do this in Regmon on the toolbar.
> Also, click Options from the menu bar and select Filters. Replace "*" with
> XBuild.exe (or one of the Build programs) in the Include box so that only
> that program's activity is captured.
>
>       d. The utility is used to log activity with the registry. The
> general idea is that you will start Regmon and try to import the data and
> reproduce the error. After the error appears, stop the capture
> immediately. It is important to do this as quickly as possible because the
> Regmon files grow very large very quickly.
>
>       FileMon
>
> Filemon log is quite the same. Go to
> http://www.sysinternals.com/files/ntfilmon.zip to download Filemon. Start
> the Build program and start Filemon. Set the filter to include only
> XBuild.exe. Check the log file.
>
> These logs can help finding what files or registration keys are missing.
>
> 6. If none of these solutions work, change you Regional Settings under
> Settings to English (United States).
>
>
> -----Original Message-----
> From: DSSAT - Crop Models and Applications [mailto:[log in to unmask]]
> On Behalf Of Gabriel A. Angella
> Sent: Tuesday, February 23, 2010 5:52 AM
> To: [log in to unmask]
> Subject: Re: installable ISAM
>
> Dear all,
>
> I also had the same problem, any help to solve it will be appreciated as
> well.
> Regards,
>
> Gabriel A. Angella
> INTA EEA Santiago del Estero
> Argentina
>
> ----- Original Message -----
> From: "GLADYS AGUILAR" <[log in to unmask]>
> To: <[log in to unmask]>
> Sent: Monday, February 22, 2010 11:38 PM
> Subject: installable ISAM
>
>
> Hello,
>
> I've been running DSSAT Version 3.5, 4.0 and 4.2 on  Windows XP version
> 2002.Service Pack 3 machine with no problems. But now, after I run any
> experiment appears this message: Couldnt find installable ISAM, in
> Cmboutfiles/frm Selection.
> Any suggestions to solve this problem would be appreciated.
> Regards
>
> Gladys
> ----------
> Universidad de los Andes. Facultad de Ciencias.
> Instituto de Ciencias Ambientales y Ecológicas (ICAE)
> Postgrado Ecología Tropical.
> Mérida, Venezuela.
> Email: [log in to unmask]
>
>
>
>
>
> _________________________________________________________________
> News, entertainment and everything you care about at Live.com. Get it now!
> http://www.live.com/getstarted.aspx
>
>
> El contenido del presente e-mail y sus posibles adjuntos, pertenecen al
> INTA y puede contener información  confidencial. Si ud no es el
> destinatario original de este e-mail y por este medio pudo acceder a dicha
> información, por favor solicitamos contactar al remitente y elimine el
> e-mail de inmediato. Se encuentra prohibida La divulgación, copia,
> distribución o cualquier otro uso de la información contenida en el
> presente e-mail por parte de personas distintas al destinatario.
>
> This e-mail contents and its possible attachments belongs to INTA and may
> contain confidential information. If this e-mail was not originally
> addressed to you, but you have accessed to such information by this means,
> please contact the sender and eliminate this e-mail immediately.
> Circulation, copy,distribution of the information contained in this e-mail
> is not allowed on part of those different from the addressee.
>
> Imprima este mensaje solo si es necesario. Proteger el medio ambiente está
> también en sus manos.
>


El contenido del presente e-mail y sus posibles adjuntos, pertenecen al INTA y puede contener información  confidencial. Si ud no es el destinatario original de este e-mail y por este medio pudo acceder a dicha información, por favor solicitamos contactar al remitente y elimine el e-mail de inmediato. Se encuentra prohibida La divulgación, copia, distribución o cualquier otro uso de la información contenida en el presente e-mail por parte de personas distintas al destinatario.

This e-mail contents and its possible attachments belongs to INTA and may contain confidential information. If this e-mail was not originally addressed to you, but you have accessed to such information by this means, please contact the sender and eliminate this e-mail immediately. Circulation, copy,distribution of the information contained in this e-mail is not allowed on part of those different from the addressee.

Imprima este mensaje solo si es necesario. Proteger el medio ambiente está también en sus manos.

ATOM RSS1 RSS2