jaclaz

JFYI, not needed according to the first randomized clinical trial (2018): https://www.bmj.com/content/363/bmj.k5094 jaclaz

Likely: https://msfn.org/board/guidelines/ jaclaz

D@mn, I had just submitted it as candidate for the "2022 most senselessly prolonged thread" award. jaclaz

The grub4dos USB drivers do not run unless they are manually invoked, just for the record. The reason they were developed/added originally was essentially because there are (were) motherboards that have USB 2.0 hardware but only have BIOS support for USB 1.1, on those, starting the internal USB driver makes booting (or copying to RAM/ map --mem) much faster. Besides different (okder or newer) grub4dos versions may behave differently. The blinking cursor is (typically) an issue with some fields in the bootsector (related to CHS geometry) that are "off". It happens often that (for *some reasons*) the (more or less) crappy BIOSes assign to a device a "queer" geometry (different from the one the image or partition/volume was prepared/formatted with). This may be influenced by the size of the device (this would also nicely explain why you have reports of some devices working), and also - in some cases - by some assumptions by the bootloader/bootmanager. It is a hit and miss game, I had similar (though not the same) issues with another Thin Client several years ago, and I remember how I threw at it everything (and the contrary of it) before being able to actually boot it from physicaldrive (IDE/ATA CF card and USB stick), again only for the record: https://zeroshell.org/forums/topic/a-report-from-a-new-user/ It should be possible (though right now I have not a precise idea on how to exactly do it) to boot to the Win95 as image, configure it, then dd (using some dd port to dos or a win9x imaging program) it to a second image (essentially pulling data from the RAW drive) then boot this second image. Still you should IMHO first try to boot from the actual volume partition (not map --mem), PLoP, makebootfat, *everything* should be attempted. Can you make and post/attach a copy of your MBR and PBR? jaclaz

Yep, there is very little English documentation for it, the Author's site is not that bad via google translate, but it's not like there are many docs, the FAQ's however will be useful: https://hdd-by.translate.goog/?_x_tr_sl=ru&_x_tr_tl=en&_x_tr_hl=it https://hdd-by.translate.goog/victoria5_faq/?_x_tr_sl=ru&_x_tr_tl=en&_x_tr_hl=it https://hdd-by.translate.goog/victoria_faq/?_x_tr_sl=ru&_x_tr_tl=en&_x_tr_hl=it jaclaz

The grub4dos (recent version) have an "own" USB (2.0) driver stack. If you do not post the EXACT grub4dos menu.lst or commands you use, there is no way I can understand what you are trying to do. As well, if you post some EXACT reference to the hardware involved it may help (or it may be completely be not useful, no way to know). If you want to run the Windows 9x entirely in RAM, probably you can disable/remove the IDE drivers/detection/whatever (i.e. have essentially a virtually diskless PC). jacpaz

I did try that, first thing, of course, and there is only one (bad) archived page from 2015: https://web.archive.org/web/20150108204046/http://dlcdnet.asus.com/pub/ASUS/Audio_Card/Xonar_DX/Xonar_DX_81738_RC01_vista.zip Anyway the issue is solved. jaclaz

Hi, Polish dude , don't worry, the member that the A guy was denied quoting won't probably quit, and I hope that if he does quit it would be for other reasons. It was a simple misunderstanding, it ended up in Funny Farm , ruffled feathers seem to me to have been unruffled, everything is cool, and all in all this is the best of all possible worlds[1]. jaclaz [1] https://www.goodreads.com/quotes/150939-if-this-is-the-best-of-possible-worlds-what-then

Try (on the BIOS machine that is NOT booting) to change the disk boot order (as opposed to F12 choice). It is well possible that for *some* reasons either: the stick is not BIOS bootable or the F12 menu in your particular BIOS is not an exact equivalent of the disk order change. If the issue is the first, you can check it with grub4dos, that basically can boot a Windows (on BIOS) in three different ways; 1) chainloading the MBR (please read as "normal booting") 2) chainloading the VBR/PBR (please read as "bypassing the MBR") 3) directly chainloading the BOOTMGR (please read as "bypassing BOTH the MBR and PBR/VBR) On a "properly setup" stick grub4dos should work in all three ways above. jaclaz

To be fair, you were actually very accurate and provided a lot of details in the question. More often than not similar questions go *like*: Hey guys, I remember having got from the internet a driver for my Xonar audio card that worked so much better in Vista than the one I have now. Any ideas on where I can find that driver? jaclaz

1) post your menu.lst or however the commands you are using in grub4dos 2) try (it depends I believe on the "host" OS) to map the USB as physicaldrive: http://reboot.pro/index.php?showtopic=8581 https://www.sysprobs.com/access-physical-disk-virtualbox-desktop-virtualization-software jaclaz

The file is seemingly on driverguide: https://www.driverguide.com/driver/detail.php?driverid=1796663 jaclaz

Likely you have a number of "slow" or "weak" sectors. You need a tool like Victoria to assess the situation. IF these sectors are all concentrated in one area (or a handful of areas) of the disk, the easiest would be to exclude the affected area(s) by some clever partitioning. Only for the record, once upon a time (cannot really say if it i still done, I doubt it) "huge" multi-platter disks (think of the 500 GB disks some 15 years ago) with defects were "refurbished" (in some countries) by disabling one or more heads and resold as having a smaller capacity. jaclaz

Ok, I see. Once said that that topic is now officially a S.E.P. for me: https://en.wikipedia.org/wiki/Somebody_else's_problem I can however spend a couple of cents commenting on the general matter. Daniel_k has an history of being accurate, but you are likely wanting to read in his brief statement something that possibly is not there. TNSH (which will alas forever be known as "the Polish dude" ) seems - until actually proven wrong on the specific topic - as well reliable and accurate, but - again - it seems to me like you are nitpicking on the perceived contents of a couple of Daniel_k's and possibly Jakob99's posts. All in all it seems to me like the whole stuff is based on no actual grounds. From a little experience with similar experiments, the perception of an OS working terribly/so and so/perfectly can vary greatly depending on the expectations of the experimenter and on the actual specific uses/tests performed/whatever, and a number of local/specific factors may well influence the results. @NotHereToPlayGames Rest assured that lately many of your posts come out (in my eyes) as (without reason) slightly aggressive, mainly due to your (mis-)use of bolding, CAPITALIZATION and general tone. Only for the record actual wolf pack leaders need not this prolonged aggressive approach, and most probably they don't even exist (as Alpha male/females), they are likely only the eldest of a family: https://sciencenorway.no/ulv/wolf-packs-dont-actually-have-alpha-males-and-alpha-females-the-idea-is-based-on-a-misunderstanding/1850514 There is another word (in English it begins as well with an a) that may describe someone that is not actually Alpha, leads nothing and is senselessly aggressive, if you want we[1] can start calling you "the A guy" leaving to the reader the option to expand the initial ... https://reboot.pro/public/style_emoticons/default/jaclaz.gif jaclaz [1] by we I mean the guild of grumpy old bastards, of which I am a proud member

If I knew what the question was, I may. The original question, if any, has been lost (or I cannot find it easily) in the midst of the (senseless) bickering (and whining). Maybe if these latter behaviours could be stopped (possibly right now) the communication among members would be easier, smoother and also more productive. jaclaz

Yes and no. Meaning that surely the (crappy and mostly unneeded and generally speaking misused) CCleaner is the "trigger", but the base issue is almost surely at a lower level. As pcalvert wrote, the Windows 2000 NTFS filesystem is (not much, but IMHO "enough") different from the Windows 7 one that some types of disk access may well create havoc. Besides, even "mixing" XP with Vista in some (not-so-unusual) cases can make all logical volumes inaccessible, only for the record/FYI: A good idea (my personal advice) is to (for a production machine): 1) DO NOT allow the two OS instances to "see" each other, or if you prefer, the two OS's MUST be installed to separate partitions and the Windows 2000 partition should not be able to see the Windows 7 one, and viceversa (you can use a bootmanager like grub4dos to selectively hide at boot time the "other partition") 2) DO NOT use Disk Manager from the Windows 2000 on the disk (provided that the disk has been originally partitioned/formatted under 7) 3) DO NOT use (if possible on your setup) logical volumes (because the XP/Vista Disk Manager bug is "nasty" and it is very likely that the same exist in 2000/7) 4) If you need to exchange data between the 2000 and the 7 use a third FAT32 partition (you will be limited to 4 GB files, though) jaclaz

Good work. Only for the record, the Win386.exe patch is Rloew's one: https://msfn.org/board/topic/155954-how-do-i-stop-garbled-directory-after-exiting-win311/ https://msfn.org/board/topic/155954-how-do-i-stop-garbled-directory-after-exiting-win311/#comment-993238 jaclaz

It's not so much what they say, the issue is IMHO the implied long stern look of disapproval: https://www.marriedtothesea.com/092110/stern-look-of-disapproval.gif jaclaz

Maybe useful, maybe not: https://www.betaarchive.com/wiki/index.php/Microsoft_KB_Archive/275423 http://taris111.blogspot.com/2011/12/windows-me-ems-memory-support.html http://www.columbia.edu/~em36/wpdos/emswinme.html jaclaz

I see, so your "real" question is: I want to run WFWG (Windows 3.11) from Windows ME DOS (Dos 8.0) in 386 enhanced mode, but it doesn't work because Dos 8.0 cannot load EMM386.EXE, an the only other seemingly compatible memory manager is qemm386 which is buggy/outdated/whatever. Any way to workaround the issue? (this way you are not "limited" to "disable the built-in XMS driver") I think you are (loosely) here: http://reboot.pro/index.php?showtopic=14204 (no solution found there) Since Roytam is also an user here on MSFN, maybe he has some related news. jaclaz

I am not sure to understand the question, normally one would replace the memory manager with a "newer/better" one, *like* Umbpci.sys: https://www.mdgx.com/dos.htm#DOS https://www.mdgx.com/umb.htm but there are more and - depending on your machine and amount of RAM[1] - it may be tricky to find the "right" one and the "right" configuration for it. jaclaz [1] this "summary" thread might be useful: https://msfn.org/board/topic/118097-day-to-day-running-win-9xme-with-more-than-1-gib-ram/

I must be non-european, then (though last time I checked Italy was part of Europe ). Maybe you are expanding your regional experience to whole Europe? Using "dude" to address someone - at least in my perverted mind - is not particularly funny. Maybe I am just becoming too old, and the yutes[1] communicate differently nowadays. jaclaz [1] https://www.imdb.com/title/tt0104952/quotes/qt0404568

Small (but substantial) nitpick, the issue is not with "formatting", it is with "partitioning" (using the XP built-in disk manager, the diskpart should be able to create the needed alignment even on XP). See: https://sites.google.com/site/robertjkarp/home/windows/diskpart-to-create-aligned-volume To clear the essential separation of the two steps (partitioning+formatting), you can create the partition(s) on Vista+ and then format (please read as "apply a file sytem") under XP . jaclaz

That would be a slippery slope, next would be putting a limit to pointless/senseless ones (no more than one per week per member), another one for otiose ones, etc. jaclaz

Something you can try (hit and miss) is to clear the Registry history entries: https://msfn.org/board/topic/175838-be-careful-with-nirsoft-cleanafterme/ and given links. But from what you say it seems like the issue happens earlier, during the BIOS part of booting? jaclaz