Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About 98SE

Profile Information

  • OS

Recent Profile Visitors

3,776 profile views

98SE's Achievements



  1. I was on the Q/A gaming side. They'd have to pay at least $50,000 to take that kind of offer and relocate finding a place and assimilate. Probably miss home too much so not more than a year. Sounds like they were looking for cheap labor. The VAIOs are probably my favorite brand laptops. I think I have around 2 dozen hoarded VAIOs a good number of them in my room stashed. Sadly they stopped making their laptops. I can't say much for their desktops being a custom builder but I did have one P4 VAIO that was completely fanless cooled which was pretty impressive then. I'm not sure when you were there but some stand out laptop models I own. Vaio TR series - also used in the Facebook movie - The Social Network. X505 - the James Bond thinnest lightest model ever made and completely fanless. NR-NW models seems to my favorite for XP legacy support. After this generation no more dial up modem ports and I think Firewire ports also got discontinued so no more DVCam. What is this CE? Something to do with this? https://www.cepro.com/company/sony You were into home theater setups?
  2. Just wait FranceBB, once I work out a guide for getting XP onto Coffee Lake and AMD AM4 CPUs this will boost XP to 7.00%
  3. Yes but not many would want to dig around in DOS to setup the Ramdrives. Otherwise why did Microsoft develop Windows? But as an attempt to simply the OS user interface so even kids and grandparents could use the computer instead of CLI geeks. Aside from that assuming they setup the Ramdrive in DOS preloaded in the Autoexec, if they loaded into 98SE OS and wanted to change the Ramdrive letter from a DOS assigned Z: to X: would this work while within 98SE OS or would exiting to real 98SE DOS from 98SE OS work or would a warm reboot be required after modifying the autoexec be done first? I would assume you need to do a warm reboot since the OS loading has either dirtied or locked the Ramdrives from changing drive letters or capacity. Well if you can make a hidden Ramdisk (not use a drive letter) as the Temp drive location it would be useful in that case as most people won't be digging around there. You also mentioned you had a drive letter mounter to do any switching so you could switch it to a real drive letter when needed and force another drive out. It was wishful thinking maybe you had one more Ace up the sleeve if programmed for 9X/ME. Most of the ideas I stated were to make it such but as you said they are not possible. So if the foundation of ideas can't work the subsequent ones will not matter. Not sure. I haven't checked your prices vs the current prices for others. I suppose if yours did cost $20 then a GUI version for $30 would be reasonable to me and possibly others. Or a combo package of both versions for $40 basically older CLI and newer GUI options for the user. Then the price above I think would be fair for most all things equal. What is the capacity limit of the Ramdrive for DOS and for 9X/ME? Depends on your target audience. With 9X you are restricted and need a compliant 9X/ME based graphics card and drivers. Going to real DOS most older DOS based games should work and native applications or utilities. Now if FreeDOS was used instead possibly the source code could improve DOS hardware compatibility that might open up multiple cores to be utilized. The 98SE USB advantage is allowing a USB sound device to be identified as a Sound Blaster type when used with DOSBOX. There is less work for the user to get a DOS gaming rig going on a modern system in this manner than it would be to install 98SE from scratch on a Coffee Lake system. Now if you're not a frequenter of Vogons you might not know the niche it may fill there for legacy gamers. But this is the only viable idea I have of making 98SE relevant today on newer machines so it isn't about me. Remember I have older P4s with ISA slots and have made SkyLake work with 98SE but the limitations and the steps to get it to work properly versus the 98SE DOS using 98 system files and USB 2.0 support would simplify a lot of the problems. Most standard 9X/ME applications can run properly in XP so direct 9X/ME apps really are now pointless to most consumers. However your background programming expertise is mainly in DOS and an understanding of 9X/ME so this is something I would think you'd be capable of doing rather easily. We all wish we were billionaires but then we wouldn't be working anymore. Like you said there is no free lunch so if you want food on the table you must make something that brings in the dough like your patches. Just eyeballing the 98SE tests I've done on socket 1151/AM4 motherboards the pool of people trying to get these to work on these modern systems is less than I would have suspected. Even recent attempts by others seem to have failed where I was successful and not many probably use my technique either. DOS itself is rather simplistic and easier to get working even on a Coffee Lake system. There is also no AHCI driver issue to deal with or any potential 9X/ME based conflicts that come up plaguing the system. Otherwise I'm out of any other ideas that you can sink your teeth into of value. I see no other branch to prolong 98SE's usefulness on modern systems and that's just being honest. So it comes down to a FREEDOS modification to support multicores and being able to run 98SE programs at the command line. 98SE USB detection of devices (sound and game controller) in 98SE DOS the system is running. Two other useful programs MUNT and DOSBOX that would definitely be 9X/ME programs if it could be run at the 98SE Real DOS command line would make 98SE relevant on modern systems. Otherwise I would say the death coffin is pretty much closed for 9X/ME relevance which is regrettable. I need the FAT16 for the backward compatibility of DOS programs in case it dislikes FAT32 partitions. Sounds like SSDs going forward for larger capacities would be a better solution to avoid these misalignments. The drives do take a beating and slow down reusing deleted space. Are all the USB to SATA adapters you have 4K USB Bus and 512B SATA Bus including the two USB docks you previously mentioned? What current > 2.2TB drive capacities do you have now aside from the recent 6TB 4Kn drive? Does your SATA to USB adapter allow the 6TB 4Kn drive to recognize the entire drive as one large MBR NTFS partition uncapped? You might want to see if your new 4Kn drive hooked via SATA directly can interface with XP SP1-3 and the same for USB 2.0 Port to XP SP1-3. Does both the SATA and the USB method allow booting off this 4Kn drive on the Z87? So both XP SP3 and the USB Stack handle 4KB at the FS level? Are you saying XP works with your 4Kn drive directly connected via SATA and also using your SATA to USB on the USB 2.0 ports? The IDE stack is used if using the IDE controller with IDE devices but what about a BIOS setting SATA in IDE compatibility mode, does this use the IDE stack in XP? How does this affect computers using the XP AHCI mode which SkyLake and all modern systems are now stuck on? You are talking about the IDE stack? What files are needed to be patched? This sounds like something that would affect NT/2K since they lack AHCI. So what ends up happening in 9X when using the 2K Sectors or your 4Kn drive? Well you can examine my 8TB post I updated it with the DOS MBR I extracted. I don't think anyone has actually "achieved" and hooked up a true 16TB single drive as MBR in XP just yet. Now there was this Samsung 16TB 2.5" SSD that cost a fortune that only Bill Gates' son could afford. It's doubtful the owner of something like that would hook it to XP or make the attempt to get it seen as a 16TB MBR drive but most likely GPT on Windows 10. Assuming the OS's supported 64KB wouldn't the 64KB open up higher capacities just as 4K vs 512B? I would figure it would be less of a burden when transferring TBs of data per second one day. Yes the 64KB to 4KB translation does slow it down but since it's done on the drive side the OS wouldn't care as long as the OS was happy with the 4KB blocks. There's only one way to find out and test on as many motherboards one has starting with the newest. Since I have more Intel MBs you probably won't have to do that much work weeding out just the AMD ones that work with 4Kn drives. I'll take care of the other half as soon as some cheap 2.5" 4Kn drive pops on the market to do some more testing. But for the Bootable testing even the smallest capacity drive will do down to 128GB to see how they work with older OSs. Microsoft has been notorious for leaving out exact facts that matter. I'm sure they might as well have stated somewhere DOS will not work on anything past a P4 but here I am using it still today. Must have been then. I started using 4TB as soon as they were available since most of these still supported XP via USB. And since I learned my lesson with 2.5" drives using 512 Bytes AUS I began repartitioning these 4TB drives with 64KB AUS so they perform better. I do have one 4TB 2.5" drive but the performance was real sluggish so I might have to check if this particular drive I had used 512 Bytes or 4KB which was the default. What do you mean by "fully accessible?" and which named "patches" are you referring? Currently I can see the 3TB drive fine in 98SE DOS otherwise I couldn't partition it and make it bootable.
  4. Wow that's a good deal and does your "XPerties" name have anything to do with a preference for XP? If you're using a laptop for the DJing what external sound device will use you for the inputs/output?
  5. What were you doing for Sony? I worked for Sega, Sony, MicroProse which Hasbro bought out. Anyone heard of Final Fantasy VII? Manilla? Manila as in the Philippines? Stopped by there once and it's brutal. Sounds like some sort of over the phone customer service support gig. And $500 to relocate? Did that even cover the airplane ticket?
  6. Just in case for no apparent reason except to show what my sealed Apple Snow Leopard DVD I bought years ago still unopened with the shipping package it came in directly from Apple.
  7. I never said anything about going to Pirate Bay I believe these are your own assumptions. I said there were torrents which is just a peer2peer way of getting a file. Just like someone uses FTP it's just another file transfer method. If you check the Apple Forums they probably have a "legal" torrent link somewhere if you don't want to go through the Apple Store method. There are a lot of "legal" files that are torrent files so don't mix this up and confuse this with pirate sites. Most unknown sites I wouldn't trust the content. If you see an official torrent link set up by an Apple Forum moderator I would consider downloading it that way if it's available. If this method no longer exist then yes you need a Mac or as I pointed out buying a cheap copy of an much older Snow Leopard for $20 from Apple. The newer Apple MAC OS has been free since Mavericks 2013 from what I can recall I remember it was available it to download for free off their main Apple Page then. I don't get why everyone thinks a "torrent" automatically assume = illegal/copyright infringement. Even you could make a torrent for your 9X demo programs if you wanted people to distribute the 9X demos freely. It's just a distribution platform before people began abusing it and giving it a bad reputation it now has since you automatically assume torrent mean PB. Just like FTP and HTTP can be used to download free "legal" files. https://www.mytechlogy.com/IT-blogs/4660/the-origins-of-torrents/#.Wf6iK7hbMz4 Too much negativity has been connected with PB in general I suggest you refrain from mentioning this name as I said before the best way for you is to get an official retail Snow Leopard MAC OS DVD install disc through the Apple Store. Since you never downloaded MAC OS Mavericks for free off the Apple site when it was available you have to go a round about way to login to the Apple store on a MAC as that was 4 years ago. I already previously gave you the official Apple purchase link here it is again. https://www.apple.com/shop/product/MC573Z/A/mac-os-x-106-snow-leopard $20 Once Snow Leopard is installed and working then you create a free Apple Account and login to the Apple Store where you can download the latest MAC OS update for free. You can keep updating to the newest version for free since Apple has made MAC OS free for quite a few years now since Maverick but you apparently missed the earlier boat. Latest version info: https://www.apple.com/newsroom/2017/09/macos-high-sierra-now-available-as-a-free-update/ Older version info: https://www.apple.com/newsroom/2016/09/macos-sierra-now-available-as-a-free-update/ 2013 version info: https://www.apple.com/newsroom/2013/10/23OS-X-Mavericks-Available-Today-Free-from-the-Mac-App-Store/ https://www.apple.com/shop/product/MC573Z/A/mac-os-x-106-snow-leopard $20 If the Apple store Snow Leopard Retail DVD won't install on your system then maybe buy a cheap used Apple laptop on eBay that meets the OS minimum system requirement. https://support.apple.com/en-us/HT201475 Then you can go directly to the Mac App Store with it and download the latest free Apple MAC OS update. No confusion as I know you were looking at "internal" drives. I would go for the laptop 2.5" because you can use a SATA to USB adapter to power it up (no power brick adapter) and lower heat dissipation. And laptop drives can be used internally so what you are looking for are actually internal 4Kn 3.5" SATA drives. These 3.5" drives get so hot I keep them connected bare outside of the chassis. I usually run a bunch of tests directly to find out if XP can see it. 3.5" drives are more limited in what methods you can hook up while 2.5" size drives you could test standard USB adapters to see what happens which is what I would try out. If I see a 4KB Native 2.5" drive pop up very cheap I might test one out and run them myself. I'm sure you'll find out through testing. Are you talking about the logical sector size the USB would appear to the OS? There is no confusion the Hard Drive will be 28X TB but the Windows limit states 256TB so if MS meant 28X then according to you they should have used 256TiB or state in full the exact bytes for accuracy and avoid any confusion. I only went with the hard drive manufacturer capacity in decimal but Windows does not declare in Bytes for exactness when they stated 256TB. Microsoft may have decided to drop the binary prefix altogether and assume the values themselves are now Binary rather than Decimal but using the conventional Decimal name. So a KB to them is 1024 Bytes instead of 1000 Bytes. This might cause more confusion so they may need to use the older 28X TB value if they want to make you happy since they didn't use 256TiB but 256TB. The 256TB probably also looked better over 28XTB. People tend to like these binary looking numbers: 1,2,4,8,16,32,64,128,256,512,1024... But for a user the 28X TB actual limit is a benefit as a 25TB loss would have been painful. However the Hard drive manufacturer wanted the larger decimal number for advertising/marketing so if they were sell specific 256TB drives that would actually be hurting us in this case. They would most likely skip above 28X TB to 300TB so using one of these drives you would have to separate the extra 19TB of space. If they followed the GB capacity upgrade path it would be a 320TB drive instead making a 256TB drive most likely max you'd consider buying to keep with the older NTFS compatibility on one partition. In the past they used 137.4 GB / 128GB Binary https://support.wdc.com/knowledgebase/answer.aspx?ID=936 Hard drive manufacturers use the TB but based it off of decimal version of 1KB = 1000 Bytes. In my calculations 18.0TB would be about the correct MAX limit hard drive that could use as much of its space for MBR. You will not find a 2.2TB drive nor will you find a 17.6TB drive and highly unlikely a 17.0GB drive will pop up so the the 18.0TB drive will be as close a drive capacity that will max it out. Hard drive companies will most likely make a 14GB, 16GB, 18.0TB drive, and a 20.0TB drive. If you want to avoid confusion using the binary form you fully adopted then I suggest you go with the full length binary name rather than the abbreviated form which adds to the confusion more than it helps. Spelling it out entirely MeBiBytes or TeBiBytes would be more clear and allow people to make sense of what you are talking about if they needed to look it up. Most people if you asked them in person how many GiBs or TiBs they have will look at you funny. Now if you wrote MiBs some might think you were talking about Men In Black. Now if you say how may Gigs or Ters is your drive they might get your meaning. But the war of decimal vs binary went to battle in the court system and who won? https://web.archive.org/web/20071016171124/http://wdc.com/settlement/docs/complaint.htm From this chart it looks like they officialized the binary terminology in 2000 but YottaByte was already in use in 1991. They missed the boat by 9 years which didn't help and Giga and Tera prefixes were already adopted 40 years earlier so I find it unlikely an easy transition any time soon. https://blog.codinghorror.com/gigabyte-decimal-vs-binary/ I'm basing if off the 18TB x 16 drives to reach the limit. I don't think they will skip 12.0GB right to 20GB. I see a 2GB increase in capacity leap increment happening. Your 281TB or my 288TB overestimate is the Hard Drive manufacturer's version of actual HD decimal capacity since they would use the decimal bytes instead of binary bytes. Examining the conversion 17.592TB = 16 TiB approximately. A true 256TiB hard drive = 281.47497671066 TB approximately. 256TB is the Windows NTFS stated limit as I explained before so if they really meant 256TiB they didn't declare it in binary form or spell it out in bytes for no possible confusion so I found what might be the exact NTFS Bytes limit. 281,474,976,654,120 Bytes using 65536 Bytes cluster size https://blogs.technet.microsoft.com/askcore/2010/02/18/understanding-the-2-tb-limit-in-windows-storage/ Even something written with an exponent would be clearer. But I didn't start the capacity terminology but stuck to what was maintained in the early 80s when PCs became popular and mainstream and has been sustained even till today as being more dominant. Whether you or someone in the past could have brought up the 1000 Bytes vs 1024 Bytes 2.4% differential argument for major adoption could or would they have won and made everyone change the naming scheme before it was too late is uncertain. I think because these base 10 prefixes were pretty common maybe this is the reason why we are where we are now stuck with it. I still have my binary byte memory counts memorized seeing it so much back in the day but I would never think 1000 = 1KB when discussing computers. So I'm not a hater of binary but most people like decimal form because it's more relatable. But trying to convert everyone or even 95%+ that already have been using an existing standard to use another with much lower acceptance except some geek heads would be like making everyone here that speaks English speak French overnight. There's going to be a lot of resentment and a lack of adoption even if it is considered more accurate and even kilometers would seem more precise than miles. Curiously I wonder how Americans would take converting speed limit signs from MPH to KPH all over the US all of a sudden even though the US borders Canada it still hasn't happened. I think it would cause a lot of chaos. The 5 1/4" 360KB disk had 362,496 Bytes from my memory. This converts to a 354KiB Floppy Disk. So even the 360KB disk could have been called the 362KB disk or the 354KB disk but certainly 360KB probably sounded the best. The 360 Degrees in a circle probably helped. If we went all binary in the past I guess a 1.44MB floppy disk is now downgraded to a 1.416 MiB Floppy Disk. Neither 354 KiB or 1.416 or 1.41 MiB Floppy would seem flattering to say today. I agree I'm not the only one but the standard that existed and I followed and even during 1980-2000 there was no perceivable resistance or adoption of the binary standard. Following a new standard ultimately adds to the confusion. I'm sure partly can be blamed on Hard drive manufacturers and the original Floppy drives started the same pattern of non binary labeling of capacities. One positive thing that may resolve this issue is after YottaBytes there hasn't been an official set name for beyond that capacity although some favorable possibilities only. This might be a good time to switch from YB to a newer Binary name that can be finally be agreed upon by the computer industry and adding the extra XBB to designate Binary Bytes to force the new standard which would be more convenient to adopt over the former. When YottaBytes is reached it becomes significant enough a figure of 20%+ difference with YoBiByte that it will probably happen some time around then. https://www.ramicomer.com/en/blog/conversion-and-difference-kilobyte-to-kibibyte-megabyte-to-mebibyte/ The TeraByte vs TeBiByte difference was 10% so that would have been a better stage to transition more easily but that time is gone. Something like 1.2 YottaByte = 1.0 XBB where the conversion is mathematically easy to translate and just continue on this Binary standard. Then there will be a YB to XBB crossover usage similar to how KB and MB were used so often. Eventually people will be using large XBB drives like we use TB drives today and the older Bytes usage will probably be forgotten since they are so tiny no one even uses or cares anymore except some relic programmers. How large can the Sectors for NTFS be increased? But according to this Intel says GPT was supported on Vista 32-Bit. Are you saying it requires a 64-Bit CPU to run this 32-Bit OS with GPT? I actually ran Vista 32-Bit on an old Pentium-M laptop. http://download.intel.com/support/motherboards/server/sb/gpt_white_paper_1_1.pdf Unfortunate news that NT/2K/XP won't work with GPT external drives. We'll see how long MBR will survive. Perhaps I will end up transitioning to GPT at 32TB+. The current memory limitations on XP 32-Bit might be overwhelmed for every day "future internet" usage requiring a jump to XP Pro 64-Bit or later and I'm open to that possibility if I've exhausted all other methods. When the time comes 18TB might be within reach in 5 years or less and depending on the prices of drives as storage capacity increases and their monetary values continue to plummet. This probably would make eXFAT a better candidate for XP and already in existence since 2006 making it a better workaround if exFAT could support > than the current NTFS 256 TBB / 281 TB limit. You mean your 11.444 MiB / Mebibyte hard disk drive. The first hard drive I used was a 5MB Seagate ST-506 MFM full height 5.25" so it occupied one large rectangle slot so that left the other slot for a large full height 5.25" floppy drive or later dual half height 5.25" 360 drives when the technology improved. I still remember the red blinking light on those some drives also used green. I kind of miss seeing those drives blinking on their own. Later was a ST-412 10MB MFM also a full height hog. There were ways to cheat and get 50% more space with RLL controllers. Since these hard drives really got filled up fast copying floppies to them their only redeeming quality was not needing to fiddle with floppy disks to boot DOS and a faster boot time. The loud obnoxious noise and a tendency to get bad sectors or fail completely were its downfall. Some nice PCs could interface with the controller and it would show the hard drive and floppy drive info on the front display panel. It made computers more interesting then.
  8. I'm the picky one? LOL. This is the computer standard I grew up with in the USA and especially during the golden age of computers. Unless in your country they started labeling everything in Kilo Binary Bytes from the start? Did all your hard drive manufacturer boxes show 120GiB, 100GiB, 80GiB, 60GiB, 40GiB, 20GiB? or did they show 120GB, 100GB, 80GB, 60GB, 40GB, 20GB like in the USA? Yes in the USA this is known as the 128 GB / 137.4 GB barrier. The so called Kilo Binary Bytes naming never took off in the USA that you prefer however this may be different in your country and you are claiming your country always used the KiB, MiB, GiB, TiB unit naming scheme on all their products? In the USA it is more well known as the 128GB barrier and as far hard drives there is and has never been a 137.4 GB or a 140GB hard drive to fully capitalize on it. This would have given someone roughly 9GB more of usable space which is about 14% then so quite a boost. There were only three capacities that came close to this barrier before and after. 120GB, 128GB (usually SSDs) and 160GB. Now I would never tell someone at the time to get a 160GB drive to max out the so called 137.4GB barrier. Sticking to 120/128GB was the smarter thing to do. Stressing the 137.4GB may cause people to take a risk and go for the 160GB drive. Unless you've ever lost 40GB or more of significant data you probably won't understand my point. Please stop making wild accusations about what I said. Just to be clear I never said you couldn't access the MBR off a regular USB device as you know I can make these bootable to 98SE so it's obvious in this case that is false. I said because this one used a special SATA to USB adapter not a regular SATA to USB adapter and I didn't want to risk damaging 8TB of DATA and I couldn't shut down the machine since I do work on it I would try to find a DOS based MBR program to access it directly connected to the SATA port. Now maybe this came out to you as a "conclusive" no way to access the MBR via a regular SATA to USB adapter. You do know there is a difference between how the data is interpreted using the special SATA to USA adapter and a regular SATA to USB adapter when it comes to these > 2.2TB drives? The Windows program I had tried to access the MBR which you were not familiar nor did you volunteer any DOS based equivalent MBR extracting programs in a typical jaclaz manner or show any interest I went and tried using a Windows program I found myself that supposedly claimed to be able to do it and as a first attempt at trying to get some data going on the topic even though there was never any indication my data gathering was fully done and even I would call it still not "complete". My preliminary work since it is a work in progress and thus the Partition Boot Record or Volume Boot Record was only accessible at the time by default in the way the program was set up for examining the first sector and you neglected to understand the 14 byte width was the default setup on my system so using a new program I cannot predict how the information would be extracted in the same manner instead of the standard 16 byte width. Since there were several options to extract all code and pop it out without any spaces or try to retain the structure of it with the addresses which I felt would be more digestible for people. So it's obvious someone who has done it before would have recognized what they were seeing which is the goal. So any incorrect information could be correctly updated. Now unlike you the only time I really examined the MBR was on the early 8088 way before your first 486 machine that you used. I mainly studied copy protected NON-DOS bootable floppy disks probably something you weren't interested in because I got a ton of these unique MBR snowflakes. Hard disk MBRs didn't interest me at all and this was during the MFM days of FAT not NTFS. Also I didn't see any need to waste time looking at the MBR of my hard drive then. All you had pretty much to use was IBM PC-DOS and MS-DOS. There was not a multiple OS installation then and DOS was all most people used. Now I could go on about the other NON IBM based computers I have but that probably doesn't interest you. But if it does which ones do you have? In general no one needs to waste time examining regular MBRs to get their systems running. No problem getting DOS->W10 working on all my systems and no need to study the MBR in detail. As long as you can image your boot partition to recover it when something goes awry that's all the necessary info you need. It's like someone who drives a car and knows what tires to buy. Studying the MBR would be someone who cares about looking at the tire treads for what kind of wear it accumulated over time. No one cares. They just care their tires are fine and the car drives and continue with their life. In your case since you tend to dabble more on the Linux side this became more of a necessity which is the mother of invention. However on my side it doesn't add to the experience since Microsoft took care of such headaches quite nicely so no real fiddling is required of the MBR as long as you have the right tools to restore your boot partition or OS image which takes much less time to get back up and running. I would say your other claim about everyone knowing how to boot a full XP SP3 off USB in SkyLake also is a bit ridiculous. If 99.99% knew how to do this on their modern system today you'd see a surge of XP OS browser usage maybe close to 25%. https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0 You also forget I didn't shift from FAT32 to NTFS till probably late 2012-13 when large HD videos became too burdensome when exceeding over thirty minutes in recording length since the file sizes would run into the 4GB limit quite easily. Mainly used to store HD videos and not bootable drives. There is really only one purpose of this Drive Discussion I opened here and it's to find a way to either replicate the special SATA to USB connector so it uses regular USB power rather than a brick. If this was a standard regular < 2.2TB drive or a GPT drive there would absolutely be no interest to me to gather the info. However since this is still in the data gathering phase nothing is set in stone yet so any incorrect data can be fixed if spotted. Any information gathering I am doing is for the MSFN community not for you alone. I know you admittedly stated to me that the largest drive you have is only 500GB which seems a bit outdated so you may have a bias towards larger capacity drives of 8TB and up. You don't specify what computer have so I have guess it's probably a socket 1366 era or at best Ivy Bridge but with 500GB as the largest drive it's questionable. Now I don't know if you just can't afford larger capacities or simply don't need to upgrade your system as you are not taxing it much with what you use it for. So if you have no interest in the actual data gathering I'm doing or getting larger capacity drives working in 2K/XP I don't see why you even care about arguing with me here. But if you do have a positive interest your mannerisms do not invoke it. Now given IF maybe you do have actual interest and since you seem to think you know it all and are into puzzles and profess to be an expert on things concerning MBR then you should be able to correctly answer these questions without faltering. Setup 1: Can the 3TB hard drive be accessed and then made bootable to 98SE DOS using this special SATA to USB adapter attached to the USB port (not a regular SATA to USB) adapter during computer BIOS boot up set for USB bootable device priority? Setup 2: When the 3TB hard drive is directly connected to the SATA controller and under 98SE DOS using FDISK to partition the Primary Partition as FAT16 2047MB then an Extended Partition as FAT32 size of 14311 MB with the Logical drives to fully use up the space made in this Extended Partition as (4GB, 4GB, 4GB, 2GB) Formatting all 5 Partitions in 98SE DOS and Partition 1 made bootable and active. Now... using the special SATA to USB adapter (not a regular SATA to USB adapter) to hook up the 3TB hard drive to the USB port. Under Windows XP's Disk Management the exact total capacity for the drive will be 2794.51GB. You should be able to answer the following. What will the break down of the partition sizes be shown in XP Disk Management? In XP can these partitions be accessed correctly as it was created under 98SE DOS? What will be the size of the "Unallocated" partition space be in XP Disk Management?
  9. Calm down my digital mucker friend... Patience... It takes awhile to get all the data collected in my spare time. Got about 3 systems I will have to build after the 3TB testing so I can move stuff onto it and free up some spare boot drives which could allow me to do more testing without shutting down my main system. First you didn't care when asked the DOS MBR tools to use and now you seem to have an interest...? The 16 Byte View was condensed by default probably because the program was expecting a larger video resolution which caused the initial truncation effect. But since it's just numbers/letters this shouldn't affect you copying it as the data wasn't altered just how it was presented. There is another output where it spits it all out without any spaces if that interests you more and can be loaded into a MBR analyzer. I found a DOS method to "properly" and "safely" extract a copy of the MBR a week ago. I've been busy gathering all the different capacity drives I have and analyzing them to see any differences. Though the program I used does have a feature to extract the MBR but it has a somewhat hidden way to get it and since you never used my program then you would not have a clue. I might test your Tiny-Hexer for MBR extracting as well. Although I've seen some better sites relating to the real "StarMan" (1984) and MBR research. Yours didn't have what I was looking for at first glance and some other MBR sites did but will check it out StarMan again in more detail if necessary to accomplish a future goal. However I did spot an erroneous statement. It may not look like much but this is the template that makes DOS -> Windows 10 Bootable off a small partition. At least you recognized some of the characteristics but I thought you also could gleen the possible OS info. For your analysis you probably would want to use 2 GiB for 2 GiBiBytes since you like that binary form and 32 KB. The large B is for Bytes, the small b is for Bits. 32Kb would imply 32 Kilobits not Kilobytes. So be careful and don't get sloppy there as you've been pretty concise. http://www.overclockers.com/forums/showthread.php/262320-Dont-get-confused-KB-vs-kb http://www.wu.ece.ufl.edu/links/dataRate/DataMeasurementChart.html
  10. I'm talking about 9X GUI support like other commercial Ramdrives like those in XP. Customizeable drive letter choosing, setting Ramdrive size, and the ability for multiple Ramdrives up to 24 or 23 meaning if C: is taken by your hard drive then D: to Z: can be assigned to use the available > 4GB+ RAM in what manner they see fit. Rebooting the system will retain the saved settings. If a user chose to they could have D: to Z: as Ramdrive drives of different capacities as long as it doesn't exceed the available RAM. Now if you could also create hidden Ramdrives that don't use Drive Letters or extend the Drive Letters beyond Z: C2, D2, ... Z2 pattern so drive letter consumption won't be a limitation. It's not about how much extra but how good the interface and features it has so people want it. If your 9X Ramdrive with a true 9X interface was created on par with an XP Ramdrive then a similar pricing to what other XP Commercial Ramdrive exceptional software would be priced if the feature set is identical. Now if there are certain memory limits for 9X where the Ramdrive size is capped then yes you can't charge the same but less assuming you could do 2TB Ramdrive in XP but your 9X version was capped at much less due to an OS limit that can't be broken. Now if you were really serious about doing it I could probably help guide the user interface design and look of it to where I would call it exceptional. The Networking Interface doesn't need to be implemented as DOS browsing isn't critical. Just getting the 98SE USB interface working on 98SE DOS. I would say the USB Audio and maybe the USB game controller are really the ones that need to get targeted. You assume this is about me and I am a Multi millionaire or Billionaire like Gates. I'm just giving you ideas on what real 9X users would possibly pay for especially those interested in using 9X DOS for legacy DOS gaming without dealing with the headaches / limits of 9X on post ISA slot modern hardware. A real 6 figure project would be a DOS->W10 32/64 Bit OS all in one fully software compatible. Boot Partition 2GB is fine. OS Partition 16GB for 98SE would be plenty. You create another dedicated partition much larger for Program Files and Document/Data storage. There is no need to constantly bloat your OS partition and 16GB would probably be way more than enough for the main OS files as long as you separate the Program files and other files that can be redirected to another partition which allow it. True. About a week or so ago I found a suitable MBR reader for my data gathering tests. I had a much older one in the early 80s for Floppy and MFM Hard Drives I used to use but I believe that one stopped working properly way before IDE drives or some newer DOS version it was incompatible with somehow. I think I was using it on DOS 1.1 and 2.0 at the time. The last time I really examined the MBR out of curiosity. It was more about analyzing copy protected NON DOS boot disks. I was talking about 64KB Physical Sectors on the platter side storage with a direct SATA connector that interfaces as 64KB Logical sectors to the OS. So no conversion would take place. Now adding on top of that the 64KB Cluster size or AUS it will just be icing and of course improve performance. You might be more specific here. The "Adapter" are you talking about the "SATA to USB"? Which side is the 4KB and which side is the 512 Bytes. From what I can tell the Bare drive in the USB enclosure is a 4KB platter storage drive but converts to 512 Bytes on the SATA connector end. These are the two typical scenarios to hook it up: Hard drive platter 4KB Physical - HD circuit board to SATA connector - Logical 512 Bytes - SATA Cable - Sata Controller - OS Hard drive platter 4KB Physical - HD circuit board to SATA connector - Logical 512 Bytes - SATA to USB Adapter - USB Cable - USB Port - OS Logical Sectors would be 512 Bytes at the XP OS Interface? Now you say larger Logical Sectors at the OS interface so how large Logical Sectors can XP SP1 handle? Non modification of the OS and using true hardware is the objective of increasing the MBR capacity so it works on any system without modification. Using a DDO or emulator adds another level of patching similar to just why not switch to GPT entirely if you're going that route. There's a reason why using 18.0TB on XP via a USB cable is an advantage without any kind of OS modification. Nothing needs to be done on the destination system at all. As long as they are running XP SP1 or higher OS this drive can be automatically detected. Now whatever they did in the actual SATA to USB adapter if they could incorporate that into the Hard drive circuit board then you could access the total capacity of the drive natively on the SATA controller or using a "regular" SATA to USB adapter. I'm not certain why they chose to not do that and used a special adapter method. This should include 2K and XP 32-Bit? What do you mean here by limited to 4K? Now here you are saying XP can understand 4KB Sector size and a regular 4KB native SATA drive will work with XP without any adapter? The adapter boards already breaks the 2.2TB MBR standard limit. So I would not say 18.0TB MBR max on XP is something to laugh at. Rewriting the File Systems probably won't happen unless the technology is present first which is my point. If 64KB drives were made as the first jump from 512 Byte drives then i would say yes Windows 8 probably would have supported 64KB now just like it currently supports 4KB drives. https://support.microsoft.com/en-us/help/2510009/microsoft-support-policy-for-4k-sector-hard-drives-in-windows The reason 4KB drives aren't supported on XP is because they didn't get these 4KB Native drives out fast enough to consumers so MS would have been forced to created an OS patch just like SP1 was created for the 128GB issue. If MS and the hard drive manufacturers all agreed to 64KB drives and they released it today trust me there will be a patch coming from MS for Windows 10 for sure since it's still new. Possibly W7 and W8.X would get a back port since W7 is still quite dominant an OS today. If 64KB drives won't be out till 2030 of course it won't happen till way past 2030. And it looks like you recently acquired a 4KB Native drive so this drive should work fine on Windows 8 without any special patching. Sure I have. I have done both the 4TB and the 8TB drives as I've partitioned and formatted it as one large MBR NTFS partition chunk. I also did some testing last week and the 3TB drive is bootable to 98SE DOS directly connected to the SATA controller. Though not many will try this ever.
  11. The unit reminds me of a toaster. The way two drives are vertically inserted worries me if it were to tip over. Try 3TB and larger with XP 32-Bit to see if translates and allows the entire drive as MBR. These are probably the drives that have a soldered USB connection from the looks of the shell. You won't be able to use these internally. The Seagate external drives seem to be the only ones I've seen that still can be extracted with the SATA connectors intact. A MAC isn't required. Sandy Bridge and Ivy Bridge have done it. You can get Snow Leopard for cheap and get the Hackintosh working. Then login to the Mac Store to download the newer versions for free or if you know someone with a MAC they can download it to a flash drive. Like I said many have made a USB method to simplify the install process. https://www.apple.com/shop/product/MC573Z/A/mac-os-x-106-snow-leopard I'm sure they would have 2TB 2.5" drives. These will be USB powered making them portable. 4KB Native drives currently have no USB adapters that I've seen that work with XP. The drive inside the XP compatible USB enclosures use a 4KB Physical -> 512e model. Indirectly 2.5" drives also work with the adapter taking up less space. Looks like I confused what he wrote but it's also irrelevant now until further tests. I examined the 3TB drive hooked up directly to the SATA controller and the Sector Size is indeed 512 Bytes. Identified as BIOS Drive (Int13x 81h) DOS only sees 782.7GB capacity. Cylinders: 364801 Heads: 255 Sectors: 63 Sector Size: 512 Bytes Total Sectors: 1565565872 No offense but there is no naming confusion. I choose or refuse to use the computer naming standard of Kilo Binary Bytes. Also as a purist I would never call a 360KB floppy drive a 360 KiBiByte floppy drive. 360 KiB looks lame. They should have just kept all the Prefixes the same and made it KBB, MBB, GBB, TBB, PBB, EBB, ZBB which would have been accepted more easily as all you are indicating is the extra B is for "Binary". You're welcome to try and spread the ISO/IEC 80000 standard but I think it's liberal "PC" gone amok. The original already existing standards sound better, but adding an extra letter adds 50% more waste going from 2 to 3 bytes. If they were going to use that then just spell out the prefix or go with the extra B. Ask anyone which they would rather pronounce, learn, and use? KILO byte or KiBiByte? You were born saying Kilo. Kibi? What is this the Keebler elve? MEGA Byte or Mebi Byte? Mega Millions or Mebi Millions? Mega wins. GIGA Byte or GiBi Byte? GIGA wins. No contest. TERA Byte or TeBi Byte? Who doesn't love Tera or closely resembling Terra like Earth? PETA Byte or PeBi Byte? Toss up. PETA stands for you know what so pro pets I'm game. But Pebi? Sounds tiny like a pebble. EXA Byte or ExBi Byte? Exa looks and sounds better. ZeTTa Byte or ZeBi Byte? Zetta definitely. YoTTa Byte or YoBi Byte? --- this one is toss up as Yobi doesn't sound that bad although Yotta Byte sounds like Ya Outta Bite. And are you going to get the United States to change from Miles to Kilometers next? Anyone using computers since the 1970s knows what a Bit, Nibble, and Byte is and that 1KB = 1024 Bytes and there is no confusion. Hard disk manufacturers aren't going to switch and neither are the newest graphics cards. Any software program I see using it I junk it since it breaks the standard. I still stand by my 256TB standard or TeraByte standard. Even wiki and Microsoft do as well. https://en.wikipedia.org/wiki/NTFS Microsoft Most Valuable Professional Microsoft Most Valuable Professional (MVP) award is given to "technology experts who passionately share their knowledge with the community."[1] The awarded are people who "actively share their ... technical expertise with the different technology communities related directly or indirectly to Microsoft". An MVP is awarded for contributions over the previous year. Windows File System Troubleshooting 1st Edition, Kindle Edition, Publication Date: June 26, 2015 https://www.amazon.com/Windows-File-System-Troubleshooting-Halsey-ebook/dp/B00UBYYY34/ref=sr_1_1?s=books&ie=UTF8&qid=1509174353&sr=1-1&keywords=9781484210161 Page 22: https://books.google.com/books?id=ylQwCgAAQBAJ&pg=PA22&lpg=PA22&focus=viewport&dq=256tb+ntfs+limit https://technet.microsoft.com/en-us/library/dn466522(v=ws.11).aspx That's GPT and not MBR and it's still confined to internal drives and not external drives. Still to be tested with 3TB+ SSDs when they get cheap if MBR can exceed 18TB. It's a matter of perspective. 1PB today is what 1TB looked like to us then when we were using 8GB drives. How long did it take for us to get from 8GB to 1TB? Not that long. It's going to happen and we are going to find ways to consume that space and want more. 2PB on NTFS would be tremendous but only if MS updates NTFS to v4.0 to exceed 256TB. Since 2PB is like the 2TB of today it really seems to be not a lot of space once we get there. I recall a 1GB SCSI drive seemed to be enormous during the 386 days but who am I to judge what capacity seems ridiculous today.
  12. 4aK? Which step? If you need the MAC OS it is free to all unlike Windows. . Some people have made it easy to transfer to a USB flash drive simplifying the process. Good any 2.5" models? This I'm not 100% on just yet. I have to try hooking up this 3TB 4KB 512e drive to XP 32-Bit to check if direct access of all 3TB of MBR data still works. My guess is you can't write to the drive in XP 32-Bit to the entire 3TB directly. I think it will still be capped at 2.2TB without the address translation adapter. Now if it turns out I can read / write to the entire 3TB then that would mean any 2.5" 3TB or larger could do the same. I found some more comments on that website: So given what is said there I'm not sure if this guy is saying as long as the drive is 512e or 512 Bytes to the OS no matter if the physical sector size is 8KB->64KB it won't make any difference and larger physical sector sizes would give larger and larger reachable MBR capacities without needing to go to GPT. 4KB would get at least 18TB 8KB would boost to 36TB 16KB would boost to 72TB 32KB would boost to 144TB 64KB would boost to 288TB, capped at 256TB Windows NTFS/exFAT limit. But since Step 1 won't happen with XP 32-Bit that is out of the question but looking at Step 2 increasing to 8KB->64KB Physical sector size seems to be the only way hard drives can boost MBR capacity limits. Since we discussed SSDs not having an actual physical sector size then it is possible for SSDs to mimic 128KB and 256KB sector hard drives that show 512 Bytes on the SATA connector end to continue the legacy MBR support on 32-Bit Operating Systems like Windows 2000 and XP. 128KB would give you 576TB 256KB would give you 1152TB breaking the 1 PB barrier.
  13. Yes I know the "e" stood for emulated but if SSDs don't have a defined Sector Size wouldn't they be emulating 512 Bytes? If it can appear as 512 Bytes then there is no reason they can't appear as 4KB or 64KB. MACS are Intel based now so yours probably can be made into a Hackintosh quite easily on the Z87. https://www.tonymacx86.com/ Is UEFI still stuck with this old limit? That was one of the cheaper ones available since you hadn't seen a 4KB bare SATA drive. Not a fan of Seagate either as far as reliability back in the day had a bad reputation except some of their recent laptop drives absorbed from Samsung are pretty reliable. Options are limited these days and prices goes up for everyone. SSDs are probably going to be the future so I'm not sure if 4KB drives will actually be mainstream. Why? They don't work with XP nor the adapter. It'll be quite awhile before I switch to 4KB Native drives assuming 512 Bytes and 512e disappear. Those would be the ones to stockpile for legacy support.
  14. Is there a page on all the forum commands / features and how to use them? How do I get the MSFN links from showing a preview or shorten links to a small clickable object? Can you create collapsible spoiler windows?
  15. SSDs should be 512 Bytes on the SATA connector end as they work on DOS->XP. Now if 3TB->18TB SSDs will be 512e that would make them useful. 31 Total MFM drives on an IBM XT now that would be a sight. I can't find any references to this limit. How did you calculate this? Did MFM Floppy drives and tape drives count against the 31 Total Drive Limit? Copied the wrong link. Here is the correct 4KB Native SATA model. Seagate 2TB 3.5 HDD V.5 (4Kn) 3.5" SATA Model ST2000NM0105 https://www.amazon.com/Seagate-2TB-SATA-Model-ST2000NM0105/dp/B01G3S8SGA Two more higher capacity 4KB Native SATA drive models. ST4000NM0085 https://www.ebay.com/itm/Seagate-4TB-Ent-3-5-4Kn-SATA-MPN-ST4000NM0085/152658137978?epid=1679560179&hash=item238b22537a:g:ASsAAOSw66pZjGh3 ST6000NM0125 https://www.amazon.com/Seagate-ST6000NM0125-Enterprise-7200RPM-256MB/dp/B01E1XS3W8
  • Create New...