Re: [Freedos-user] Freedos-user Digest, Vol 635, Issue 1
--- Was the printer both plugged in and powered on? The most likely problem is that you have more than one USB host controller. If you simply do a USBUHCI or USBUHCIL to install the driver for the USB host controller, it will only install the driver for the first host controller (Index 0). That may not be the host controller that the printer is plugged into. Start by doing a USBHOSTS to see how many UHCI controllers the computer has, and then try installing USBUHCIL with the different Indexes (USBUHCIL /Index:#), where # are the different indexes (0 through however many controllers you have). That's the shotgun approach that will probably get you going. If it doesn't, there are many more extensive troubleshooting steps we can perform, but they are complicated to work through. --- Hey, thanks for your help. I actually found out from HP that my printer is not compatible with DOS at all. I tried loading the USBUHCIL and then running USBPRINT. The program beeped, indicating the printer is bad. So, that settles it. I'm trading printers for an older one that should work with DOS (an HP Deskjet 932c), or something. -- 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
Re: [Freedos-user] UIDE Diskette Change Line Capability Tests.
Jack: Are you more interested in actually getting your program to work, or in trying to prove that you're smarter than everybody else? Let's take this from the perspective of someone trying to write a BIOS. If I were trying to do that, I would do my due diligence and obtain as many references as I could. This would include BIOS Central, RBIL, and as many hard books as I could reasonably get hold of. Some people have been doing research on this in the background, and nobody yet has reported a hard book saying anything at all 40:8F. BIOS Central says one thing, RBIL says another. Which one is right? Maybe both (different BIOS's on different computers), maybe neither. I do know that both of these are secondary, not primary, sources. At least some of their information is gathered by experimentation on specific computers, and can be pure conjecture. Extrapolating information from specific computers and applying it to all computers is, at best, reckless. Which one do I believe? I can't believe either one. I need another source of corroboration, one that I know didn't just copy their information from BIOS Central or RBIL. So, I go to a primary, official source -- The IBM Technical Reference (it doesn't get any more official or primary than that). The IBM PS/2 Technical Reference from 1991 simply says that 40:8F is Reserved. So, what do I do with 40:8F in my BIOS? The short answer is, I can do anything I want. If somebody points the finger back at me and says, It should work like BIOS Central says, I can laugh and say, Says who? BIOS Central does not have any more credibility than RBIL, and neither one of them can touch IBM. UIDE is using an undocumented and unverifiable feature and needs to be fixed. VirtualBox is following the rules. -- 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
Re: [Freedos-user] Freedos-user Digest, Vol 635, Issue 1
I'll also try the things you've suggested before I trade to see if it will work. On Thu, May 24, 2012 at 11:06 AM, Kenny Emond cheeseylem...@gmail.comwrote: --- Was the printer both plugged in and powered on? The most likely problem is that you have more than one USB host controller. If you simply do a USBUHCI or USBUHCIL to install the driver for the USB host controller, it will only install the driver for the first host controller (Index 0). That may not be the host controller that the printer is plugged into. Start by doing a USBHOSTS to see how many UHCI controllers the computer has, and then try installing USBUHCIL with the different Indexes (USBUHCIL /Index:#), where # are the different indexes (0 through however many controllers you have). That's the shotgun approach that will probably get you going. If it doesn't, there are many more extensive troubleshooting steps we can perform, but they are complicated to work through. --- Hey, thanks for your help. I actually found out from HP that my printer is not compatible with DOS at all. I tried loading the USBUHCIL and then running USBPRINT. The program beeped, indicating the printer is bad. So, that settles it. I'm trading printers for an older one that should work with DOS (an HP Deskjet 932c), or something. -- 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
Re: [Freedos-user] UIDE Diskette Change Line Capability Tests.
Bret, A favorite tactic of propagandists, be they Fascist/Nazi/Communist or others, is that they flatly IGNORE any information from opponents and simply go on spouting their own ideas. In responding to the above thread, you have totally IGNORED all info I offered to begin with, and you cite, as your reference, a 1991 IBM Technical Reference for the PS/2. That reference is now 21 years old, and was written for a computer that AFAIK has NOT been sold by IBM for YEARS! I can also note how IBM in fact LOST control of their own PC market beginning about 1985 to vendors in Japan and Asia, due largely to the same class of FIXED thinking that you now exhibit! IBM thought they were Gods and Asia did not matter, and Asia just MASSACRED IBM in their own marketplace same as Crazy Horse did to Custer in 1876! I have NEVER given much trust to IBM, surely not after 1985, and I never will! So I will say it all again, for the cheap seats -- (A) The 1991 IBM Technical Reference for a PS/2 is 21 years old, was written for a system that is now obsolete, and MAY NOT have been kept current. (B) Using byte 0:048Fh is not undocumented. BIOS Central has noted this from at-least 2006, when I first read their BIOS data list. (C) As of 11-Jan-2007, 16 years PAST your IBM reference, Phoenix and maybe other BIOS vendors do in fact support byte 0:048Fh exactly as BIOS Central describes that byte. I have such a BIOS, and I expect others using a hardware PC can verify that 0:048Fh DOES work exactly as BIOS Central indicates, DESPITE some 21-year-old IBM reference calling that byte reserved. (D) UIDE/UIDE2 have NEVER failed, to my knowledge, to cache diskette data and deal with diskette media-changes, if used on any actual hardware PC system. If so, I want to KNOW about it and shall FIX any such problems, REAL QUICK!! (E) VirtualBox handling of diskette change-lines IS IN DOUBT! Eric did find (yesterday) a source file in which THEY DO set the byte at 0:048Fh, despite other parts of their emulator saying they do NOT support diskette change-lines. Since Their RIGHT hand may not know what their LEFT is doing! (a usual result re: too many programmers on one task!), I believe it is WRONG to say they are following the rules. WHOSE rules?? Even THEY seem not able to agree among THEMSELVES what those rules ARE!! And now, Bret, DO NOT merely spout your own propaganda again! If you have more to say, speak to the points -- SPEAK TO THE POINTS! -- that I have listed above!! And do so in private, as after this E-Mail, I will again unsubscribe from FD-User.Jack is right and everyone else is an idiot, Are you trying to prove yourself smarter than everyone else, plus other such INSULTS will be ENOUGH for me! Use UIDE/UIDE2 if you think they work. Otherwise, do not use them. Your choice. I think they work, I have evidence to say they should and NO actual PROOF to the contrary. So I will leave them as is. Jack R. Ellis -- 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
Re: [Freedos-user] UIDE Diskette Change Line Capability Tests.
Jack, Bret, VirtualBox users, A favorite tactic of propagandists, be they Fascist/Nazi/Communist or others, is that they flatly IGNORE any information from opponents At this point, you lost the discussion and many readers will simply have skipped the rest of your mail, as explained here: http://en.wikipedia.org/wiki/Godwin%27s_law#Corollaries_and_usage In responding to the above thread, you have totally IGNORED all info I offered to begin with, and you cite, as your reference, a 1991 IBM Technical Reference for the PS/2. No. The point was that BIOS Central, RBIL, Tischer and other reputable sources disagree* about 40:8f and therefore, even though each individual source is reputable, 40:8f is not a safe way to decide about floppy change lines. On the other hand, all sources do agree about int 13 for that purpose. * can mean ONE thing, ANOTHER thing, or be a RESERVED byte. (C) As of 11-Jan-2007, 16 years PAST your IBM reference, Phoenix and maybe other BIOS vendors do in fact support byte 0:048Fh exactly The weak point is in maybe other here. (D) UIDE/UIDE2 have NEVER failed, to my knowledge... on any actual hardware PC system. If so, I want to KNOW about it... Virtual machines are widespread now, their users deserve support. (E) VirtualBox handling of diskette change-lines IS IN DOUBT! The comment in orgs.asm indeed supports your claim that VirtualBox is in conflict with itself IF 40:8f really means what UIDE thinks. However, documentation about that very byte is contradictionary... Also, DOSEMU treats the same byte as reserved (0) and is backed by literature for this. As long as you can find support in literature for multiple interpretations of the same byte, it is not safe to demand from all BIOSes to interpret the byte in one specific way. Note that I was not able to download rombios.c from BIOS so all statements about me reading VirtualBox sources are limited to the BIOS-new directory and I do not know which version is used when. Use UIDE/UIDE2 if you think they work. Otherwise, do not use them. The third choice is giving my prosthetic helper a try ;-) Users of VirtualBox and UIDE, but also of other systems including real hardware, are invited to write me off-list, so I can send a copy and receive feedback :-) My tool does the following: It installs a PCI BIOS handler where scans are limited to existing bus numbers (VirtualBox has 1 bus but VirtualBox BIOS scans 256) which should speed up UIDE init a lot. This function is an experimental TSR and takes circa 400 bytes of DOS RAM. Loading into UMB with LH should be possible without problems. The other function does not take any DOS RAM: It simply enforces the expected-by-UIDE semantics for the BIOS Data Area byte 40:8f - This should protect you from data loss in VirtualBox and should enable UIDE caching of floppies in DOSEMU. Regards, Eric :-) -- 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
Re: [Freedos-user] UIDE Diskette Change Line Capability Tests.
Use UIDE/UIDE2 if you think they work. Otherwise, do not use them. The third choice is giving my prosthetic helper a try ;-) Users of VirtualBox and UIDE, but also of other systems including real hardware, are invited to write me off-list, so I can send a copy and receive feedback :-) My tool does the following: It installs a PCI BIOS handler where scans are limited to existing bus numbers (VirtualBox has 1 bus but VirtualBox BIOS scans 256) which should speed up UIDE init a lot. This function is an experimental TSR and takes circa 400 bytes of DOS RAM. Loading into UMB with LH should be possible without problems. The other function does not take any DOS RAM: It simply enforces the expected-by-UIDE semantics for the BIOS Data Area byte 40:8f - This should protect you from data loss in VirtualBox and should enable UIDE caching of floppies in DOSEMU. Out of curiosity, why not post the tool online, and share the URL on this list so people can try it? A key part of free / open source software is making our programs easily available to everyone so people can use them. -jh -- 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
[Freedos-user] SAMBA/CIFS support
Hello FreeDOS Users. I have found out that FreeDOS is a greate piece OS. However there is one thing that I am missing in it. That is SAMBA/CIFS support. What I would like to know is there anything like road map where this functionality will be provided ? Is there already anyway I can use SAMBA/CIFS with FreeDOS ? Thanks, czezz -- 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
Re: [Freedos-user] SAMBA/CIFS support
On Thu, May 24, 2012 at 6:20 PM, czezz cz...@o2.pl wrote: Hello FreeDOS Users. I have found out that FreeDOS is a greate piece OS. However there is one thing that I am missing in it. That is SAMBA/CIFS support. While I haven't used SMB under DOS, this page seems to answer your question: http://www.jacco2.dds.nl/samba/dos.html -jh -- 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
Re: [Freedos-user] SAMBA/CIFS support
Hi Jim, Czezz, That is SAMBA/CIFS support. While I haven't used SMB under DOS, this page seems to answer your question: http://www.jacco2.dds.nl/samba/dos.html The jacco2 page suggests the following: IBM LAN Client - dead link IBM DOS LAN Services - 10 diskettes and not necessarily what you want Pathworks client - license and availability unknown Artisoft / Spartacom / PCMicro LanTastic - dead product? Windows for Workgroups - no longer sold? MS Workgroup Add-On for DOS - expensive MS CLIENT - takes lots of RAM but still available, 1995: ftp://ftp.microsoft.com/BusSys/Clients/MSCLIENT/ 845+282k LAN MANager Client - less popular than MS CLIENT? ftp://ftp.microsoft.com/BusSys/Clients/LANMAN/ 4 disks! The page does not mention a modern alternative: A DOS port of Samba smbclient exists! You can use that to access SMB drives with a similar user experience as text FTP clients. It does not mount the SMB drive / share as DOS drive letter but you can look around and upload and download files etc. www.mail-archive.com/freedos-user@lists.sourceforge.net/msg07232.html You can download SMBCLIENT from http://mik.dyndns.org/dos-stuff/ only while the computer of the maintainer is on (DynDNS)... Regards, Eric -- 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
Re: [Freedos-user] SAMBA/CIFS support
Am 25.05.2012 um 01:20 schrieb czezz: Hello FreeDOS Users. I have found out that FreeDOS is a greate piece OS. However there is one thing that I am missing in it. That is SAMBA/CIFS support. What I would like to know is there anything like road map where this functionality will be provided ? Is there already anyway I can use SAMBA/CIFS with FreeDOS ? Thanks, czezz Hi Czezz, there is a tool called smbclient for FreeDOS. I explained more in this mail: http://old.nabble.com/Free-smbclient-for-DOS-td17659937.html As the server seems to be down at the moment, I provide a copy here: http://lazybrowndog.net/freedos/files/smbc3b.zip This is working like a textmode FTP client, that can access smb shared folders. It is also possible to install the old MS Client add-on, that Microsoft created for MS DOS. Read more here: http://sourceforge.net/apps/mediawiki/freedos/index.php?title=Networking_FreeDOS_-_MS_Client But don't expect too much. regards Ulrich -- 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
