[syslinux] Re: WinME command.com

Sat Jun 14 12:06:39 PDT 2003

Hi..

Well i've tried each and every method to insert any winme command.com into 
any bootable image and its really giving me problems....
I even further tested the same image with reinserting the 98 command.com and 
the image worked just fine.. So acc to me the problem has to lie in me 
command.com as there is no real mode dos in ME..

Also try using umbpci.sys and lowdma.sys for managing memory in dos instead 
of emm386 or qemm386..

I suppose you better try out the Universal Boot Disk of Ramattack.. it'll 
give you all the solutions.

Bye.
Jassi

>From: syslinux-request at zytor.com
>Reply-To: syslinux at zytor.com
>To: syslinux at zytor.com
>Subject: SYSLINUX Digest, Vol 3, Issue 3
>Date: Tue, 3 Jun 2003 12:00:25 -0700
>
>Send SYSLINUX mailing list submissions to
>	syslinux at zytor.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://www.zytor.com/mailman/listinfo/syslinux
>or, via email, send a message with subject or body 'help' to
>	syslinux-request at zytor.com
>
>You can reach the person managing the list at
>	syslinux-owner at zytor.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of SYSLINUX digest..."
>
>
>Today's Topics:
>
>    1. Re: pxelinux 2.04 dumps vmmon, was Re: [syslinux] load
>       pxelinux w/o	PXE BIOS? (Michael Blandford)
>    2. Re: WinME command.com (was Re: Problems with Memdisk	2.04)
>       (Andreas Kneiseler)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Mon, 02 Jun 2003 13:05:14 -0700
>From: Michael Blandford <mlblandf at sedona.ch.intel.com>
>Subject: Re: pxelinux 2.04 dumps vmmon, was Re: [syslinux] load
>	pxelinux w/o	PXE BIOS?
>To: hm at seneca.muc.de
>Cc: sales at vmware.com, Michael Blandford
>	<mlblandf at sedona.ch.intel.com>,	Support at ArgonTechnology.com,
>	syslinux at zytor.com
>Message-ID: <3EDBADFA.4040706 at sedona.intel.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>hm at seneca.muc.de wrote:
>
> >Anyway I tried pxelinux-2.03 now instead of 2.04 which produces the 
>crash.
> >2.03 works slooooooow within a VM but it works. It actually takes more
> >than 5 minutes to TFTP a 900KB kernel and a 5MB initrd. Which makes it
> >like 20-25 KB/s.
> >
> >Does anybody have an idea what _is_ so slow here?
> >
> >- Is it pxelinux' TFTP client within a VM?
> >
> >
>I am not sure of the cause.  However, using the rfbg floppy on a real
>box is very fast.  It is definitely a vmware/pxelinux related issue.
>
>I would be happy to help diagnose this problem is someone has some
>insight as to what to try.
>
> >To recapitulate: as for the crash, this is VMware WS 4.00-4460 w/
> >pxelinux 2.04. The warning "You do not have VMware tools installed"
> >isn't very meaningful here because you install them in a guest OS as
> >soon as it is installed, not before.
> >
> >
>Does the vmware log give you any more insight/data?
>
>Michael
>
>
>
>------------------------------
>
>Message: 2
>Date: Tue, 3 Jun 2003 07:01:49 +0200
>From: "Andreas Kneiseler" <Andreas.Kneiseler at aumav.verwalt-berlin.de>
>Subject: [syslinux] Re: WinME command.com (was Re: Problems with
>	Memdisk	2.04)
>To: "SYSLINUX PXE ISO9660" <SYSLINUX at zytor.com>
>Message-ID: <002101c3298d$3d75be40$db021c0a at aumav.verwaltberlin.de>
>Content-Type: text/plain;	charset="iso-8859-1"
>
>Hi,
>
>I've got the same Problem. Not with WinMe but Win 98SE. But what I figured
>out is,
>that it doesn't realy apply to the Command.com rather to the Way the
>BootImage was created.
>It took me a long time to get my Hands on a Image with 2.8MB that's 
>working.
>Since creating one
>my self, was allways failling. I downloaded the Bootutils 4.3 from 3com and
>used the Imageedit tools.
>With these tools it should be possible to to read in an bootable Disk and
>extend this one to I think
>16MB none exept the original Size of 1.44M worked for me. So searched the
>Net and finaly found a
>2.8M Image where I could boot from. deleted all the files in side of it and
>put DOS7(win98se) german in it.
>And I could getit to work.
>
>Now I'm having another problem "MEMORY" with out any thing loaded I've got
>517KB for DOS, loading himem.sys and emm386.exe couldn't help me as much as
>I was hoping.
>since I'm loading a lot of network stuff, most of it get's load in to the
>normal memory, 'cause
>EMM can't get his hands on some MEM-Pages to switch Frames to the Rest of 
>my
>unused 256MB,
>because of low free addresses (Axxx-Fxxx) I think MEMDISK and/or the
>DiskImage is sitting in it.
>
>I was trying to get a share on the SAMBA-Server for accessing Images with
>ghost 7.5.
>We have a couple motherboards from different firms and what I figured out 
>is
>the available Memory
>is not equal on every configuration. On some Platforms it's working out of
>the Box and on some
>ghost is complaining low memory. Other than this when I restore or save an
>Image with ghost 7.5
>the server has a havy duty serving the client so that other clients having
>slower access to there shares.
>
>OK I thought, let's give NFS a try. But since the normal TCP-Stack from MS
>is not all to make NFS Happy,
>I need to load another MS-Utility called sockets.exe, only ca. 330K Mem 
>left
>for operations. So I tried
>(SUN's PC-NFS 5.1, Netmanages Versions) I found another inside of the SuSE
>distris. Since I only
>need the client Stuff I thought It can't be that bad. Boom it is.
>
>The reason is, why I'm using the client found on the SuSE distries, is that
>SUN's and NetMange NFS
>clients are also Server, and need those registrations. but when I'm working
>on a Image in one House
>and some one else is working on another one, I've got the Problem, that the
>cleint will figure out, that
>the Serialnumber that I used to create the Image is already used by some 
>one
>else and will create
>an error Message that I've got 10 Minutes to go until the NFS-Driver stops
>working.
>
>I was looking at the "NETBOOT V 0.9.8" they do I think almost the same, you
>are loading the initial
>bootloader and right after this your boot Image, and inside the BootImage
>there is a special driver
>for a RAMDISK, as fas as I understood this stuff, that will load the whole
>initial Ramdisk into another
>one at a higher region of Memory and destroy the initial one.
>
>I tried the driver with memdisk, but the driver complained, that it could
>find the initial RAMDISK.
>Than I tried to build a disk Image with the tools from NETBOOT mknbi-dos 
>but
>it wouldn't boot
>because I think they are building some kind of bootsector the memdisk don't
>like.
>
>Like I said at the Top, I don't think it is a command.com problem rather
>than a problem
>with the Bootsector of the Image in use.
>
>I tried this stuff with
>
>dd, mkdosfs, copying all the stuff in it.
>dd, fdisk, mkdosfs, copying
>A small partition on a HD, format /s, copying , dd from it
>
>Then mkdiskimage from the syslinux (2.05-pre1)
>
>None of this stuff worked out for me.
>the only Image which was bigger then 1.4M, was the one I downloaded from 
>the
>Internet.
>
>All the other Images stopped working right after
>
>.
>.
>Loading Boot secotr ... Booting ...
>
>
>Any advice what I'm doping wrong here ??
>
>I'm trying this boot and memory stuff now for more than 2 weeks.
>Searching the Internet for Ideas.
>
>What I need is, MS-TCP/IP with maybe some sort of SMB- in it and
>a free nfs-client to experiment with, since I know how it works with SMB.
>As far as I collected Information NFS with UDP-Transfers, since it is 
>faster
>than
>TCP, none of my clients are runnig over router, so the UDP-Stuff shouldn't
>be a problem
>except it's faster.
>
>What would help also is a configuration advise how to setup DHCP with TFTP
>to
>get a Multicast Stuff working with a simple packetdriver loaded instead of
>the
>MS-TCP/IP stack.
>
>My current configuration is a mixture of MS-Stack, bundled with a patched
>version
>from the last dis_pkt9 Package. Plus a huge enviroment-Variables Pointing 
>to
>the Serving DHCP-Server, MAC-Address, IP-Adress, Netmask, STD-GW etc.
>Frome those ENV-Variables I created some DOS-Names (one depending on the
>MAC-Adress,
>one debending on the IP-Adress, everyone created with a bunch of AWK and
>SED-Scripts)
>to do a quick and flexible Client-Depending Backup and Restore, build 
>inside
>of a Menu.
>
>If somebody has interess looking what I've did so far, please Mail me.
>
>By the way does anybody has a DOS-Version of NSLOOKUP, ARP, TRACEROUTE that
>works with the
>MS-TCP/IP-Stack (Freeware please) I could find any.
>
>I wish every one a nice Day
>
>Andy
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Andreas Kneiseler
>Netzwerk-Management & Security
>AUMAV (Automatisiertes Mahnverfahren)
>Amtsgericht Wedding
>13357 Berlin
>Brunnenplatz 1
>Tel.:  +49-(0)30-9(0)156-671
>FAX : +49-(0)30-9(0)156-203
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>------------------------------
>
>_______________________________________________
>SYSLINUX mailing list
>Submissions to SYSLINUX at zytor.com
>Unsubscribe or set options at:
>http://www.zytor.com/mailman/listinfo/syslinux
>Please do not send private replies to mailing list traffic.
>
>
>End of SYSLINUX Digest, Vol 3, Issue 3
>**************************************

_________________________________________________________________
Attention NRIs! Send money home in a jiffy. 
http://server1.msn.co.in/msnleads/citibankrca/citibankrca2.asp