> -----Original Message----- > From: Alain M. [mailto:ala...@pobox.com] > Sent: Thursday, February 05, 2009 11:46 AM > To: freedos-user@lists.sourceforge.net > Subject: Re: [Freedos-user] dd for DOS? > > I can't refrain myself... > > David C. Kerber escreveu: > > Building it with static RAM (SRAM) instead of DRAM would > have the same effect, and SRAM is inherently much faster than > DRAM. The problem is that SRAM is much less dense and more > expensive than DRAM, so you can't fit as much in a given > machine, and it's more expensive to build. > > that is just theory. Where would you buy a SRAM to run at 1033MHz???
I don't know; I've never looked for it. It's not just theory, however; don't you remember the days of 5ns SRAM caches on motherboards, when the DRAM had access times of 60 or 70 ns? > In the same category: parlel is faster than serial. then why > is SATA faster then IDE? The issue with parallel is that the bits must be reasonably synchronized across all the data lines, which means you can't drive them all that fast in an inexpensive flat cable. If you were to build each bit's data line as a full-blown transmission line (differential drivers, controlled capacitance, etc) you could run it many times faster than it goes now, and get overall faster speed. However, that gets really expensive, and would require changes to the electronics on each end as well. So, if you're going to change the electronics anyway, it's overall cheaper to build high-quality tranceivers and serial cables that only have a few wires in it, and drive it much more than 8x faster than a parallel data cable, giving you overall faster data transmission. The other advantage is that the cables, being physically smaller, don't block as much air flow, or take as much room in a small case, giving the mfrs more packaging options for the overall system. > > D > > > > > >> -----Original Message----- > >> From: Travis Siegel [mailto:tsie...@softcon.com] > >> Sent: Wednesday, February 04, 2009 12:24 PM > >> To: freedos-user@lists.sourceforge.net > >> Subject: Re: [Freedos-user] dd for DOS? > >> > >> Now, I'm surprised they didn't carry this research a few steps > >> farther. > >> The claim is always made that if computers didn't need to refresh > >> their memory, they wold be magnitudes faster. > >> Why not build a computer (liquid helium cooled) that does exactly > >> what they tested in this experiment. > >> I.E. no need to refresh memory at all except for once an > hour or so. > >> Wouldn't that make the machine much faster. > >> Effectively it would be 0 refresh, since in 99 percent of cases, > >> nothing needs to remain in memory for an hour anyhow during normal > >> computer usage, only update the memory when it changes, > and not have > >> to worry about loosing memory continuity at all. > >> You could of course implement some sort of a sleep mode (I.E. > >> dump the contents of memory to a flash drive or nvram or > >> something) when not used at all for x minutes, this would > negate the > >> need to refresh even after an hour. > >> There's always technology researched for making machines faster by > >> running them at higher clockrates, but this would do wonders for > >> speed, as there would never need to be a single memory > refresh under > >> normal operating circumstances. > >> Of course, all this is theoretical, until someone does the > testing, > >> but it is a nice idea. (at least I thought so) > >> > >> > >> -------------------------------------------------------------- > >> ---------------- > >> Create and Deploy Rich Internet Apps outside the browser with > >> Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use > >> existing skills and code to build responsive, highly engaging > >> applications that combine the power of local resources and > data with > >> the reach of the web. Download the Adobe AIR SDK and Ajax docs to > >> start building applications today-http://p.sf.net/sfu/adobe-com > >> _______________________________________________ > >> Freedos-user mailing list > >> Freedos-user@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/freedos-user > >> > > > > > ---------------------------------------------------------------------- > > -------- Create and Deploy Rich Internet Apps outside the > browser with > > Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use > > existing skills and code to build responsive, highly engaging > > applications that combine the power of local resources and > data with > > the reach of the web. Download the Adobe AIR SDK and Ajax docs to > > start building applications today-http://p.sf.net/sfu/adobe-com > > _______________________________________________ > > Freedos-user mailing list > > Freedos-user@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freedos-user > > > > > > -------------------------------------------------------------- > ---------------- > Create and Deploy Rich Internet Apps outside the browser with > Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can > use existing skills and code to build responsive, highly > engaging applications that combine the power of local > resources and data with the reach of the web. Download the > Adobe AIR SDK and Ajax docs to start building applications > today-http://p.sf.net/sfu/adobe-com > _______________________________________________ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
