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 [ 25 | July | 2005 ]

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


Date: Mon, 25 Jul 2005 14:48:45 PDT7
From: J.Pfisterer <pfisterer@gtcinternet.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: OS/2 boot diskette

On Sun, 24 Jul 2005 14:02:29 PDT7, Steven Levine wrote:

>In <20050724010813.B35121FFAE@mail1.gtcinternet.com>, on 07/23/05
> at 06:08 PM, J.Pfisterer said:
>>I'm trying to build an OS/2 bootable diskette, using the
>>from the 1995 New Riders Publishing: OS/2 Certification Handbook.
>>It's based on Warp 3; but I used files from the v4.52 convenience
>>package and my current OS/2 installation.
>
>Use the diskette builder that's on the 4.52 CD. It will produce
>working diskettes that you can optimize for your setup. It's called
>makedisk.cmd or something like that.

The closest thing I could find was g:\cid\server\mpts\makedisk.exe.
That directory suggests it's not what we want; but I tried it on an
empty diskette just to see what would happen. What happened was an
error message saying I hadn't supplied all the required parameters,
and calling for a "source", a "target", and a "d" parameter that I
took to be for a disk number. Looks to me like a utility to create
diskettes from the three disk images for the Warp business server.

>>Attempting to boot from the resulting diskette produces errors:
>> OS/2 !! SYS2025: A disk-read error occurred.
>> OS/2 !! SYS2027: Insert a system diskette and restart the system.
>
>This is probably a bad diskette, what do you have that can check that
>the diskette is readable? Worst case, you can do:
> xcopy /h /o /t /s /e /r /v a:\ c:\tmp
>where c:\tmp can be any handy work directory.

Did that. Everything appeared to copy with no problems.

>>Not very enlightening (as usual). At least it recognizes that it's
>>trying to boot OS/2. CHKDSK reveals no problems with the diskette.
>
>Chkdsk does not read every sector, so this is not unexpected.
>
> chkdsk /v a:
>reads some more of the diskette, but it is still only a partial read.

Did that. No errors reported.

>>Copied from the convenience package CD:
>> 10-29-01 9:00p 849,407 0 a--- OS2KRNLI
>
>This is correct because you need to be prompted for the 2nd and 3rd
>diskette.
>
>> (Also tried with OS2KRNLI renamed to OS2KRNL)
>> 10-29-01 9:56p 44,544 0 a--- OS2LDR
>> 10-29-01 8:38p 8,878 0 a--- OS2LDR.MSG
>> 10-03-01 6:35a 25,507 0 a--- KEYBOARD.DCP
>> 10-26-01 10:09a 4,240 0 a--- SYSINST1.EXE
>> 10-27-01 10:51p 32,336 0 a--- SIPANEL1.DLL
>
>This will never work. Warp4 is simply too big for a single diskette
>boot.

At one time I had a 2-diskette boot set, one 3.5" and one 5.25" that
worked well together. Unfortunately, I can't find a trace of them
since our big move.

>You have two problems. A bad diskette and a bad build process.

Certainly the latter :(

Then on Sun, 24 Jul 2005 14:03:58 PDT7 "Steven Levine" wrote:

>In <20050724195549.0A7F41FFD0@mail1.gtcinternet.com>, on 07/24/05
> at 12:55 PM, J.Pfisterer said:
>>I had tried using the eCS CD #1 with the HD in its present state.
>>It boots, displays a few confirmations, the last of which is "CD Rom
>>emulation terminated", flashes two presumably-error-messages too fast
>>to read and then reboots in an endless sequence. My guess is that it

>>can't see the unformatted partitions that are intended for it; so am
>>hoping that formatting them will help.

It appears you have not told us the whole story. Is this a new
system? Your old system had none of these problems.

Yes, a new system; but wanted to focus on the boot diskette problem.
The constructed boot diskette performs (fails) exactly the same way
on both new and old boxes.

Thanks, Steven.

Jack P.

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

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
"postmaster@scoug.com".

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


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

Return to [ 25 | July | 2005 ]



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.