home *** CD-ROM | disk | FTP | other *** search
- Debugging info from the problem stated by a previous poster (Machines takeing
- a long time to boot)
-
- stdfile.c:1421; trace info in `futzwithdosdisks': enter macdrives = 0xffffffff
- stdfile.c:1423; trace info in `futzwithdosdisks': i = 0
- stdfile.c:1428; trace info in `futzwithdosdisks': trying to mount 0
- stdfile.c:1423; trace info in `futzwithdosdisks': i = 1
- stdfile.c:1423; trace info in `futzwithdosdisks': i = 2
- stdfile.c:1428; trace info in `futzwithdosdisks': trying to mount 2
- stdfile.c:1423; trace info in `futzwithdosdisks': i = 3
- stdfile.c:1423; trace info in `futzwithdosdisks': i = 4
- stdfile.c:1423; trace info in `futzwithdosdisks': i = 5
- stdfile.c:1423; trace info in `futzwithdosdisks': i = 6
- stdfile.c:1428; trace info in `futzwithdosdisks': trying to mount 6
- (From here up takes *ages*)
-
- stdfile.c:1423; trace info in `futzwithdosdisks': i = 7
- ...
- stdfile.c:1423; trace info in `futzwithdosdisks': i = 31
- stdfile.c:1450; trace info in `futzwithdosdisks': leave
- (These go by reasonably fast)
-
- Seems to be a problem with the CD-ROM mounting code... I've only seen it
- happening on 486 DX2/50's and above (I.e. 486 DX2 80, 486 DX2 66, 486 DX2 50)
-
- (Executor started with no parameters. If you add
- -skipdrives cdfg (E is my cd-rom drive), the startup speed is acceptable)
-
- Running under DOS, no autoexec/config, 486DX2/80, executor 1.99p9+6.
- (Happens with machines without CD-ROMs too, so this does not appear to be
- a factor)
-
-
- So, do I get a chocolate cookie? <GRIN>.
- If you have any questions, I have a machine in front of me which exibits the
- problem.
-
- --
- Allan Stirling
- (INSC2AS1@RIVER.TAY.AC.UK)
-
-