jaclaz

Start by reading the guide: http://diddy.boot-land.net/grub4dos/Grub4dos.htm Although now more than a bit dated (more recent grub4dos 0.4.5c and 0.46a series have countless added features) it still cover the basics nicely. I see however that there is still a communication problem between us. Our conversations are becoming pretty much pointless as you (I have to presume deliberately) continue to largely ignore the information I try to share with you and attempt - at every interaction - to shift the topic at hand to something else, I won't even try to comment on these As I tried to tell you before it is YEARS that several different methods to run XP entirely in RAM exist, there is nothing to be invented or added to them: Personally I believe that using either Winvblock or Firadisk is easier and more handy than using the good ol' Euhenio's way (making use of the MS Ramdisk.sys coming from server 2003 SP1) but of course beauty is in the eye of the beholder. jaclaz

I don't know. On one side this kind of lists are a handy way yo know about existing applications, on the other a "full review" that omits benchmarks (when we are talking of tools that are - or should be - intended to speed up things) and focuses on lists of (often theoretical only) features (present or missing) is pretty much useless. Besides the 15 defraggers list (that very likely almost entirely use the same plain MS defragging API), there is another list with 42 (fortytwo) "Free Data Destruction Software Programs": https://www.lifewire.com/free-data-destruction-software-programs-2626174 with *any*, really *any* kind of tool mixed up together, good, extremely good, bad and pure crap, without any sensible evaluation of WHAT they actually do and how much time it takes to do the ONLY kind of wipe that is needed is appalling to me. There are only 3 tools among the 42 listed that do "the right thing" of using Secure Erase, and the Author perfectly knows about the differences: https://www.lifewire.com/what-is-secure-erase-2626004 still he puts all together in the same basket. I fear that by putting out too many options it will only confuse the reader. On the other hand (you may be less lucky than me ) I appreciated the image on the ad for "Hot Russian Ladies". jaclaz

Hey peeps, do we really need yet another burst of posts on this matter? And Dybia, you know how I appreciate your enthusiasm :), and believe me, I have a lot of sympathy for young people and for there eagerness to learn, their sometimes brilliant ideas, etc, but you shouldn't really make statements like "When back in 2013 I bought a new desktop" or however pose yourself as a long time professional user of any OS that was ever run in the world (unless you actually are one of those). How old were you in 2013? jaclaz

Yes and no, while 65534 (or roughly 32256 if "normal" long file names are used) is very hard to be reached normally, but as soon as you create stupidly long filenames it is relatively easy to reach it, the given reference shows how the good MS guys reached it alright in a Windows 7 "standard" install. But you are right, it depends more on the user's (wrong/absurd) habits than on sheer size of the volume, but besides the above reference I have seen more than one hard disk with thousands (really thousands) of (possibly - let's say - of dubious provenance) MP3's with the file name composed of the song title AND the singer AND the Author AND the year AND the label AND comments like "this_is_a_cool_one_must_give_a_copy_to_George_and_one_to_Franck" all put together in a directory like "Music" or "Downloaded Stuff". jaclaz

On other news, the strange case of the recommended updates that became UNrecommended (at least for some users): https://www.theregister.co.uk/2017/06/26/dotnet_4_7_not_ready_for_skype_for_business_or_exchange/ jaclaz

Why don't you cite what EXACTLY Jason Hood (Author of SHSUCDX) wrote? Ora are you talking of mkisofs (Author is Jörg Schilling)? Again, there is NO such thing as a "DOS ISO", let alone a "Windows standard ISO", most probably you misunderstood the meaning of the *whatever* you read or you took it out of context. jaclaz

The limit of 32 Gb in XP for FAT32 is "political", but people should use some "common sense" (a very UNcommon thing BTW) anyway. 64 Gb? OK. 128 Gb? OK. 256 Gb? Maybe. Anything larger, though possible, is simply not "smart", the size of FAT tables will become HUGE, the filesystem (and its drivers) are simply not adequate to that amount of data, and all in all file access will slow down noticeably. Besides the single 4Gb file size limit, FAT32 has another one (actually not that common to reach) which is the number of files in a same directory, see (seemingly off topic): http://reboot.pro/topic/19643-winsxs-hardlinked-files/?p=182961 So, if it is for testing or similar, it is fine to make huge FAT32 volumes, but one should know how it would be way "better" or "faster" to have several smaller volumes instead. jaclaz

No I am not. Rest assured that I know what I am doing. I am writing the FAT tables on a pre-wiped (all 00's) device. Actually wiping a large device (and/or checking it for bad sectors) is something that takes hours/days, and it makes no sense whatsoever to do it when formatting. Although I don't normally use such stupidly large devices, I do have a "dedicated" machine to wipe disk(s) overnight (actually using the internal ATA Safe Erase which is WAY faster than *anything* software). Wiping just the area where the partition table will reside is more than enough in any non-tinfoil-hat, non-national-security, non-mission-critical environment, which comprises probably 99% of computers and 100% (more likely 101% ) of those running DOS/Windows 9x/Me. jaclaz

Very few things lack "a" standard as ISO9660 (which is actually a standard), there is no such thing as a "DOS ISO" (as opposed to "standard Windows ISO") the whole point is that each and every extension to the ISO9660 (including the El-Torito emulation) might have been interpreted slightly different by BIOS vendors and OS programmers and by the people that wrote iso making programs. If I wanted to make a DOS bootable 98SE CD I would already know very well how to make it, in several different ways, thank you, this: makes no sense whatsoever. jaclaz

Another (small) thing that should probably be taken care of (seemingly the good MS guys do not consider it an issue), clipboard access on locked system: https://hexatomium.github.io/2017/02/15/windows10-clipboard-lockscreen/ jaclaz

Quite obviously SHDUCDX belongs to the same family as the ramdisk I already gave you a link to, SHSUFDRV: http://adoxa.altervista.org/ http://adoxa.altervista.org/shsufdrv/index.html http://adoxa.altervista.org/shsucdx/index.html What do you mean by "how do you create the CD image"? A CD image is a .iso i.e. a dd-like image of a CD, there is not any connection to the os used in making it, though of course DOS may be limited to a given "iso level" (and surely there may be issues with long names, unicode, etc.). You mean a DOS tool to make a .iso? Normally a port of mkisofs is used (but you cannot probably use it without infringing your self imposed ideological limits as it is contaminated by its Linux roots ), just in case: http://bootcd.narod.ru/index_e.htm http://bootcd.narod.ru/cdrtools-2.01-msdos-bin.zip Now, a good question could be "What is the simpler method I can use to convert a 1.44 Mb boot floppy into a bootable CD"? But the answer may be unusable (as it is contaminated by MenuetOS): http://reboot.pro/topic/9916-grub4dos-isohybrided/?p=86679 jaclaz

Hmmm. Las time I created a FAT filesystem by hand it was a matter of a few bytes (F8FFFFFF) in the right locations, starting from a cleaned (wiped) device, maybe the time RFORMAT takes is to make sure that the areas are blank and/or wipes them to be sure they don't contain "old" data. jaclaz

Sure , hence the scoop. jaclaz

The jacket vendor has however the advantage of seeing the physical credit card of the customer, which, in some cases, may contribute to better understand the customer's character, and be prepared to being questioned about (say): 1) the colour of the jacket he sold 2) how the jacket was manufactured, including, but not limited to, the quality of the leather, the choice of the sewing patterns, the specific brand of thread used (and its colour), the way it was folded and stored, the chemical composition of the plastic bag it was in, the temperature (min, max and average) and percentage of humidity of the storage warehouse for the last 10 years 3) how the jacket was advertised, the choice of furniture of the shop and the design of its lighting 4) the size and position of each and every pocket of the jacket 5) the choice of zips instead of buttons (or of buttons instead of zips) and being suggested how to better each one of these items. SCOOP! We have an image of the centurion on 98SE's Amex card: https://tinyurl.com/yc6p7a9q jaclaz

Automatic translation is very often terrible, rest assured that the adjective otiose has been chosen very carefully, hand picked among a number of possible candidates, and intentionally posted in Aldine, what you would call italic. Particularly, it was a comment aimed to Dencorso, we speak languages that share a common latin origin and as such it is often fun for us to use here and there some latin-derived words that an average native English speaker would never use (and possibly doesn't even know), even if they are correct. @dencorso https://maeperfeita.files.wordpress.com/2011/05/preguic3a7a-quino.jpg jaclaz

Well, you wouldn't want the Financial Times to use the same scale as The Economist, wouldn't you? http://www.ft.com/cms/s/2/9f128868-68b4-11da-bd30-0000779e2340.html?ft_site=falcon&desktop=true#axzz4kqyy3M5c but I believe the Mars Bar is more related to inflation or differential of buying capacity over time (but "domestic", not as comparison with other countries), just as the Freddo Index (which also is connected to the Mars Bar one): http://www.telegraph.co.uk/news/2016/07/08/this-is-how-much-a-freddo-will-cost-by-2030/ https://www.vouchercloud.com/resources/the-freddo-index While the MarS Bar is "international" the Freddo is a British only brand/name- jaclaz

Grub4dos is NOT GRUB. Rest assured that the bootloaders are the files I mentioned, whatever you call "bootloader" remains a mistery. 9x/Me and NT/2K/XP have a very different booting mechanism. All the rest of the world has made boot floppies for all these OS's, if you want a couple examples, see here: http://www.xxcopy.com/xxcopy33.htm http://www.multibooters.co.uk/floppy.html And you will need some time to read about how Firadisk and/or Winvblock work (together with grub4dos). jaclaz

Well the Big Mac Index was started out by the Economist, which last like I checked was UK based alright (since 1843): https://en.wikipedia.org/wiki/The_Economist I would venture to say that it sounds as British as something can be. jaclaz

Still what? I never talked of downloadable drivers, official or not, you managed to introduce the matter. Do we really need to debate about the availability (or non-availability) of drivers for a not-in-the-hands-of-the-OP card? When/if someone will ask for those drivers, then - maybe - they will be looked for (and hopefully found) *like* here: https://web.archive.org/web/20051001102448/http://www.hauppauge.com:80/pages/support/support_pvr250-350.html WHAT (the heck) is the problem? jaclaz

Now it is becoming interesting, grabbing some popcorn ... jaclaz

I stated: Go here: http://www.hauppauge.com/site/support/support_pvr250-350.html Click on the FAQ tab. Expand the question "What Operating Systems are supported by the WinTV-PVR-250/350?": jaclaz

To be fair you asked an otiose question http://www.fastfoodmenuprices.com/mcdonalds-prices/ Besides that, using McDonalds prices is extremely appropriate as - not so casually - they are used in the by now internationally recognized Big Mac Index: https://en.wikipedia.org/wiki/Big_Mac_Index And - within the US - the QPI: https://www.nerdwallet.com/blog/mortgages/home-search/quarter-pounder-index-most-least-expensive-cities/ the above 2013 prices (excluded Alaska and Hawaii ) show some non-trivial variation, $4.52 in Rhode Island vs. $2.24 in Arkansas is almost exactly a 2:1 ratio. jaclaz

No. Do not confuse GRUB with grub4dos. That tutorial: http://clubweb.interbaun.com/~mward/grub.html#use is a very old one and it is about GRUB. They are DIFFERENT tools, grub4dos is an evolution of the first, GRUB only has a small subset of the capabilities of grub4dos, which was named "for Dos" for some reasons... There is no "Linux Ramdisk" anywhere involved in the threads on reboot.pro you linked to. You still seem like having an obsession with "Linux". I don't know where did you find those "crazy" multi-Mb sizes. The boot manager and loader of NT up to XP (NTLDR), including the accessory files (NTDETECT.COM and BOOT.INI) is in the hundreds of Kb range, and as well the NT 6+ (BOOTMGR and \boot\BCD\) are only slightly larger. DOS/9x/Me do not have a "real" bootloader, IO.SYS is the system file that is also the bootloader. Boot floppies for all those OS can be done easily, and they are (talking of a coommon 3.5" 1.44 floppy more than half empty (for a single OS). jaclaz

That would make 007 McRib Sandwiches (with license to kill) jaclaz

The device at hand is a TV capture card, it has (including the software) a level of complexity that is higher than a "normal" network card or of an audio card, and since part of the software (besides strictly the driver) is "proprietary" it is very probable that it is "picky", even on supported OS. Anyway the TVR-H-1600 is PCI so that is not the issue at hand. http://www.hauppauge.com/site/products/data_hvr1600.html The Win-TV-USB cards do have drivers for 98: http://www.hauppauge.com/site/support/support_usb.html But more or less the PCI cards supported in Windows 9x are seemingly the 250 and 350: http://www.hauppauge.com/site/support/support_pvr250-350.html jaclaz