dencorso

I had made a quite botched calculation, which now I've fixed, thanks to you. It is. Yes. So, to get back to the start, people earn 1/5 and the hardware costs twice to thrice.

We also use the 40h week, which means 8h of work per day. But the minimum wage is the pay for one month of work. As one year has 52 weeks, that creates the 4.5 weeks per month magic number used here in many calculations regarding work. However, people here receive per 13 months, the 13th being paid 2/3 in Nov, then 1/3 in Dec, and being less taxed than other month's wages (for those who are taxed). People on Minimum Wage are exempt from income tax, but still have to pay 8% of their income to a compulsory state managed fund (to which the employer contributes further 12%) part of which, can be used on the event of loosing the job to get by until finding another one, and part of which fuels the National Retirement pension fund. So, by using 4.5 weeks per month, 40h per week of work and US$7.25 per hour, I'd conclude (using the Brazilian magic number for the weeks/month) that the Minimum Wage in the US is US$1305.00. And, IINM, there are just twelve payments per year in the US, so that would mean US$15660.00 per year (Which compares well with the more realistic 52.14 weeks per year,40h per week of work and US$7.25 per hour, which gives US$15120.60) . Now, with Brazilian 13 months and Sao Paulo's US$370.00 per month, we'd have US$4810.00 per year. Then the buts begin: but the Big Mac Index (by applying it, the US$4810.00 is reduced by 35% to account to the higher costs here, becoming US$3126.50), but the Gini Coefficient and but the unemployment rate (6.0% in 2011). And Brazil has about 2/3 of the US population. Those conclusions are correct. Yes, harder the average "middle class", much harder for the average "lower class", dire for the "lumpen". But, taken together, those comprise at least 95% of the population, if not more.

We do not know whether it was the MBR or the boot sector (PBR) which has changed (or both). With the pendrive inserted and recognised by Windows Explorer... Open WinHex, go to Tools, select Open Disk, scroll all the way down and, in the Physical Media section, select your pendrive (it'll be prefixed "RMn:", where n is an integer and RM stands for Removable Media). Then click OK and you'll get an hexview of it, starting at LBA 0 (or Offset 0). Then go to Edit, select Define Block, and enter 102400 at the End slot and click OK. The hexview is now highlighted. So go to Edit again, then Copy Block, then Into New File and you'll get a Save File As window. Then decide where you want to write the image (not in the pendrive itself!) and give it a name (the default is noname), say, pen200.bin and click Save. Then close WinHex, go to the folder you saved pen200.bin (it should be 1034 KiB long) in and zip or, even better, 7-zip or RAR it. That's all. Good luck!

Well, what I'll say next is far from perfect, but serves to give you a fair enough picture of it: Exchange Rate (Apr 5, 2012) US$1.00 = R$ 1.89 Minimum Wage (net) for Brazil: US$329.00 (per month); Then, there's the Big Mac Index: July 2011 and update (Jan 2012). And there is the Alternative Big Mac Purchasing Power Index (which I think wasn't updated ever since). Then, there's the Gini Coefficient: some newspapers were commemorating Brazil's (0,5304 !!!) had reached in 2010 its lowest value in 50 years (portuguese)... Some states do have higher Minimum Wages defined by State Laws, so let's take Sao Paulo State as the reference: Minimum Wage (average, net) for Sao Paulo State: US$370.00 (per month; it's defined by type of work, but varies just ±US$5,00 among them); Furthermore Sao Paulo City ranked 10th place (2011, it was 21st in 2010) in Mercer's Most Expensive Cities index.

Jaclaz' post was originally #4--there were already two replies. I recall searching the original post #3 for the "wrong" part. Mistery solved! It was a spam post, which was deleted! Thanks for the info. You do rock!

An image of DOS is saved during loading and restored on exit. So I wouldn't describe it as being "evicted" or quite as clever. Now, *that*'s news to me! A full 1088 KiB memory image? Did that continue on 9x/ME times? Whither is it saved? OK, not really "evicted", but still clever enough, IMHO.

... in the 1st world. Here in Brazil, as a rule-of-thumb, treble all the prices you see on e-Bay or amazon. And the cost-of-living is much higher than in the US/Canada, at least in the big cities, with lower wages generally. So, probably further 3-5 years will be required before it's generally affordable. And AFAIK it's even worse elsewhere.

Can you create an image of the first, say, 200 sectors of the pendrive, zip it, upload it to mediafire or qshare.com and PM me the link? If you don't have any program capable of creating such an image, the trial version of WinHex can do it (on XP SP3). If you need detailed instructions of how to acquire (or collect) the image, please do let me know. Once having such an image I can inspect it so that we can make a really surgically precise intervention to fix the pendrive without any great risk. You're not alone. I do find it confusing, too. Very, BTW. What you should have done (besides asking, of course) was: 1) Download plpbt-5.0.14.zip; 2) Extract from the folder plpbt-5.0.14 of the zip the file plpbt.img; 3) Write it to a floppy, using WinImage, NTRawrite or another such tool. 4) Boot the floppy you just created. Sorry if I misled you! You know that wasn't my intention.

The fact that it is "evicted" from DOS on shutdown just shows how cleverly written it is. It does not mean unmodified DOS was working under it all the while.

Thanks for the heads up about WinGauge, I'll try it soon. RP does have a rudimentary form of USER salvation. In its current form, RP does reduce the USER issue some. But the full-fledged version of it that remains just a wish, regretably... Highlights of this release: bugfixes, USER resource usage, Windows 7 skin, RPConfig UI. I wanna hear first adopters.

I told you to use a floppy, test it well, then report and discuss with us how to proceed, before modifying the pendrive, didn't I? Did you test first with a floppy? What results did you get? And, did you create a backup of the previous MBR, or a full "dumb" bit-by-bit image of the pendive, before modifying it? Don't do anything, before we talk about it, please. I do believe we can get it to work OK again all right.

A Suffusion of Red indeed! USERMaxHeapSize does work, but it seems, most if not all our resource issues stem just from too little a GDIMaxHeapSize, so it seems to do nothing. And thanks for reporting 8M works! I understand you've got no red light from it, right?

Whatever you do, please keep us posted. If you solve the video problem you'll be helping many other users besides yourself. Observe you can get graphics also with VBEMP (as described in the thread I pointed you to). The problem is it'll crash if you ever open a DOS box. Good luck!

It's got an Intel 910GML integrated graphics card (GMA 900). There's no good solution known for it, I'm sorry to say. What we do know is in this thread only. The Eee PC 701 uses the same chipset. Sorry I cannot help you more, and welcome to MSFN!

Well, in any case, the jump to x64 began with Win XP x64, so it's way back already (April 25, 2005, for the x86-64). And, at that time at least, the situation was precisely as Fredledingue put it: there was scarcely any other x64 software available besides the OS itself. And next to none had compatible hardware populated with enough RAM to actually see any benefit that might accrue. And the absence of 16-bit compatibility was a real downside then, easily overcome by using VMware, Bochs or VirtualPC, but not present right out of the box.

No. You'll still need the RAM Limitation Patch, which is not free, so it cannot be included in the uSP. However, in case you're going for a full reinstallation, you should contact RLoew and get the latest version of it, to which you're entitled since you've already bought it.

Well, I consider my answer qualifies for the "vague" one. So, with all due respect, where is the "wrong" answer hiding, since there are just three posts in this thread, of which one is the original question (hence not an answer), the other is my "vague" one and the last is yours, which, of course, cannot be part of the count. And mine cannot be "wrong" since it's "vague" and and just one entity, which prevents it ontologically from being both parts of "both"... I confess I'm flabbergasted.

There were no such things as service packs back then. Or updates for that matter. Sure there were! The last update pack to Win 3.1 transformed it into Win 3.11 (do not confuse with Win 4 Workgroups 3.11). It is WW0981, still available from MS, originally released Dec 31, 1993, and described more fully in this KB text: Win311. KB0032905 contains a full version history of the pre-9x/ME days. BTW, since the advent of 386-enhanced mode windows, it's not really correct to think about it as a windowing system running on top of DOS: it did in fact "possess" DOS, by patching it in-memory and replacing part of its functionality with its own VxDs, so the resulting OS was really a Windows/DOS gestalt. And that's how it worked ever since, up to (and including) Win ME. PS: I finally voted in the poll today. I used Win 3.1 for about half again a year, then applied the upgrade to Win 3.11, just as it was released, and moved on to W4W 3.11 by the end of '94, and thence to 98 FE in mid-'99. So, considering the question applies to all variants of Win 3.1 taken together, all in all it's been about 7 years. ..

Oh! Now I see it! Of course: in my mind I usually picture the MBR on top, with all other sectors below it, while you were thinking of it as one usually does with a memory map, that is, the MBR on the bottom, with all other sectors above it. Sure! Of course both representations are mental pictures, models which help one think about a concept, and both are equally valid (but confusion arises from two interlocutors using different mental pictures implicitly and taking it for granted each other is using the same model, as just happened). Sorry, I should have mused longer about it, before posting... (which unfortunately is not that unusual with me). Now, then, at least I can add a useful comment: Ghost 2003 can and will backup all the disk, including the DDO, *provided* one gives it the -ir command-line switch (it causes Ghost to create a bit-by-bit full disk image, not a simple "intelligent" partition image).

Sorry, but you've got me confused: with all due respect, what area above the MBR? The MBR is in LBA 0.

Wow, not me! I was around back then, but I'd never heard of the Software Carousel. BTW, was that a photo you took of the monitor? It wasn't a screenshot, was it? (Nahh, couldn't be...) --JorgeA Yes, it's a photo of a monitor, but not mine. Alas, I don't have Software Carousel anymore! That photo is from a review of it at InfoWorld (Jan 05, 87). Read it, by all means, Software Carousel was much more than just a DOS menu system, since it instanced and swapped all memory above itself, and would run real great on a PC-XT clone having an AboveBoard or any other form of LIM EMS. And just required PC/MS-DOS 2.00+!

Who remembers this?

Yours is a superb machine, but it has a not-so-recent BIOS, so I'd bet you're booting and running at USB 1.1 speed. If I'm right, you'd experience a noticeable acceleration by using the Plop bootmanager instead. It's quite easy to test this idea: grab a floppy and install to it the default Plop bootloader. Then boot to the floppy with the pendrive inserted, and select USB from the boot menu. The system will now boot using Plop's USB 2.0 support. If you find out everithing is faster, then I was right, and we may go ahead and modify the pendrive poot routine to use Plop automatically by default. Do try it and let me know the results.

Yes. But I think it best to always report the preferred base. It's added to my to-do list. True. For the sake of completeness, this MS document presents the Virtual Address Space Layout for the NT-Family OSes. In it, the Arena nomenclature is not used, but it in fact still applies (unless the /3G switch is used, because it changes the layout).

Thanks for the heads-up about that selectors thing, even if I don't quite know what it means. However, Tihiy didn't specifically say that setting the heap limit above 4M would cause a problem, simply that RP10 would default to 4M and that setting too high a limit may deplete selectors. How high a limit would cause problems is not specified, although we can infer that it is somewhere above 4M. Anyway, I'm still learning these old tricks and simply report my finding, that setting the limit to 8M (on two machines now) has made a noticeable improvement to stability. Joe. Well, there is a problem... While I used 16M for both GDIMaxHeapSize and USERMaxHeapSize, I had this issue, which went away when I fell back to 4096. However, since RP calls the Windows native LDT cleanup when LDT is lower than 20%, you won't normally notice that issue, except for the red light. But it's much better to avoid having the LDT cleanup routine (which Tihiy deems not that effective anyway) called more sparingly, to avoid unnecessary system processing, so 4M is the best value to use for both.