Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Hard drives with 4kb sector-size are now available

Featured Replies

Has anyone tested the performance of 4K drives with aligned partitions on Win9x? Is there performance degradation?

Even if the data area is 4K aligned and uses 4K clusters, wouldn't there be degraded performance on FAT accesses (which aren't cluster-bound)?

Windows 9x implements 4KiB transfers internally whenever possible. This was done to improve performance and to reduce Memory paging issues. If the Data Clusters are at least 4KiB and aligned on physical 4KiB Sector boundaries, there will be no degradation. This alignment applies to the Data area, not the Partition itself.


Windows 9x implements 4KiB transfers internally whenever possible. This was done to improve performance and to reduce Memory paging issues. If the Data Clusters are at least 4KiB and aligned on physical 4KiB Sector boundaries, there will be no degradation. This alignment applies to the Data area, not the Partition itself.

Yep.:)

We have here the result of a test, that, though made on NT based system, may give an idea both of the procedure and of the advantages:

jaclaz

Windows 9x implements 4KiB transfers internally whenever possible. This was done to improve performance and to reduce Memory paging issues. If the Data Clusters are at least 4KiB and aligned on physical 4KiB Sector boundaries, there will be no degradation. This alignment applies to the Data area, not the Partition itself.
But what about when reading/writing cluster chains in the FAT itself?

The surest way to tell would be to benchmark it, but I don't have 4K drives, and I'll try to avoid them for now, if I can. :)

Windows 9x implements 4KiB transfers internally whenever possible. This was done to improve performance and to reduce Memory paging issues. If the Data Clusters are at least 4KiB and aligned on physical 4KiB Sector boundaries, there will be no degradation. This alignment applies to the Data area, not the Partition itself.
But what about when reading/writing cluster chains in the FAT itself?

The surest way to tell would be to benchmark it, but I don't have 4K drives, and I'll try to avoid them for now, if I can. :)

Windows 9x does the same buffering on the FAT itself so large requests will still be aligned. Most reading and writing of the FAT would be one sector at a time though, so alignment would have no significance.

That's good news. So it seems quite possible that a properly aligned partition with the right reserved area size would work well.

I don't remember now the exact structure of things, but wouldn't the cluster count need to to be set to specific values because the 2nd FAT copy would go right after the first, so may be unaligned?

That's good news. So it seems quite possible that a properly aligned partition with the right reserved area size would work well.

I don't remember now the exact structure of things, but wouldn't the cluster count need to to be set to specific values because the 2nd FAT copy would go right after the first, so may be unaligned?

Yes, if you read the already given thread:

and this one:

You may get some ideas/data/methods/tools.

jaclaz

IO.SYS needs patches to increase some buffers to handle the larger Sectors and to recognize the Sector Length field in the Boot Sector's BPB.

What is the native capability of IO.SYS, 512 bytes or 2K bytes? (The last part of that comment at least, implies 512 bytes.)

BTW, I just purchased a cheap MP3/MP4 player whose sector size (via USB) is 1KB. I'm having some difficulties with it (in all O/S, from DOS to Vista), but that may be due to the quality (or lack thereof) of its Flash, rather than its sector size. It's formatted as a "Super Floppy" (sans MBR). Anyway, that's what led me to re-read this thread.

Joe.

IO.SYS needs patches to increase some buffers to handle the larger Sectors and to recognize the Sector Length field in the Boot Sector's BPB.

What is the native capability of IO.SYS, 512 bytes or 2K bytes? (The last part of that comment at least, implies 512 bytes.)

BTW, I just purchased a cheap MP3/MP4 player whose sector size (via USB) is 1KB. I'm having some difficulties with it (in all O/S, from DOS to Vista), but that may be due to the quality (or lack thereof) of its Flash, rather than its sector size. It's formatted as a "Super Floppy" (sans MBR). Anyway, that's what led me to re-read this thread.

Joe.

As is, DOS and Windows 9x will only handle 512 Byte Sectors. I have extended DOS to 32KiB and Windows 98 and 98SE to 4KiB.

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.