This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Heather, I did some research on the error you originally reported: Warning: Cannot convert string "10x20" to type FontStruct mcimagem: ERROR fork()ing Warning: Cannot convert string "10x20" to type FontStruct mcimagem: ERROR fork()ing This error has been experienced infrequently by other users of McIDAS under Windows XP. It appears to be related to the Physical Address Extension (PAE) being enabled in Windows XP. Here is a quote of an exchange from SSEC to a user on how to get around this problem: We've had a user with this problem once before, although we have never seen the problem here. That user did some investigation on his own and found that disabling Physical Address Extension (PAE) fixed the problem. He was not sure why PAE was enabled. It's required only if you have more than 4 GB memory, whereas his system had only 504 MB. Here is the information he sent to us after he fixed the problem: Errors with fork are generally related to memory. I noticed in the �General� tab of �System Properties� that Physical Address Extension was enabled. Physical Address Extension is only required if you have an address space larger than 4GB. More information can be found about it here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/memory/base/physical_address_extension.asp I found information about how to disable it here: http://support.microsoft.com/?kbid=895575 By following the information in the second article I was able to disable Physical Address Extensions. I did so by adding the text highlighted in bold (/NOPAE /NOEXECUTE=alwaysoff) to the boot.ini file: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NOPAE /NOEXECUTE=alwaysoff After rebooting, I was able to verify in �System Properties� that Physical Address Extension was no longer being used. Running McIDAS no longer generated any errors. So, the first thing you need to do is determine if your problem resembles the one referenced above. Aside: I checked the Windows XP Home SP3 setup on my netbook and did not see any indication of PAE being active. Please let me know if disabling PAE on your Windows XP machine works around the problem you are seeing. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: AMA-903084 Department: Support McIDAS Priority: Normal Status: Closed