dencorso

Thin Lizzy - The Boys are Back in Town

It's normal for me, too. And since I have a 2 Mbit/s ADSL connection (that's nominal: 1.3 -1.5 Mbit, really), I usually sense thraffic issues earlier than most. On the other hand, any connections to Europe are slower than usual for me those last few days... I guess the problem lies in the European backbone.

Well, RASPPPoE remains available, and it's better than any ISP-provided drivers. It served me well for a long time, and still does, whenever I decide to connect bypassing my router for some reason. It's universal, configurable, and just works! Hope this solves your original problem. As for IPv6, well, tomorrow I'll worry about it... Then again, the fridge is a much more serious matter, but mine's far older than Win 95, and I'll try to keep it going as far as I can manage to!

This is just to remind you that WinImage may not be the best tool to populate a superfloppy. When I tried, it messed-up that good 36MiB blank superfloppy image, and yielded nothing useful. It sure merits further investigation, which I didn't yet do. But, be that as it may, VDM is the way to go to populate the image, because we do know for sure that VDM works. @pengo: Cross-posting (on different forums) and specially double-posting (on different threads) only irritates the very people whose help you're seeking, so it should be avoided.

Congratulations, to the two of you! That sure was a bug hard to swat! Persistence and method wins the day. You both rock!

Yes. But my crystal ball is out for sevicing once again. On such scanty info as you've provided there simply are too many possibilities for me to be able to go on. Please elaborate and I may be able to help you.

Bon Jovi - I'll Be There for You

For Win9x, you could install without ACPI (KB186111): Setup /p i Can one still do it with Win 7? Win XP has a non-ACPI hal and kernel pair so I think that might be the way to go, if one such hal and kernel is stil avilable for Win 7. bcdedit should have the equivalent of /KERNEL and /HAL boot.ini switches to allow for selecting kernel and hal. Moreover I think ACPIOption=2 in HKLM\Software\Microsoft\Windows\CurrentVersion\Detect still is avilable and works.

@Drugwash: Well, I guess it's your logical filter that makes the difference, plus a gist for formulating it clearly. Yes, but you won't like the prices... <link> Working with such beautiful vintage sound equipment has its downsides, price being the worst one, you know.

The only simple app I know that can do it is Jon Grieve's Disk Space Monitor (find it here). It sits on the tray, however, and requires one icon per logical disk, but I like it a lot. Moreover, it was created for the Classic Skin, so it has a hardcoded silver frame that I'd love to change into blue, but all my attempts to do it, up to now, didn't succeed. It also displays decimal byte multiplyers (1kB = 1000 bytes), but that's not a problem for one who just wants the graphic display.

Just for a quick reference on what MS says cannot be done to files, using .infs: Quoted from this page. @Drugwash: Your explanations are so much clearer than MS's that I cannot resist asking you to consider writing a full ".inf How to" or Tutorial. Please do consider it.

You need the free Avira NTFS4DOS.

Win XP Pro SP3 supports up to 2 physical processors, no matter how many cores they have inside, and no matter whether they do have HyperThreading or not.

For those languages for which someone started creating update packs a long time ago, like French, Italian and Polish, there are numerous localized updates available. For all others it may be already too late. Moreover, there are numerous updates that were never released in more than a handful of languages. So, IMHO, the best bet nowadays is to set up any new machine using the EN-US locale, regardless of where one is. And, BTW, welcome to MSFN!

Sorry, I think I lost myself by reading this thread too little. And many other may be feeling like I do. Are you positive the problem is caused by the bootskin code added?

Santana - Singing Winds, Crying Beasts

Dual-booting is a integral part of the NT-Family OSes design from incept time, and they always installed a boot menu component by default, to confirm it.

I had not quite grasped it was a single sided format (silly me!), but the 0xFA format is also in Thom Hogan's handbook, which relevant table I reproduced here. I think no format can be more officially recognized by MS than one which has its own Media Type Byte, so for me that's more than settled.

Wow! Does it require a DDO, or just modding the bootstrap loader and IO.SYS can get it to boot?

Proactive anxiety in not a good frame-of-mind, IMHO. Let's wait and see whether there is a problem, before setting on solving it. Or, as we say here in Brazil: "Tomorrow we'll think about it!".

Well, I guess you've got the Media Type Byte figured all right. And since fa 320 KB 1 80 8 is bona-fide, I guess it should be include, despite being super-obscure. But I still think support for non-512B sectored formats is unneeded, even if they are documented enough.

The 640K size is the 8 sectors per track version of the common 720K size, from a time drives (or media) couldn't do 9 sectors per track reliably. It was the first format standard for the 3.5" floppies. So, yes, 2 Sectors/Cluster and THEN a FAT of 2 sectors. It survived longer in Japan, but was used worldwide for a very short time. The 320K size is the 2 sided version of the old 160K size, both also from a time drives (or media) couldn't do 9 sectors per track reliably. So, yes, 2 heads and 40 tracks. It was the second format to be officially supported by PC-DOS, being introduced with v. 1.10. All later DOS versions support it natively up to V. 8.00, and I bet all Win NTs up to at least XP also do. And all DOS versions but 1.00 can boot from it. So, yes, both the above existed in the wild as FAT-12 floppies, although the 640K never made it to the list of formats supported by DOS FORMAT. Of course, v. 7.xx and 8.00 should boot OK from a 640K floppy. I think I once read a mention to a single-sided 80 track version of a 320K floppy in a post by Multibooter (yet I may be wrong), but that's the only reference I can think of for it, and it sure was never a common DOS floppy format. I'm positive this format can be dropped too. The sole single-sided formats that need support are 160K and 180K, because they are standard from very early on, which support was never dropped. I do still have a working MS-DOS 5.00 160K boot floppy I created just for fun more than 10 years ago. I've just booted from it and chkdsked it, to confirm it still works, while writing this.

Yeah, that's what I think, too. That's why I agree those 1024B sector formats should be removed from the floppy image creating spreadsheet. While they may be of historical interest, they are useless for boot floppies.

Of course. That remains undocumented (and, hence, is only knowable through RE). The official documentation never reveals more than what's deemed strictly necessary, as usual. But I thought maybe Czerno would find useful those pointers to the existing documentation of FAT-32, even if they do not contain the info he's seeking. It's unfortunate RBIL ended with v. 61, BTW... A v. 62, containing a lot of MS-DOS 7.xx - 8.00 info would be a dream come true, but I guess it'll never be more than just a dream...