Dear Bill,
I've had similar woes with multiple NIC's in DOS, IIRC that was with
Intel chips... but could be modern Realtek, I don't know...
This problem pops up on me every once in a while, but hardly ever
anymore nowadays, as I don't PXEboot into DOS very often lately.
Unless you need both the
GPT support? Do people also work on UEFI integration? ;-)
(That would be *mad*, if only for the cool factor.
Except that many DOS apps would fail to work, due to the missing
legacy BIOS services, also not sure how far the CPU real mode would
be feasible under 64bit UEFI etc. Sounds moot.)
Frank
Hello,
do you have some machine in the network, that would be able to
"share" the printer via Microsoft networking? (AKA Samba or CIFS in
the Linux parlance.)
This is a recurring topic.
LPT is originally a physical local port, a DB25 female on the PC,
against a 37pin Centronics on the printer
>
> What I don't understand is why there's an insistence on keeping the
> rate of UTC identical to TAI and inserting leap seconds. Why not just
> define the UTC second to be the advancement of Earth's 0-longitude
> line by 15 arcseconds relative to the sun (in other words, make the
> Earth's rotat
> On Tue, 12 Nov 2024 at 15:53, tsiegel--- via Freedos-user
> >
> > To solve the whole time/date problem, I never understood why they
> > don't separate the two. Time could then be a regular integer, since
> > there's only 86,400 seconds in a day.
>
Hmm. I have to give this idea some credit, in t
> String "DOS" is absent from
> https://en.wikipedia.org/wiki/Year_2038_problem. Has anything been
> done or planned to deal with it in FreeDOS, or the legacy filesystems
> it supports?
The UNIX epoch time is originally a 32bit integer in seconds, since
1.1.1970. Not defined to be signed, but of
Hello Ged,
> > I guess this should do for my daily wallpaper...
>
> Damn, that was interesting. Thank you.
>
thanks for the compliment, not sure to what extent this was deserved
:->
> Any time you feel like expanding on it please feel free to do so - not
> forgetting references, references, r
> I took the easy way out on this one. Rather than more reading and
> downloading I booted Windows on an old Dell, which when double
> clicking on it in the file manager extracted
> mb_bios_ga-970a-d3_f12.exe from mb_bios_ga-970a-d3_f12.zip then
> extracted FLASHSPI.EXE and the 4M 970AD3.F12 from
As a tiny and probably unimportant side note, I'd like to mention
that in modern notebooks, the row of F-keys tends to come configured
(via the BIOS setup) to respond to the "alternate Fn function"
primarily, without using the Fn modifier key. I.e., on such a machine
ex works, you'd need to pre
> Even I closed the laptop waiting it will recognize the external VGA.
> But nothing happened.
>
You have pretty much described the root of the problem.
The routing of video outputs is nowadays a function of the OS /
assisted by software running in the OS. Be it the Windows desktop
management, or
> Yeah after scratching my head on this one I think I will try a
> different approach to the system. The screen is USB which isn't ideal
> in DOS unless you do Windows/DOS (9x etc) but that's not FreeDOS. I
> will look at another way to get the plan working. -Ed
>
Just out of sheer pathologica
> Date sent:Sat, 5 Oct 2024 14:18:30 +0100
>
> It's a Elcon generic touch screen.
>
I've read what the others have posted.
Is it that same Elcon we're talking about?
If yes, the same Elcon:
Is this a current product, or something historical that's not on that
website anymore?
If the Elcon
> Intel GL40 graphics chip isn't quite 100% VGA, VBE 1.0, 1.1 or 2.0
> compatible in some of the graphics modes. SciTech Display Doctor
> doesn't help here either. :/
Yes the Intel VESA BIOS omits a lot of the 16-color high-res graphics
modes = 4 bits per pixel, I'd say 800x600, 1024x768, 1
> Now let's see if I can connect to my NAS .
I assume that the NAS principally serves CIFS/SMB = runs Samba.
Or that's probably what you're after.
There's a chance to connect to that using Microsoft networking.
That's the *third* flavour of DOS networking, not discussed yet:
NDIS. You should ha
> Load the “lsl.com ”driver by running the command
> Load the “e1000odi.com” driver by running the command
...
> Many folks use DHCP and mTCP on FreeDOS.
I believe that for M.Brutman's software, you need the CRYNWR "packet
driver" interface.
You have loaded two low-level elements of the driver st
DOS on "modern" PC hardware struggles with too many IRQ sources
sharing just the few legacy IRQ lines/inputs = up to IRQ 15 included.
I'd hazard a guess that your PCI LAN controller ends up sharing an
IRQ with the IDE/SATA controller.
As the PCI NIC is onboard, I suspect that you have no way of
Dear Karen,
> From my DOS desktop I am using a DOS ssh program into a Linux
> shell where I run Linux programs. My screen reader program
> processes all items on the he screen and so forth.
Oh I see now :-)
The DOS screen just displays what it gets from the SSH client
program, effectively a te
...regarding running DOS in a VM guest (emulation) and having
plausible RS232 UART emulation:
I'd hazard a guess that qemu-kvm does strive to deliver this:
https://serverfault.com/questions/872238/qemu-and-serial-ports-on-the-
guest-os
root@hv:~$ qemu-system-x86_64 -device isa-serial,help
isa-s
Regarding maintenance of Motorola radios:
I used to have a colleague in that business.
He always kept an old PC with a legacy serial port (16C550A UART)
running Windows 95 I believe. In those "pre-NT" Windows editions, DOS
apps still had direct access to hardware, DOS style.
I understand that som
>
> May I please get your best links on creating an LPT1 port to a
> networked printer via Microsoft’s net tools?
>
Note that you will need to get HW-specific drivers for your network
card for DOS. These come in maybe three different flavours:
- CRYNWR packet driver (most freeware / open-sour
what, you've strapped *journaling* on to a FAT FS ?
Never heard of anyone doing that before :-D
And that "session scoped writes" feature would be very useful in the
old days in an IT classroom at our school. People could be allowed to
bring in all sorts of junk and try any sort of abuse to the f
On 17 Aug 2024 at 7:27, Ben Collver via Freedos-user wrote:
>
> I do not like dosemu2. See the [rant] section of the following post
> for details.
>
> https://www.hardwareasylum.com/articles/retro/mystic-dosemu2/page8.aspx
>
At my rookie/hobbyist level, I frankly have no clue what level of a
co
That's pretty cool :-)
Needs much less conventional RAM compared to the MS LanMan.
Resembles iSCSI or AoE or NBD, and even has "COW snapshot like"
functionality, controlled from the client side... all of that in DOS.
Priceless :-)
The floppy emulation probably won't help in trouble cases where so
On 17 Aug 2024 at 9:36, Eric Auer via Freedos-user wrote:
>
> Hi Frank,
>
> > I kind of second that :-)
> >
> > DOSEMU has traditionally been "special".
> > Different from e.g. QEMU in that DOSEMU was a relatively thin
> > emulation layer. Not emulating what needed not be emulated.
>
> Note tha
On 17 Aug 2024 at 3:27, Eric Auer via Freedos-user wrote:
>
> Even without the effort to create a network between QEMU
> and the host Linux, have you considered using DOSEMU2? ;-)
>
> https://github.com/dosemu2/
>
> For pre-compiled binary downloads for Ubuntu,
> Fedora and OpenSuSE Linux, see t
> Use mTCP netcat to move the file to a printer on port 9100. As
> pointed out earlier, most network attached printers listen on port
> 9100 and will blindly accept whatever you send on that port. So you
> can send ASCII text, Epson FX codes, HP PCL or Postscript. Just be
> sure to use "binary m
A few assorted notes:
A couple years ago I've mapped the twisted path from DOS to Samba and
CUPS and documented some landmarks here:
http://support.fccps.cz/download/adv/frr/cups_howto/cups_howto.htm
I do not want to promise, that your average print server will provide
a Samba service for print
> Michael seems like we have the same problem. I am trying to print to a
> Epson LQ300+ through usb on an DELL inspire 1525 with native freedos
> 1.3 on it.
That's just an evolution of the ultra-classic Epson dot matrix
printers, and it speaks the ultra-classic ESC*P2 print job forma
Microsoft Network client for MS-DOS can produce a local LPT device
that gets redirected over the MS networking stuff (CIFS/SMB over
TCP/IP) to a server. Which can be Windows or Linux.
The next question is, what species of an animal your USB printer is.
Decent printers accept popular print job fo
> Are there any PCI cards that live at IO adress 378 so they are
> compatible with DOS ?
I'd argue that the devil's in "subtle detail", and forecast hard
cheese for you :-/
In order to decode the IOport window at 0x378 by a PCI card, this has
to be supported by the chipset (probably south brid
Dear Mr. Ramos,
> - Balena Etcher
> - Rufus
> - Untebootin
> - Win32DiskImager.
interestingly to me, you don't mention the trusty old `dd` ... :-)
Have you tried looking for a BIOS update?
I have, but the HP support website does not respond to the "Presario
427" search query. Maybe it would res
> I also had this problem, For some reason, the ã
> is missing from codepage 850.
If that's true, I would call this a bug in the FreeDOS EGA.CPX ...?
Just fabulating, I haven't analyzed this deeper.
Frank
___
Freedos-user mailing list
Freedos-user@li
Let me suggest the following hypothesis:
Your FreeDOS and graphical hardware is running with the HW-default
code page, known as Code Page 437.
https://en.wikipedia.org/wiki/Code_page_437
Whereas, you're trying to display text encoded in CP850.
https://en.wikipedia.org/wiki/Code_page_850
CP850, a
Here is a neat summary of the DOS PPP drivers:
http://www.oldskool.org/guides/tvdog/internet.html#I
...but, someone has already raised this question:
Do you have a "counterpart"?
I mean - a dial-in service answering with a modem and a PPP stack.
Or at least a null-modem connection to a PPP "server
Hello there Brandon,
to me the key question is - what do you expect of Qmodem?
What would you like to achieve in / by using that program?
I've never used it, but I figure it would be a "terminal emulator"
with some added candy. An analog (predecessor, really) of Putty or
Hyperterminal in Windows
Thomas in the unlikely scenario, that the driver you have gets you
nowhere, I can provide the unpacked DOS drivers I have in my archive,
for RS232-based TS controllers by 3M, ELO, GroovyTouch, PenMount, and
eGalax=TouchKit=HanTouch.
I have one more suggestion. Divide and conquer.
You may want t
COM ports at legacy ISA (-like) addresses are still available in a
plethora of "industrial"/embedded motherboards and computers in
various oddball mechanical form factors. And, quite often there are
four or even six of them. Sometimes not all are available at
coastline DB9 connectors, some may
In my archive, I have a copy of some driver package for 3M
MicroTouch. Not sure if it matches the one of yours.
The directory contains the following files:
DOSPANEL.EXE
DOSPANEL.HLP
DOSPEN.EXE
DOSTOUCH.EXE
DOSTOUCH.INI
DOSTOUCH.OVL
MCAL.OVL
MICROCAL.EXE
MICROCAL.HLP
MTCONFIG.EXE
MTSFONT.BIN
QCAL.
On 11 Jan 2024 at 22:06, Eric Auer via Freedos-user wrote:
>
> Hi Anton,
>
> > The machines are indeed physical with custom made ISA Bus controller
> > cards, built on prototype board, and only 4 were made, 2 in production
>
> That sounds exciting!
>
> > plan is to eventually replace ... with
On 8 Jan 2024 at 10:29, Michael Brutman via Freedos-user wrote:
...
>
> Obviously something that does real-time operations should not be
> burdened with a TSR. But it should also not be burdened with running
> DOS on legacy hardware either. Nobody in their right mind is running
> something sa
On 7 Jan 2024 at 21:28, Anton Gustafsson via Freedos-user wrote:
>
> Hi Roderick! I agree, in this case it is mostly to satisfy my
> supervisor's need to follow protocol. All machines in the network are
> supposed monitored (load, mem, swap etc) using a software called Zabbix
> which has the abi
Oh guys, to me the era nowadays is not so much about particular
software programs - it's about fond memories of many things blasting
off all at once.
You probably know what happened by the end of 1989 in DDR, CZ+SK and
elsewhere in the eastern bloc. E.g. our neighbors in PL had a bit of
an adv
Hi there,
nice to see that you're trying to tweak old software to fit on modern
screens... still I have a cold shower for you :-) Sorry about it.
Not sure where DOS borrowed its "terminal" / console code, whether
CP/M or UNIX... the fact is, that in the way of "support", the DOS
console lacks
43 matches
Mail list logo
