Original: UAE TiME is running to FAST... (prb.other)

oK .. i try to move my problem to this directory ..

normally i work with original Amiga .. but a temprorary hd problem bring me to UAE ...

i try many configuration .. many crashs .. many runs slow .. etc ..
can anyone post me a good config ?? i think my problem is a mistake in my configs .. ( i hope so )!!

My problem on the Amiga is the FFS and validate .. the Mailboxsystem often validate .. so i try to make a SFS ..

i read .. you can on UAE make the same ... i have a HDF .. and want TRY to change from FFS to SFS .. but on HDToolBox i never see the hdf files on uaehf.device ..

is there a trick ??

Greets ..

IRoN !

[Toni Wilen]

i try many configuration .. many crashs .. many runs slow .. etc ..
can anyone post me a good config ?? i think my problem is a mistake in my configs .. ( i hope so )!!

Quickstart "Highend" configuration should be good starting point.

Originally Posted by IRoN

i read .. you can on UAE make the same ... i have a HDF .. and want TRY to change from FFS to SFS .. but on HDToolBox i never see the hdf files on uaehf.device ..

I guess you have regular hardfile which do not support partitions. You need to create new hardfile and click "Enable RDB Mode" button. Or you have hdtoolbox version that stops scanning after first non-device is found, workaround is to move the hdf to first slot in Harddrives-panel. (just use mouse to drag it)

Stability problems most likely come from directory filesystem ("Can't find key" errors in logs you posted. This is "should never happen" error, something is messed up in filesystem emulation) and using hardfile most likely fixes that. Or you may have some buggy system utility installed.

Could you try narrowing down the reason for "key" errors? Run winuae with -log ("winuae.exe -log") parameter in windowed mode. (opens log window) Boot to WB, did any "key" errors already appear in the log? If yes, there is something weird in your startup-sequence, user-startup or wbstartup.

Hello again ..

after hours of trying ..

here is my news report ...

first i try to disable my HDF files .. .i copied all data to a normally directory .. and start again ..
Nope .. the KEY errors .. not gone ..

i try other kickrom versions .. nothing ..

i start only a original amikit version ..
ahhh .. no key errors .. after hours of waiting only millions of

27-028 [156371 226x031]: WARNING: do_blit() couldn't lock
27-340 [156384 226x146]: WARNING: do_blit() couldn't lock

i start programm for programm .. and wait minutes .. no key error ..
i have one more bbs system running in background .. i configure it for a friend ..
i have troubble with the system ..
i dont start it this time .. and i have no key errors ..
20:56 oclock .. i start the other BBS system ..
temporary only the do blit errors ...
21:05 hmm nothing .. no key errors .. hmmm
ok .. my changes ..
1 ) New kickrom ..
2 ) new UAE config .. cpu ram etc ...

it runs this time .. no probs .. but what he meen with the
58-965 [45299 226x031]: WARNING: do_blit() couldn't lock

I check the logfile all 10 Minutes ..

Greets ..

IRoN

[Toni Wilen]

Originally Posted by IRoN

58-965 [45299 226x031]: WARNING: do_blit() couldn't lock

Same problem in both windowed and fullscreen modes? Note that this isn't serious problem and can be ignored.

EDIT: and update WinUAE, this message is gone in 1.5.0 and newer..

Yoohh ..

New changes .. no errors .. ( at this time )

i updatet the directx .. the do_blit errors gone ...
now i rum 1.5 beta4 new kickroms .. original Amikit config and now it works fine ..

i dont no.. but i think .. the configure is highly important ..
oK .. the system runs .. the errors are gone ..
Thanx for the helps !!

ps: my wishlist for 1.6 -> a automatic highspeed configuration ... and a configchecker .
the configchecker tell me ... Your config is very fast but its
possible that you become a running clock

Greets
IRON !

[andreas]

ps: my wishlist for 1.6 -> a automatic highspeed configuration ... and a configchecker

If this materializes one day, I also want a config WARNER which will tell the user: "Caution: Your config file is hopelessly outdated - you may run into trouble".


This is OVERDUE. Many people still work with config files created from 0.8.xx versions - this is insane and likely to attract odd issues like a magnet.