OS 3.9 BB4 Drive Polling

[Snoopy1234]

Hi. My OS 3.9 Boing Bag 4 A1200 is polling the drives erratically in the background on Workbench. DF0: is especially noticeable - with no disk inserted; it's grinding and clerking away in random gestures... The DF0: icon Unreadable: DF0: also randomly pops up and often isn't cleared.
I ran SnoopDos and the behaviour is looping repeatedly:


SnoopDos logging started on Sunday, 27-Nov-22 at 13:59:46

Count Process Name Action Target Name Options Res.
----- ------------ ------ ----------- ------- ----
273 [5] Workbench #FLUSH (None) DH0 OK
274 [5] Workbench #FLUSH (None) DH0 OK
275 [5] Workbench #FLUSH (None) DH0 OK
276 [5] Workbench #FLUSH (None) DH0 OK
277 [5] Workbench #DISK_INFO 2000928 CF0 OK
278 [5] Workbench #DISK_INFO 200093E IDF1 OK
279 [5] Workbench #DISK_INFO 2000956 IDF0 OK
280 [5] Workbench #DISK_INFO 200096E OK
281 [5] Workbench #DISK_INFO 2000986 OK
282 [5] Workbench #DISK_INFO 200099E OK
283 [5] Workbench #DISK_INFO 2007FD8 RAM OK
284 [5] Workbench #DISK_INFO 2007FEE DH0 OK
285 [5] Workbench #DISK_INFO 2008004 DF0 OK
286 [5] Workbench #DISK_INFO 200801A DH1 OK
287 [5] Workbench #DISK_INFO 2008030 DH2 OK
288 [5] Workbench #INFO 219F899, 217BE32 DH0 OK
289 [5] Workbench #FLUSH (None) DH0 OK
290 [5] Workbench #FLUSH (None) DH0 OK
291 [5] Workbench #FLUSH (None) DH0 OK
292 [5] Workbench #FLUSH (None) DH0 OK
293 [5] Workbench #DISK_INFO 2000928 CF0 OK
294 [5] Workbench #DISK_INFO 200093E IDF1 OK
295 [5] Workbench #DISK_INFO 2000956 IDF0 OK
296 [5] Workbench #DISK_INFO 200096E OK
297 [5] Workbench #DISK_INFO 2000986 OK
298 [5] Workbench #DISK_INFO 200099E OK
299 [5] Workbench #DISK_INFO 2007FD8 RAM OK
300 [5] Workbench #DISK_INFO 2007FEE DH0 OK
301 [5] Workbench #DISK_INFO 2008004 DF0 OK
302 [5] Workbench #DISK_INFO 200801A DH1 OK
303 [5] Workbench #DISK_INFO 2008030 DH2 OK
304 [5] Workbench #INFO 219F899, 217BE32 DH0 OK
305 [5] Workbench #FLUSH (None) DH0 OK
306 [5] Workbench #FLUSH (None) DH0 OK
307 [5] Workbench #FLUSH (None) DH0 OK
308 [5] Workbench #FLUSH (None) DH0 OK
309 [5] Workbench #DISK_INFO 2000928 CF0 OK
310 [5] Workbench #DISK_INFO 200093E IDF1 OK
311 [5] Workbench #DISK_INFO 2000956 IDF0 OK
312 [5] Workbench #DISK_INFO 200096E OK
313 [5] Workbench #DISK_INFO 2000986 OK
314 [5] Workbench #DISK_INFO 200099E OK
315 [5] Workbench #DISK_INFO 2007FD8 RAM OK
316 [5] Workbench #DISK_INFO 2007FEE DH0 OK
317 [5] Workbench #DISK_INFO 2008004 DF0 OK
318 [5] Workbench ChangeDir SYS:
319 [5] Workbench ChangeDir SYS:
320 [5] Workbench Open ENV:sys/def_DF0.info Read OK
321 [5] Workbench *Open ENV:sys/def_DF0.info Read OK
322 [5] Workbench #FINDINPUT 20AA791, 202B7EF, 20AA7F RAM OK
323 [5] Workbench #SEEK 20400E1, 0, RAM OK
324 [5] Workbench #SEEK 20400E1, 0, FFFFFFF RAM OK
325 [5] Workbench #READ 20400E1, 834588C, 70 RAM OK
326 [5] Workbench #END 20400E1 RAM OK
327 [5] Workbench #DISK_INFO 200801A DH1 OK
328 [5] Workbench #DISK_INFO 2008030 DH2 OK
329 [5] Workbench #INFO 219F899, 217BE32 DH0 OK
330 [5] Workbench #FLUSH (None) DH0 OK
331 [5] Workbench #FLUSH (None) DH0 OK
332 [5] Workbench #FLUSH (None) DH0 OK
333 [5] Workbench #FLUSH (None) DH0 OK
334 [5] Workbench #DISK_INFO 2000928 CF0 OK
335 [5] Workbench #DISK_INFO 200093E IDF1 OK
336 [5] Workbench #DISK_INFO 2000956 IDF0 OK
337 [5] Workbench #DISK_INFO 200096E OK
338 [5] Workbench #DISK_INFO 2000986 OK
339 [5] Workbench #DISK_INFO 200099E OK
340 [5] Workbench #DISK_INFO 2007FD8 RAM OK
341 [5] Workbench #DISK_INFO 2007FEE DH0 OK
342 [5] Workbench #DISK_INFO 2008004 DF0 OK
343 [5] Workbench #DISK_INFO 200801A DH1 OK
344 [5] Workbench #DISK_INFO 2008030 DH2 OK
345 [5] Workbench #INFO 219F899, 217BE0A DH0 OK
346 [5] Workbench #FLUSH (None) DH0 OK
347 [5] Workbench #FLUSH (None) DH0 OK
348 [5] Workbench #FLUSH (None) DH0 OK
349 [5] Workbench #FLUSH (None) DH0 OK
350 [5] Workbench #DISK_INFO 2000928 CF0 OK
351 [5] Workbench #DISK_INFO 200093E IDF1 OK
352 [5] Workbench #DISK_INFO 2000956 IDF0 OK
353 [5] Workbench #DISK_INFO 200096E OK
354 [5] Workbench #DISK_INFO 2000986 OK
355 [5] Workbench #DISK_INFO 200099E OK
356 [5] Workbench #DISK_INFO 2007FD8 RAM OK
357 [5] Workbench #DISK_INFO 2007FEE DH0 OK
358 [5] Workbench #DISK_INFO 2008004 DF0 OK
359 [5] Workbench ChangeDir SYS:
360 [5] Workbench ChangeDir SYS:
361 [5] Workbench Open ENV:sys/def_DF0.info Read OK
362 [5] Workbench *Open ENV:sys/def_DF0.info Read OK
363 [5] Workbench #FINDINPUT 20AA791, 202B7EF, 20AA7F RAM OK
364 [5] Workbench #SEEK 20400E1, 0, RAM OK
365 [5] Workbench #SEEK 20400E1, 0, FFFFFFF RAM OK
366 [5] Workbench #READ 20400E1, 834588C, 70 RAM OK
367 [5] Workbench #END 20400E1 RAM OK
368 [5] Workbench #DISK_INFO 200801A DH1 OK
369 [5] Workbench #DISK_INFO 2008030 DH2 OK
370 [5] Workbench #INFO 219F899, 217BE32 DH0 OK
371 [5] Workbench #FLUSH (None) DH0 OK
372 [5] Workbench #FLUSH (None) DH0 OK
373 [5] Workbench #FLUSH (None) DH0 OK
374 [5] Workbench #FLUSH (None) DH0 OK

Any idea as to stop the poltergeist?

[Thomas Richter]

This is actually not erratic. The workbench regularly polls all known drives. If a DF0:BAD appears then this means that the file system could not read the disk (for whatever reason) even though the drive indicates that there is something in it.

[Snoopy1234]

Originally Posted by Thomas Richter

This is actually not erratic. The workbench regularly polls all known drives. If a DF0:BAD appears then this means that the file system could not read the disk (for whatever reason) even though the drive indicates that there is something in it.

Thanks for clarifying. This is the 3rd fdd I've put in the A1200, all with the same condition about 12mnths from install. This is happening on DF0: without a disk in the drive. What would cause repeated drives seeing a disk there when not?

[Snoopy1234]

I've commented out "AntiClick" from the User-Startup and the drive hasn't returned to any clicking. Would AntiClick do any damage to the drive over time?

[paul1981]

I've had drives that try and access non-existent disks when the sensors (tiny switches) are dirty in the floppy drive. Nothing WD-40 carefully applied to the switches couldn't fix though. Currently in my main A1200, the write-protect switch is faulty which means sometimes it doesn't see that I have a floppy disk write-protected! I shall get around to it one of these days...

In your case, I wonder if there's a dry joint on the floppy header or something?

When you say 'hasn't returned to any clicking', do you mean it WAS clicking before and now doesn't? I've never heard of AntiClick killing anyone's drive yet.

[Snoopy1234]

Originally Posted by paul1981

I've had drives that try and access non-existent disks when the sensors (tiny switches) are dirty in the floppy drive. Nothing WD-40 carefully applied to the switches couldn't fix though. Currently in my main A1200, the write-protect switch is faulty which means sometimes it doesn't see that I have a floppy disk write-protected! I shall get around to it one of these days...

In your case, I wonder if there's a dry joint on the floppy header or something?

When you say 'hasn't returned to any clicking', do you mean it WAS clicking before and now doesn't? I've never heard of AntiClick killing anyone's drive yet.

Sorry for the belated response. I replaced the drive with a modified ALPS unit and that fixed it but since later I have a new issue with the drive not reading disks from Workbench and the Amiga Guru's. When booting from the drive it is ok. It might be the new ACA 1221ec installed, I think I'll try a different accelerator but it's like running away from the issue...

I also found out Boing Bags 3+4 which are installed replace the Anticlick command in User-Startup with system patched already so no clicking. Removing Anticlick and or NoClick eliminates conflict AFAIK.