61
Setup & Installation / Re: DOS VDM: WordStar-for-DOS 7c ("WS") and Borland Quattro Pro ("QP")
« on: November 25, 2023, 07:02:32 am »
Hi Andrew
Not sure which bit may be confusing you...
As you do not seem to be able to boot the system "... we get to the AN logo on a black background... then the m/c runs and runs and runs, going nowhere. I left it for over an hour and a half, without joy." my suggestion is to discover where config.sys "barfs" during boot. This can be done by pressing keys ALT-F2 when OS/2 is displayed at top left of screen - almost immediately after boot starts. This should display drivers loading and will indicate which driver is not loading.
Then you probably need to be able to boot from something - I suggested install media - in order to edit config.sys and resolve non-boot problem.
Come to think of it: If you are running UEFI boot instead of booting install media you can, once you have established what the boot problem is, press ALT-F1 when OS/2 is displayed at top left of screen. This should display a Recovery Menu which includes the option to edit config.sys for this boot. Hopefully that will resolve the non-boot problem.
Regards
Pete
Not sure which bit may be confusing you...
As you do not seem to be able to boot the system "... we get to the AN logo on a black background... then the m/c runs and runs and runs, going nowhere. I left it for over an hour and a half, without joy." my suggestion is to discover where config.sys "barfs" during boot. This can be done by pressing keys ALT-F2 when OS/2 is displayed at top left of screen - almost immediately after boot starts. This should display drivers loading and will indicate which driver is not loading.
Then you probably need to be able to boot from something - I suggested install media - in order to edit config.sys and resolve non-boot problem.
Come to think of it: If you are running UEFI boot instead of booting install media you can, once you have established what the boot problem is, press ALT-F1 when OS/2 is displayed at top left of screen. This should display a Recovery Menu which includes the option to edit config.sys for this boot. Hopefully that will resolve the non-boot problem.
Regards
Pete