From owner-freebsd-questions  Tue Sep  5 22: 4:48 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from web5105.mail.yahoo.com (web5105.mail.yahoo.com [216.115.106.75])
	by hub.freebsd.org (Postfix) with SMTP id 1F60437B422
	for <questions@freebsd.org>; Tue,  5 Sep 2000 22:04:46 -0700 (PDT)
Message-ID: <20000906050445.29822.qmail@web5105.mail.yahoo.com>
Received: from [203.11.192.243] by web5105.mail.yahoo.com; Wed, 06 Sep 2000 15:04:45 EST
Date: Wed, 6 Sep 2000 15:04:45 +1000 (EST)
From: =?iso-8859-1?q?Paul=20Jansen?= <vlaero@yahoo.com.au>
Subject: Re: extracting bootblock from dos 6.22 boot floppy (FreeBSD 4.1)
To: Rick Hamell <hamellr@heorot.1nova.com>
Cc: questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Rick,

the mknbi docs (mknbi-dos in particular) are
interesting reading.  According to these docs (and
people on the etherboot mailing list) it is possible
to do this.
This is why I am investigating this option:

I want to have a dos client set up to connect to a
Windows Terminal server.  I know there is a Citrix ICA
client for Dos that can be set up from a floppy but
the terminal servers I want to connect to don't have
Metaframe installed. Also video performance under the
dos ICA client when doing web browsing etc. is quite
ordinary.  Using Windows 3.x or above with the
appropriate display driver for your video card greatly
improves video speed.
The problem I have is the terminal server I need to
connect to may not be on the local subnet.  You cannot
configure windows 3.x to run windows from off a TCP/IP
network attached drive and then use the winsock TCP
features within the windows session (Windows terminal
server client uses winsock).  You can however
configure windows with Netbeui or IPX along with
TCP/IP-32.  It can then run windows off the Netbeui or
IPX mounted network drive and then start TCP/IP-32
once windows has loaded.  I don't have the flexibility
of having a Netbeui or IPX server on the local
ethernet.

Network booting will be a much faster, cleaner option.
 The Windows 3.x image that needs to be network booted
is <20MB so it's not that big.

I've been told that I can use the dd command with rfd0
to get the bootblock off the floppy.  I'll try that
tongiht and see how it goes.

Cheers,
Paul

--- Rick Hamell <hamellr@heorot.1nova.com> wrote: > 
> > I believe this process should should allow this
> other
> > floppy disk to be a bootable msdos 6.22 floppy
> after
> > the steps described above are performed.  This
> results
> > in the error message:
> > 
> > non-system disk or disk error
> > replace and press any key when ready
> > 
> > Can someone tell me what I'm doing wrong here?
> 
> 	I don't think what you're doing is really possible
> with the DOS
> fat tables. Microsoft got around it by writing a
> propritary FAT table with
> the Windows 95 and Word 95 floppy disks. Why do you
> need extra room on the
> disks? You can use the DOS TCP/IP Networking stuff
> off of the Windows NT
> 4.0 disk and their web site to create a boot disk
> that would do just about
> everything you need. Load Samba on the server, and
> you could simply run a
> terminal program off of the share that automatically
> connects back to the
> same server.
> 
> 					Rick
> 


_____________________________________________________________________________
http://geocities.yahoo.com.au - Yahoo! Australia & NZ GeoCities
- Build your own Web Site - for free!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message