Hyperion Entertainment Message Boards

I got my new motherboard, Enhancer, and USB startup stick from Amiga kit, and assembled it all today. The USB boot stick from Amigakit is found OK. "Loading finished ######################### 100%" message comes up after a short time. Next Line reads: "About to call loader entry at 0x7BD02020" at wh...

In anticipation of getting an X5000/40 when available, I'm looking into whether to do my own build or buy it pre-built from AOTL. I'm seeing more and more computer cases available without an internal optical drive bay. Could an external BD/CD/DVD drive hooking up via USB 2 work for booting, or does ...

Thanks Raziel. I should be more curious and/or read more carefully before I post dumb questions.

Paul

Do I understand correctly when I think that the drop down menu for workbench "Tools" should now include an item for "AmiUpdate" in addition to the "ResetWB" which has always been there? If so, something went wrong in my install of update 6. The functionality is all there. It found several updates an...

If it's caused by a 16-bit Use Count running over, then that implies > 65536 Opens, which in a day means about one per second. That's an awful lot of Opens! One per second from a clock app? To test it, I would turn off AmiDock and all Commodities. Also, you can go into ScreenBlanker Prefs and turn ...

Problem solved. I had to take out my USB2 card first 'cause I was trying to boot from the original 4.1 before there was USB2 support.. Still got the black screen. So I reset the UBOOT to factory defaults and finally was able to boot into 4.1.0 from the original CD. So I was finally able to edit the ...

Do what Slayer's ghost suggested. I notice that the error message says "3dfxVoodo.chip". Is that really what it says? It is miss-spelled, it should be "3dfxVoodo o .chip". I wonder if you have a corrupted Kicklayout file? The misspelling is my fault. I think I caught it and corrected it on the amig...

I ran the update on my A1-XE. Reboot started. It got part way through then said it couldn't find 3dfxVoodo.chip and quit booting. Short of taking things apart and using my backup HD as the main HD, it looks like I'm in serious trouble.

Tony, Having turned various items and combinations of items in WB startup, I've come to the conclusion that the Screen Blanker module is what's causing the problem here. Are there issues with the module, (update4) or is there just something wrong with mine? Paul (using the ON/OFF switch on the monit...

Exactly. I don't think the bug only shows up when running out of memory, it is there always when the swap is enabled. Memory is always allocated and deallocated when messages and timers run, so after time there could be corruption causing lockup, but apparently mostly when swapping is enabled, even...