Re: [Freedos-user] VMWare, MSClient, Marvell Yukon - controller not found

2012-09-19 Thread George Brooks
Thanks for your reply.  (Note the addition of the original, apparently not 
sent, subject.)


While netbootdisk.com looks interesting it is not a feasible solution here.  
For one, the machine does not have a floppy drive!  Plus, my OS is Win7, which 
does not create bootable floppies.

I did see that netbootdisk will find the Marvell Yukon card and use the same 
driver that I have.  My problem is not that the I can't find the right driver.  
It's that the driver does not see that the controller is present.  I don't 
know enough about the MSClient process to tell whether this is the fault of the 
driver (yuknd.dos) or the configuration of protocol.ini.  That file is 
borrowed from this discussion.  I also added the appropriate lines to 
fdconfig.sys.


I remain stumped.

George




 From: Alain Mouette ala...@pobox.com
To: George Brooks truckeetr...@yahoo.com; Discussion and general questions 
about FreeDOS. freedos-user@lists.sourceforge.net 
Sent: Wednesday, September 19, 2012 4:01 PM
Subject: Re: [Freedos-user] (no subject)
 
I can do it this way:

1) configure VMware as Bridge PCnet NIC
2) use the drivers from netbootdisk.com for the driver inside VMware. 
the guy there is making an excelent job of collecting new drivers

It just works...

Alain

Em 19-09-2012 19:53, George Brooks escreveu:
 I'm experimenting with FreeDOS in an effort to find a solution for
 access to a legacy DOS application. The environment is an HP laptop
 (6730s) running Win7 32-bit, VMWare Player v5 and FreeDOS 1.1. All
 proceeds smoothly until I try to gain access to a printer share via
 MSClient. (This is the only way I can see to get the application to
 print.) The challenge occurs when attempting to load the driver for the
 laptop's ethernet card - a Marvell Yukon. The driver is named yuknd.dos.

 I've tried a number of configurations based on postings found on the
 web. In an effort to narrow the problem down I entered the following
 into fdconfig.sys:

 device=c:\net\yuknd.dos

 When stepping thru boot, this line results in the error message
 Controller not found. What means, if any, are available to get over
 this? (The laptop also has wireless, but I suspect that is even more
 highly problematic.)

 Many thanks for sharing your wisdom.

 George

 ps: my apologies if my lack of understanding of lists has caused this to
 be a duplicate posting.


 --
 Live Security Virtual Conference
 Exclusive live event will cover all the ways today's security and
 threat landscape has changed and how IT managers can respond. Discussions
 will include endpoint security, mobile security and the latest in malware
 threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/



 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] VMWare, MSClient, Marvell Yukon - controller not found

2012-09-19 Thread George Brooks
Alain,

Thanks for the link.  I'll try to make an iso here.  I downloaded the iso from 
the link you provided, booted it to get:

Processing archive...FILES.HUA
ERROR: Not enough memory
Process aborted
Bad command or file name

More fun to be had with this...

George



 From: Alain Mouette ala...@pobox.com
To: George Brooks truckeetr...@yahoo.com 
Sent: Wednesday, September 19, 2012 6:09 PM
Subject: Re: VMWare, MSClient, Marvell Yukon - controller not found
 
Yes, use a CD burning software to breate a bootable CD with the 
netbootdisk image. It is explained in the site, or use this:
http://suporte.cosmodata.com.br/downloads/moni/netbootdisk65.iso

You don want the driver for your phisical board, but for one of the 
virtual boards inside VMware.

much easier then what you are trying to do

Alain

Em 19-09-2012 21:54, George Brooks escreveu:
 Thanks for your reply. (Note the addition of the original, apparently
 not sent, subject.)

 While netbootdisk.com looks interesting it is not
 a feasible solution
 here. For one, the machine does not have a floppy drive! Plus, my OS is
 Win7, which does not create bootable floppies.

 I did see that netbootdisk will find the Marvell Yukon card and use the
 same driver that I have. My problem is not that the I can't find the
 right driver. It's that the driver does not see that the controller is
 present. I don't know enough about the MSClient process to tell whether
 this is the fault of the driver (yuknd.dos) or the configuration of
 protocol.ini. That file is borrowed from this discussion
 http://www.computerhope.com/forum/index.php?topic=121970.0;wap. I also
 added the appropriate lines to fdconfig.sys.

 I remain stumped.

 George


 
 *From:* Alain Mouette ala...@pobox.com
 *To:* George Brooks truckeetr...@yahoo.com; Discussion and general
 questions about FreeDOS. freedos-user@lists.sourceforge.net
 *Sent:* Wednesday, September 19, 2012 4:01 PM
 *Subject:* Re: [Freedos-user] (no subject)

 I can do it this way:

 1) configure VMware as Bridge PCnet NIC
 2) use the drivers from netbootdisk.com for the driver inside VMware.
 the guy there is making an excelent job of collecting new drivers

 It just works...


 Alain

 Em 19-09-2012 19:53, George Brooks escreveu:
   I'm experimenting with FreeDOS in an effort to find a solution for
   access to a legacy DOS application. The environment is an HP laptop
   (6730s) running Win7 32-bit, VMWare Player v5 and FreeDOS 1.1. All
   proceeds smoothly until I try to gain access to a printer share via
   MSClient. (This is the only way I can see to get the application to
   print.) The challenge occurs when attempting to load the driver for the
   laptop's ethernet card - a Marvell Yukon. The driver is named yuknd.dos.
  
   I've tried a number of configurations based on postings found on the
   web. In an effort to narrow the problem down I entered the following
   into fdconfig.sys:
  
  
 device=c:\net\yuknd.dos
  
   When stepping thru boot, this line results in the error message
   Controller not found. What means, if any, are available to get over
   this? (The laptop also has wireless, but I suspect that is even more
   highly problematic.)
  
   Many thanks for sharing your wisdom.
  
   George
  
   ps: my apologies if my lack of understanding of lists has caused this to
   be a duplicate posting.
  
  
  
 --
   Live Security Virtual Conference
   Exclusive live event will cover all the ways today's security and
   threat landscape has changed and how IT managers
 can respond. Discussions
   will include endpoint security, mobile security and the latest in malware
   threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
  
  
  
   ___
   Freedos-user mailing list
   Freedos-user@lists.sourceforge.net
 mailto:Freedos-user@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/freedos-user

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user