🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.os.os2.bugs
7 messages
7 total messages Started by robin Thu, 13 May 1999 00:00
Help, lost dual boot
#69
Author: robin
Date: Thu, 13 May 1999 00:00
14 lines
1065 bytes
Suddenly I can't dual boot.  I'm stuck in DOS.
An attempt to dual boot back to OS/2 gives the message:

SYS1313 An error has occurred while reading or writing to the
hard disc partition.

which occurs immediately after giving the command
to dual boot.

Does anyone know how to recover from this problem?
I suspect that it occurs when the boot sector is being
re-written so as to start up OS/2.

Thanks, Robin
Re: Help, lost dual boot
#70
Author: Frank McKenney
Date: Sat, 15 May 1999 00:00
49 lines
2450 bytes
In <zyJ_2.30040$MB3.45468@newsfeeds.bigpond.com>, robin <robin_v@bigpond.com> writes:
>Suddenly I can't dual boot.  I'm stuck in DOS.
>An attempt to dual boot back to OS/2 gives the message:
>
>SYS1313 An error has occurred while reading or writing to the
>hard disc partition.
>
>which occurs immediately after giving the command
>to dual boot.
>
>Does anyone know how to recover from this problem?
>I suspect that it occurs when the boot sector is being
>re-written so as to start up OS/2.

In most cases I've seen, this type of error message appears when the
OS/2 boot record has been successfully written to the C:  partition boot
record location, but for some reason the DOS C:\AUTOEXEC.BAT and
C:\CONFIG.SYS files are still in the root directory.

Boot from a floppy and check your C:\OS2\SYSTEM directory for *.DOS or 
*.OS2 files. When you are "correctly" in "boot DOS" mode, the 
following files should be present:

    BOOT.OS2
    CONFIG.OS2
    AUTOEXEC.OS2

If you are in "boot OS/2" mode (e.g. following a successful BOOT /OS2 
command), the following files should be present:

    BOOT.DOS
    CONFIG.DOS
    AUTOEXEC.DOS

I'd recommend making copies of the relevant files in the root directory
and C:\OS2\SYSTEM onto a flooy disk before doing anything else.  Once
you;ve done this, put the appropriate AUTOEXEC and CONFIG files into the
root directory of C:.  You should be able to boot at his point.

Next, if you've just booted OS/2, make sure DOS versions of the boot
sector, AUTOEXEC.BAT, and CONFIG.SYS are in C:\OS2\SYSTEM.  This will
let you switch back to DOS with the BOOT command.

Hope this helps...


Frank McKenney, McKenney Associates / OS2BBS OS/2 Advisor          
Richmond, Virginia   (804) 320-4887
Internet: frank_mckenney@mindspring.com / TalkLink: WZ01123        
Re: Help, lost dual boot
#71
Author: Jack McDowell
Date: Sun, 16 May 1999 00:00
46 lines
2580 bytes
Robin,

The most likely cause of this problem is that you have booted to DOS
while you were already in the DOS operating system.  Or the reverse,
booting to OS/2 while you were in OS/2.  What appears to happen is that
the image files for the BOOT TO system are written before the
application recognizes that it is at the wrong place.  Then it tells
you about it.  Unfortunately, ...

It is possible to recover.  Not easy, but possible.  You could try
correcting the image files for the alternate operating system.  They are
probably in ?:\OS2\BOOT or the ?:\.

Alternate:  BOOT /OS2, (Yes you get the error message.)
                Boot from diskette
                Execute SYSINSTX C:\  from your diskettes.
                This should allow you to bootup in OS/2.  Now
                BOOT /DOS  (If it works fine.)
                If not, boot from your DOS diskettes and use SYS C:

Sorry, about possible reference errors.  I am writing this using WIN98
because I cannot locate working (and documented) OS/2 drivers for this
embedded Lucent DSP modem.  Thus, I cannot check the references.

This problem seems to occur most frequently to users who prefer to use
FULL SCREEN OS/2 sessions.  It is easy to forget whether you are in DOS
or OS/2 when returning from a short break.

Jack

robin wrote:

> Suddenly I can't dual boot.  I'm stuck in DOS.
> An attempt to dual boot back to OS/2 gives the message:
>
> SYS1313 An error has occurred while reading or writing to the
> hard disc partition.
>
> which occurs immediately after giving the command
> to dual boot.
>
> Does anyone know how to recover from this problem?
> I suspect that it occurs when the boot sector is being
> re-written so as to start up OS/2.
>
> Thanks, Robin
LT Modem [was: lost dual boot]
#65
Author: George Durbridge
Date: Sun, 23 May 1999 00:00
9 lines
931 bytes
Jack McDowell (jrmcd@ibm.net) wrote:
: I cannot locate working (and documented) OS/2 drivers for this
: embedded Lucent DSP modem. 

Neither can I.  Would you post the result, if you do ?

--
/* George Durbridge  Melbourne, Victoria, Australia */
/* tel (03) 9280 3390            fax (03) 9280 3288 */
Re: LT Modem [was: lost dual boot]
#66
Author: Mark Schlegel
Date: Mon, 24 May 1999 00:00
25 lines
1585 bytes
George Durbridge wrote:
: Jack McDowell (jrmcd@ibm.net) wrote:
: : I cannot locate working (and documented) OS/2 drivers for this
: : embedded Lucent DSP modem. 

: Neither can I.  Would you post the result, if you do ?

: --
: /* George Durbridge  Melbourne, Victoria, Australia */
: /* tel (03) 9280 3390            fax (03) 9280 3288 */

It depends on the hardware, there are LT modem drivers for
the thinkpads (at least some of them).  I've personally
run the LT modem in the thinkpad 390 with these drivers

you can find the thinkpad 390 driver in www.pc.ibm.com

http://www.pc.ibm.com/qtechinfo/LWIK-3ZUQ9D.html

However, once running, the speed is subpar (I only
got 26k on the LT embedded that they called a 56k
modem) and it seems to use a lot of cpu (I could feel how
hot the bottom of the thinkpad would get.)

Mark
Re: LT Modem [was: lost dual boot]
#67
Author: Bob Germer
Date: Thu, 27 May 1999 00:00
21 lines
1579 bytes
On <7i8sb4$261$3@llama.teragen.com.au>, on 05/23/99 at 12:29 PM,
   gdurb@aardvark.apana.org.au (George Durbridge) said:

> Jack McDowell (jrmcd@ibm.net) wrote:
> : I cannot locate working (and documented) OS/2 drivers for this
> : embedded Lucent DSP modem. 

> Neither can I.  Would you post the result, if you do ?

For my ThinkPad 390E, there is a driver for the LT modem which is, of
course, a WinModem. It works only at V.34bis speed (33600) in Warp but as
a V.90 modem in Win9x. According to the Operating Systems group at IBM,
Lucent has no intention of writing a driver for OS/2 for this modem.

--
----------------------------------------------------------------------------------------------
Bob Germer from Mount Holly, NJ - E-mail: bobg@Pics.com
Proudly running OS/2 Warp 4.0 w/ FixPack 8
MR/2 Ice Registration Number 67
Aut Pax Aut Bellum
----------------------------------------------------------------------------------------------
Re: LT Modem [was: lost dual boot]
#68
Author: George Durbridge
Date: Thu, 27 May 1999 00:00
16 lines
1301 bytes
It'll have to be bellum, then ?

Bob Germer (bobg.REMOVEME.@pics.com) wrote:

: For my ThinkPad 390E, there is a driver for the LT modem which is, of
: course, a WinModem. It works only at V.34bis speed (33600) in Warp but as
: a V.90 modem in Win9x. According to the Operating Systems group at IBM,
: Lucent has no intention of writing a driver for OS/2 for this modem.

: --------------------------------------------------------------------
: Aut Pax Aut Bellum
: --------------------------------------------------------------------

--
/* George Durbridge  Melbourne, Victoria, Australia */
/* tel (03) 9280 3390            fax (03) 9280 3288 */
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads