View Full Version : Problem installing
fuligin
May 22nd, '03, 10:33 AM
Okay I've got the CD, and I tried installing it. I have win 98, and when I hit next on the picking icons part, it freezes and I get this error. The first and last quotes are mine.
"Assertion Failed
Program C:\\windows\temp\1053562906\windows\setup.exe
file:../../../src/share/native/sun/awt/font/fontmanage...
Line: 506
Expresion: errno==0&& count==(size_t)size
For information on how you possibly can cause an assertion failure, see the visual C++ documentation on asserts.
(press retry to debug the application-JIT must be enabled)"
Then it has Abort, Retry, and Ignore buttons to click.
I tried to close other programs and such, but no luck.
Lawrence
Simon
May 22nd, '03, 10:42 AM
Ah...the font problem again.
Here's what's going wrong:
Java, in initializing certain objects, performs a scan of your system fonts. If any of your font files are "corrupt", they will cause a system-level error when Java tries to scan them, causing Windows to crash Java.
There's no way for Java to avoid this crash (currently), as it is windows that is crashing the JVM.
The fix for it is easy enough: delete the corrupt font file. The issue is in determining which file is corrupt.
You have 2 options:
1. You can delete (or just move) the font files in your system font directory (typically C:\Windows\Fonts)....you only need to do this until you can run the install of HD.
2. You can install HD on another machine and then copy the install folder over to the offending machine.
One way or the other, once you get HD onto the problem computer, you're just about home-free. When HD starts, it will do the same scan of all system-level fonts. The only difference is that HD is set to log each font file as it accesses it. So, when HD crashes, you can open up the file "trace.log" in your install directory. The last font file listed is the last file that was successfully accessed. Delete the next file (alphabetically) in your fonts folder and you should be good to go.....just repeat the process until all corrupt font files have been removed.
I hope this helps....please post here if you need more help.
fuligin
May 25th, '03, 06:58 AM
I tried that, and I can get into the program, but when it kicks me out with the same error, the log file only has how much memory is used, and dosen't list any font files. I do have an odd problem that the first font I have has no name, and I can't rename it, or move it. So I'm not sure if that's causing a problem.
And sorry about the double post, that was my fault.
Thanks for the help
Lawrence
Simon
May 25th, '03, 07:53 AM
Originally posted by fuligin
I tried that, and I can get into the program, but when it kicks me out with the same error, the log file only has how much memory is used, and dosen't list any font files. I do have an odd problem that the first font I have has no name, and I can't rename it, or move it. So I'm not sure if that's causing a problem.
And sorry about the double post, that was my fault.
Thanks for the help
Lawrence
Make sure you grab the most recent update. If your trace.log file doesn't have any font declarations in it, then you are running off of version 1.0, which didn't have those statements enabled.
Go to the update page (in the Free Stuff section) and pull down "update.jar" and put it in your install directory, replacing the existing file.
The next time you start HD after that, your log file will have the font declarations in it.
fuligin
May 26th, '03, 05:28 AM
Okay, I got the update, but I'm not sure exactly where you mean the last font: I have a bunch listed under "No native font", or somewhere else? Basically, is it at the very end of the log?
Simon
May 26th, '03, 05:50 AM
Originally posted by fuligin
Okay, I got the update, but I'm not sure exactly where you mean the last font: I have a bunch listed under "No native font", or somewhere else? Basically, is it at the very end of the log?
Yup. The very end of the log will list the last font that was successfully read in. In your system fonts directory, delete the next font (alphabetically) and then re-launch HD and see how far it gets.
Powered by vBulletin® Version 4.2.0 Copyright © 2012 vBulletin Solutions, Inc. All rights reserved.