dencorso

Of course they cannot! Long live 9x/ME! Long live XP!

Congratulations loblo and jumper for the great findings! Good call starting this thread, Flasche! Anything that breathes yet another whiff of life into 9x/ME should be stimulated and having a central thread for this is the way to go! However, this thread should be on the projects sub-forum, because a project it is! So, with all due respect, I'm moving it there. Keep on the great work, friends!

FileZilla does not support even Win XP SP3, nowadays. If you kill SMSS.EXE, then you can kill WinLogon without the 0xC000021A BSOD. Or you can let whatever (say: FileZilla) crash WinLogon and still not get the 0xC000021A BSOD. But without WinLogon you'll be restricted to the Classical Theme, because the skinning interface depends on WinLogon... Just saying.

Of course not, rest assured.

Sorry, but... with all due respect: 62 °C, instead of, say, 42 °C is a *big* inaccuracy. Now, 42 Billion degrees is not inaccurate: it's a raging absurd!!! Now, seriously, it may be an SDD not having a thermistor, being read as if it had one...

And, as far as I can tell, you've just resurrected! Your latest post, before this one, is from Aug 25, 2009!!! BTW, soporific's most recent post is from Jul 04, 2011...

Purpose: to delete all $RECYCLE.BIN (aka Recycle Bin.BIN) folders across all fixed partitions in a machine. Language: batch script Introduction: Multibooting on machines using mainly FAT filesystems can lead to the Recycle Bin.BIN issue... This is a clean-up script aiming at removing those annoying extra folders, across all the partitions marked as non-removable in a given machine. Requirements: unix classic colrm.exe (findable inside util-linux-ng-2.14.1-bin.zip) and Uwe Sieber's ListDOSDevices.exe (findable here). I call it DelBinBin.cmd and it's pretty simple, although I bet it can be made still simpler: @echo offfor /F "tokens=*" %%1 in ('listdosdevices ^| find /i "fixed" ^| colrm 3') do RD /S /Q "%%1\$Recycle.BIN" 2> nulLater addition: Yzöwl has devised an interesting alternative option for achieving the same result from XP or later, without requiring the use of any 3rd party tools: @For /f "tokens=2 delims==:" %%# In ( 'Wmic LogicalDisk Where "DriveType=3" Get DeviceID /value' ) do @RD/s/q %%#:\$Recycle.BINThanks a lot, Yzöwl. You do rock!

Stop. Here at MSFN we respect every user's OS choice, whatever that might be. If you have nothing to contribute, please don't hijack the thread just to turn it into a XP vs. 7 nonsense. Thanks.

Intel says there is no official support for XP and Haswells. I believe sooner or later we'll have a working unofficial modded .INF, but it's impossible to know when. And, yes, it's true: in fact, rewards are against MSFN's rules.

One could say MS-DOS 1.00 was white-box reverse-eng'ed from CP/M-86. I'm not saying it, because it's not easy to be positive about it at all, for one that wasn't at all involved in the development process. Anyway, there's no way of denying compatibility to CP/M was one of the main development directives. Then again, other parts, like the FAT filesystem, are clearly superior to their CP/M counterparts. It never aimed to be a CP/M clone.

The newest drivers, i.e., those that cater for Haswells, seem to have some problem installing (link). It may be just something wrong in the .INF, but I cannot be sure. For the IvyBridge, they end up installing by using a modified version of the .INF taken from previous drivers (which, however, don't support the Haswell).

No problem here either. I, too, use 7.6.7600.257 I'm on XP SP3, not 2k, though... Then again, after next Tuesday, we're all in the exact same boat.

Just to make sure I'm understanding what you're doing: you're compressing each file independently, right? Or are you making a monolithic upx containing all those files (that is, in case that is even possible). Glad to have you back, loblo!

FreeDOS. It's quite good already... but that far away in the future it'll sure be quite great! And, then again, there are things like Porteus linux, which should do fine, as well.

I run XP strctly on FAT-32 since my 1st XP SP2 install in 2005. Never had any problem.

Er... jaclaz... don't look now but... this is the 9x/ME forum... right? Now, seriously, I think it's the same one MDGx gave a link to on his XP page, isn't it? The English Wikipedia says it's able to read UDF 2.60, too... but I definitely doubt that...

Did I make you angry?!? If so I apologize.Thanks! But you've got no need to apologize, you didn't make me angry, at all. What happened is that I was surprized to realize almost half the machines in the list were there already by the end of 2008. In fact, it was from about that time that our knowledge about how to do it and the issues involved was becoming really consolidated. I do count on it!

Please do keep us posted about how it develops.

Give a careful look at the machines described in the > 1 GiB list. They cover the range you're interested in, and are known to work well with 9x/ME. Here's a glimpse of the list as it was in Jan 1st, 2009... 21 of the current 48 machines were already there!!!

Easy! You must become TrustedInstaller!

In that context, a link to the unofficial SNAP FAQ may be handy. The UniVBE entry at the English Wikipedia may be relevant, too.

With all due respect: what's in there to guess? Both loblo and I told you so as a (well) known fact. Then again, that's 97.4% of the installed (viz. 2 GiB) RAM: ain't it good enough? OK! Then go ahead and use XMSDSK to create a working 53 MiB ramdisk, which can be accessed from inside Win ME (or you can make it somewhat bigger, but then Win ME will see a little less memory available). Possible it is, but I really don't think it's worth the trouble.

Lynyrd Skynyrd - That Smell