SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 30 | August | 2001 ]

<< Previous Message << >> Next Message >>


Date: Thu, 30 Aug 2001 13:46:29 PDT
From: "mrakijas" <mrakijas@oco.net >
Reply-To: scoug-help@scoug.com
To: <scoug-help@scoug.com >
Subject: SCOUG-Help: Video driver install problem

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

That's it!!! It's fixed. Rerunning SYSINSTX.COM C: on

the drive with it in its absolute location fixed the

problem. I thought I knew enough not to try something

like this but I guess I also thought that there were no

absolute references in the boot code. Everything works

fine now (save for a small Netscape issue to be asked in a

separate thread) and the video driver installed with no

problem. Thanks for the help and patience everyone.

-Rocky
---------- Original Message---------------------------
From: "mrakijas"
Reply-To: scoug-help@scoug.com
Date: Thu, 30 Aug 2001 11:49:22 PDT

>Funky, huh? You'd think that if it thought that
>drive D: was the boot drive, it eventually couldn't
>continue. That could be why the addition of the
>DaniDASD.DMD driver with it's assignable boot drive
>command line argument fixed (or at least helped) to
>allow booting to continue. It must be happening
>before the config.sys is processed. Ahhhh. How's
>this sound? I don't recall the sequence I used but
>I might have done the SYSINSTX command on the drive
>after the XCOPY but before the drive was the lone C:
>drive on the system. Should I redo the SYSINSTX C:
>after I boot to floppy? Could this be it?
>
>> Steven
>
>Thanks again for the help.
>
>-Rocky

______________________________________________________
Sent via the oco.net WebMail Server

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 30 | August | 2001 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.