From owner-freebsd-questions@FreeBSD.ORG Wed Mar 10 08:46:11 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA5A916A4CE for ; Wed, 10 Mar 2004 08:46:11 -0800 (PST) Received: from mail63.messagelabs.com (mail63.messagelabs.com [216.82.240.51]) by mx1.FreeBSD.org (Postfix) with SMTP id 3B1F043D31 for ; Wed, 10 Mar 2004 08:46:11 -0800 (PST) (envelope-from jason.dictos@yosemitetech.com) X-VirusChecked: Checked X-Env-Sender: jason.dictos@yosemitetech.com X-Msg-Ref: server-11.tower-63.messagelabs.com!1078937169!967359 X-StarScan-Version: 5.1.15; banners=yosemitetech.com,-,- Received: (qmail 12857 invoked from network); 10 Mar 2004 16:46:10 -0000 Received: from mail.tapeware.com (HELO yt-internet.tapeware.com) (4.21.59.10) by server-11.tower-63.messagelabs.com with SMTP; 10 Mar 2004 16:46:10 -0000 Received: by mail.tapeware.com with Internet Mail Service (5.5.2657.72) id ; Wed, 10 Mar 2004 08:49:19 -0800 Message-ID: From: Jason Dictos To: 'Sergey 'DoubleF' Zaharchenko' , Jason Dictos Date: Wed, 10 Mar 2004 08:49:17 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain cc: Dan Nelson cc: "''freebsd-questions@freebsd.org' '" Subject: RE: Using int 13 while BSD is running X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2004 16:46:11 -0000 > To Jason: take care not to *write* anything to the disk via int 13h. > I still don't think I understand why you are using FreeBSD for this specific purpose. Why if you just >spend time escaping from the OS? We actually _like_ protected mode, it allows us to be more flexible and our code doesn't have to be bastardized with 16 dos compilers ;). However in dos we have garanteed hard drive support via int13 (Well almost garanteed, but if an os can boot of the computer, we can access the disk), and I'm looking for the same sorta garantee in BSD. People will be using this with raid controllers, scsi hard disks, and ide drives (Server recovery), so there will be many times when the hardware running the hd requires specific support, which BSD may or may not have, point is we dont' want to manage that. Make sense? -Jason -----Original Message----- From: Sergey 'DoubleF' Zaharchenko [mailto:doublef@tele-kom.ru] Sent: Wednesday, March 10, 2004 5:51 AM To: Jason Dictos Cc: Dan Nelson; ''freebsd-questions@freebsd.org' ' Subject: Re: Using int 13 while BSD is running On Tue, 9 Mar 2004 22:12:31 -0800 Jason Dictos probably wrote: > Aren't the nodes "/dev/ad[0-9] (ide) or /dev/da[0-9] (scsi/usb)" > created by their device drivers, i.e. protected mode device drives? > That would mean that I would have to make sure that the hardware is > supported by a device driver, whereas if I had raw int 13 access I > would be garanteed access to the drive the system booted from, and any > other bios addressable device, without having to load any driver for the hardware. > > -Jason Argh, I didn't get your point first. I thought your hardware wasn't supported by int 13h, and you were trying to get FreeBSD drivers to work for you in real mode... Any real HDD's out there not supported by FreeBSD but supported by BIOS'en? Somewere around then Dan Nelson probably replied: > I guess it's possible, since you have to use the bios to make VESA > video calls, and they work. /sys/i386/isa/vesa.c has most of the > stuff you would need. Also see the i386_vm86() userland function; you > may not even need to mess around inside the kernel. That's v86 mode, not real mode. Sometimes it makes a difference. It depends on how that particular BIOS was written. To Jason: take care not to *write* anything to the disk via int 13h. I still don't think I understand why you are using FreeBSD for this specific purpose. Why if you just spend time escaping from the OS? -- DoubleF All I ask is a chance to prove that money can't make me happy. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________