registry team mailing list archive

[peter b <441835@xxxxxxxxxxxxxxxxxx>]

yes Martin, taken and v clear; so, pls check my logic/procedure flow
about this whole issue

- kernel detects/not detects the presence of floppy controller (v fast - 20 sec delays non-existent; let the BIOS think whatever it wants)
- feedback - y or n - stored
- IF n then DO NOT even bother/SKIP altogether the talking to/or trying to talk TO A non-existent floppy drive/device routine; (if there is NO floppy controller obviously there CAN NOT BE floppy drive (20 sec delays non existent)
- IF y then GOTO probing the presence of floppy device/drive routine
         - probe the presence of a floppy device/drive attached to the controller BUT as said previously - run the do/while loop with a timer set for a max/tops 3-4 sec (I think this 3-4 sec delay would be acceptable or, maybe, even less, maybe 2 sec ? I think that a conclusive y or n feedback will be obtained from 4-5 iterations max; or, maybe, do it in assembler ?)
         - feedback y or n stored
               - IF y then GOTO configure floppy /device/drive routine (v fast - 20 sec delay non-existent .....'If there is an actual floppy drive, there is no problem.'....) 
os installation continues
               - IF n then CREATE and STORE 'floppy drive NOT PRESENT/INSTALLED' file.
os installation continues
- after install finished display for user's attention/information either on the login screen or after login on user's/admin's desktop for say 5-6 sec.  'floppy drive NOT PRESENT/INSTALLED' message.

what's your opinion Martin, pls ? will it do the trick ?

-- 
Clicking on floppy gives "no device media found"
https://bugs.launchpad.net/bugs/441835
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for udev.