I think you've suffered a minor memory leak... Win98 was a deep low point. Win98 SE, on the other hand, fixed many of the problems with the original Win98 (just as Win95 was crap, but Win95 OSR2 was usable).
But as noted by another poster, nothing in the Win9x series could measure up to OS/2 3.0 for a serious OS.
Well, LibreOffice could sure use some more work, for starters. Plus there's no decent debugger for GCC. Cristian Vlasceanu wrote ZeroBugs, which is much closer to a full-featured debugger for GCC, but then he got a day job and hasn't been able to support it very well.
Cheers
Phil Hobbs
-- Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC Optics, Electro-optics, Photonics, Analog Electronics 160 North State Road #203 Briarcliff Manor NY 10510 hobbs at electrooptical dot net http://electrooptical.net
Den onsdag den 1. oktober 2014 18.52.24 UTC+2 skrev John Larkin:
I do all my Zynq development in Ubuntu, when you work with linux not using Linux is just more trouble
Ubuntu requires no more work than windows, and all the linux tools are available with a single command, not hours of searching the net hoping there's a semi functional win32 port
-Lasse
Den onsdag den 1. oktober 2014 19.57.30 UTC+2 skrev John Larkin:
no need for massive FIFOs in the PL. The PL it has direct access to DDR via the AXI master ports
I have a display with spi interface, the PL just gets the address of the framebuffer and then handles updating the display
-Lasse
1) those are apps, not the operating system 2) if I can't/won't afford MSWord+VisualStudio+etc then it is even less usable/workable than LibreOffice :) 3) gcc worries me, based on Mike Stumps' recent postings and attitude on comp.arch
But at least with Linux I has a working, useful, usable operating system and computer with peripherals (unlike with MS+WinXP).
Besides Win8 required "so much more work" that they had to skip a version to Win10 :)
That's the only problem with my Thinkpad X230-tablet. Well, that and the low-rez screen.
Slowman needs one of those.
No, it is spot on! The same could have (and was) about OS/2, but I was willing to put up with it there. OTOH, I never had to recompile OS/2.
Den onsdag den 1. oktober 2014 21.58.33 UTC+2 skrev snipped-for-privacy@attt.bizz:
very very few people have to recompile linux
-Lasse
So what do you do with just the kernel? Bash is an app, too.
Cheers
Phil Hobbs
-- Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC Optics, Electro-optics, Photonics, Analog Electronics 160 North State Road #203 Briarcliff Manor NY 10510 hobbs at electrooptical dot net http://electrooptical.net
Until Win2K, I would agree. Since, it does "just work". At least. I don't even install it. It "just works".
So you're saying that your experience is universal? That's how I felt about Ubuntu. I just deleted it, threw away the DVD, and put the system on the shelf. I bought a dock for my laptop and never looked back.
Nonsense.
Except when it's *never*.
Because you *bought* them to work with Linux. I never got any printers or scanners working *completely* under Linux (SuSE). Under all flavors of Windows, since Win3K anyway, they "just work". the worst I've had to do is download drivers (easy).
I have it. You fiddle. Whatever floats your boat.
No, WinME was the low point. Fortunately, there was Win2K, at the same time. It was bulletproof, IME.
Agreed. They weren't OSs.
All those FPGA resources are there, so we may as well use them. We need some FIFOs for timing (gotta load the DACS at the right rate) so making the FIFOs big costs nothing.
We have ginormous waveform files stored on the SD card. The software reads those files, applies gain and offset factors, optionally sum in noise, then loads the i/q FIFOs. Loading dram, and scheduling DMAs, wouldn't be worth it here.
We may do an 8-channel waveform playback machine similar to this, and it might benefit from DMA. We could move the cals and such into FPGA hardware.
-- John Larkin Highland Technology, Inc picosecond timing precision measurement jlarkin att highlandtechnology dott com http://www.highlandtechnology.com
My software guy develops ARM code under some flavor of Linux. I don't have to deal with that; I'd rather draw schematics.
The FPGA part was done by a consultant, probably under Windows.
-- John Larkin Highland Technology, Inc picosecond timing precision measurement jlarkin att highlandtechnology dott com http://www.highlandtechnology.com
There are tutorials and app notes that (claim to) show that being done.
I'm being cautious because I haven't done it (yet) either.
The Windows kernel is even worse for real-time (hard or soft). It randomly changes (i.e diddles with) each process' priority in order to "unblock" mutually deadlocked processes. I suppose they had never heard of priority inversion and how to deal with it.
(Of course the real reason is that in a non-realtime workstation or server, fiddling priority might indeed be the best workaround)
Alright, I should have written GNU/Linux :)
Den onsdag den 1. oktober 2014 22.09.57 UTC+2 skrev John Larkin:
Once you have all your modules made Vivado is a bit like drawing schematics ;)
I compile most of my user code for the Zynq on the Zynq, no messing about cross-compiling and it is plenty fast
The xilinx tools run on both linux and Windows
-Lasse
This was XP, which was after Win2k, so what's your point?
Er, no. Whatever gives you that idea? Strawman argument.
I'm not prepared to sit twiddling my thumbs while for each of the >20 download-install-reboot cycles required to get WinXP fully updated. Instead I get on and do something more productive than installing an OS, occasionally returning to press a key to start the next cycle.
I've only had "never" with WinXP; GNU/Linux has always "just installed and worked".
Er no. What makes you think that? Strawman argument.
Good answer. Not.
To expand... My Epson scanner was purchased to work with WinXP. Now it *doesn't* work with *Windows* Now it *does* work with *GNU/Linux*.
Windows fails, GNU/Linux works.
Den onsdag den 1. oktober 2014 22.06.48 UTC+2 skrev John Larkin:
if is fast enough it is fast enough, writing single registers isn't terrible fast but I guess with FIFOs you can use longer burst
if it is things like gain and offset it is really a no brainer, it is a single line of code
-Lasse
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.