| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 36684 | 2003-08-16 12:08:00 | Win 95B won't accept any autoexec.bat! | Robin S_ (86) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 168244 | 2003-08-21 07:11:00 | No bells are rung :( I wonder if it would be worthwhile re-installing the system files from a win95 boot disk, ie a:\>sys c: , so that there is a new IO.sys and msdos.sys, just in case there is something funny with them. | Terry Porritt (14) | ||
| 168245 | 2003-08-22 03:02:00 | Yes. I can't think of any "proper" way the software should behave like this. So it must be improper. :D | Graham L (2) | ||
| 168246 | 2003-08-23 10:55:00 | Thanks for the system files idea, Terry. That gives me a few other ideas too so I'll do some more trials as soon as I get a chance and report back. | Robin S_ (86) | ||
| 168247 | 2003-08-27 13:02:00 | Je l'ai trouve! By chance! Terry, I tried redoing the system files as you suggested but to no avail (I thought it might work as it was possible I had originally run the sys command from a DOS 6.22 or 6.20 boot disc). But on my list of other things to try was suppressing the startup splash screen in case it was hiding any startup messages. And lo! with the logo off a/e.bat worked. I have now installed the a/e commands that I wanted (I decided to leave out share.exe) and everything goes. It doesn't explain why there was no problem with an earlier version of Win 95 and I might try the logo.sys file from an earlier version sometime. It would appear that there was a conflict somewhere in the BIOS/Win 95B or something combination as the problem did not occur when the same version of Win 95B was tried on 2 other computers. Thanks to all who offered suggestions. Any thoughts now on how/why this came about? Robin |
Robin S_ (86) | ||
| 168248 | 2003-08-27 18:17:00 | IRQ or I/O address conflict maybe. | mark.p (383) | ||
| 168249 | 2003-08-27 21:14:00 | Well, that is probably going to remain one the great mysteries of life, the universe and everything, Robin. Logo.sys is just a bitmap file, it's a nuisance anyway as it obscures the text screen 'underneath' and you cant see what is happening. IO.sys reads msdos.sys before reading config.sys and autoexec.bat, and msdos.sys determines the win start configuration. Difficult to know why msdos.sys was saying ignore the autoexec.bat. It isnt an IRQ problem Mark, as at that stage of the boot, there are only the preset IRQs from the BIOS, and logo.sys is not a device anyway. The answer must be 42 :) |
Terry Porritt (14) | ||
| 168250 | 2003-08-28 03:55:00 | Or, in an alternative numeric base, "MS". | Graham L (2) | ||
| 168251 | 2003-08-29 07:09:00 | Isn't it trying to load mouse.com? 69 is a great number........................;) |
mark.p (383) | ||
| 168252 | 2003-08-29 07:21:00 | Well, it would load mouse.com if only it accepted an autoexec.bat in the first place. I must say it is all very strange. Generally it is not a good idea to load real mode drivers like mouse or cdrom that windows itself will try to load later in protected mode. That can certainly cause conflicts in some cases. |
Terry Porritt (14) | ||
| 168253 | 2003-08-29 12:48:00 | Thanks Terry, I thought logo.sys was a bitmap file, but it's mighty big for a bitmap. It might have something to do with the animation of the bottom banner strip. Incidentally, I have read somewhere that that banner can be used as an indicator of the version of Win 95, according to the direction and speed in which the colour patches run. I also have a reference that states that some 3rd party memory managers conflict with the Windows startup logo. I don't have any but in my case I suspect the problem lies in the Win 95B version of the logo file or the way it is handled. | Robin S_ (86) | ||
| 1 2 3 | |||||