Jump to content


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

16 Good

About Nomen

Profile Information

  • OS

Recent Profile Visitors

3,359 profile views
  1. So none of the service packs for NT4 addressed the 28-bit LBA issue? We know that XP-SP0 had the issue and was fixed relatively quickly in 2001 or 2002, and win-2K also had the issue and was fixed, but MS did not fix the issue with NT4? Perhaps because SP 6a was released in Nov 1999 - this predates any of the 28-bit LBA fixes from MS I guess. Note this from wikipedia: ----------- Service Pack 7 was planned at one stage in early 2001, but this became the Post SP6a Security Rollup and not a full service pack, released on July 26, 2001, 16 months after the release of Windows 2000
  2. I tried searching for this on the web in general and also here at msfn and couldn't find anything. Other than perhaps a 2 tb max which is a common limit for a lot of motherboard/OS combinations, does NT4 (SP6) have any specific limitation on hard drive size - specifically for IDE drives? I'm currently running a couple of NT4 servers (one on a P3 motherboard, another on a P4 motherboard), both currently have 80 gb drives, and I'm thinking of cloning them to 240 gb SSD and then using a small IDE-SATA adapter to run them off the SSD instead. So I'd be going from 80 gb to 240 gb in this c
  3. The Soyo motherboard in question has a 2002 or 2003 bios and I'm sure there are no socket-478 P4 motherboards ever made that were not LBA-48 bit capable straight from their original factory V1 bios. I could have formatted the drive as a single volume (single primary partition) even booted directly into DOS, but if I wanted to test the ability to read and write to logical sectors far out beyond the 137 gb point I assume that by creating 4 volumes as I did that the volumes are assigned fixed sector positions (start and end) and thus writing directly to the last volume would have beyond the 137
  4. To recap: I have a few Soyo socket 478 motherboards with Intel 82801DB IDE controller. I have installed long ago the IAA which replaces ESDI_506.pdr with IntelVSD.VXD and IntelATA.MPD for the IDE drivers. I attached a 250 gb SATA drive using the small IDE-SATA adapter (the adapter plugged directly into the second IDE port on the motherboard) and from DOS (format + fdisk) I have formatted the drive into 4 volumes (65/65/65/44 gb). During POST startup the drive is detected and displayed properly by the bios in the secondary master IDE position. In Windows I have copied several hundr
  5. I just tried Opera 12.02 and got different results the first time - it can't connect to bgp.he.net because of security protocol. I went in and enabled all protocals in opera and got the same error. I then renamed my hosts file (so no hosts file) and restarted Opera and it worked, and I could get info on IP's without getting the javascript message. I then restored my hosts file and restarted opera and it is still working so I don't know what's going on but I'm happy it's working again.
  6. I bought a few of these small IDE - SATA boards on Ebay recently. They are bi-directional adapters and can be plugged directly into either a motherboard IDE connector (to provide a SATA port to connect to a SATA drive) or can be plugged into an IDE drive (to allow an IDE drive to be connected to a motherboard SATA connector). I know there are lots of IDE/SATA/USB adapters around - this board has no USB connectivity. I'm wondering about connecting a large SATA drive to an IDE port on Win-98 systems and the 137 GB problem. A system I'm thinking of trying this on has an Intel 82801DB Ultra A
  7. I was sort of expecting more activity in this thread, but a lot of the old timers must be gone. I was expecting someone to say something about what (if anything) is going on with the RLoew files (in general) or the sata drivers in particular - but nothing. Or is that happening in the special projects sub-forum? I've been experiencing problems (freeze-ups when accessing SATA drives) with my current setup and I'm exploring alternate solutions for connecting SATA drives to my primary Win-98 system. I have a bunch of SATA driver files scattered across various drives and might have to pull
  8. I used to stay on top of this but that was a while ago. I'd like to pick up a few PCI sata controller cards and was wondering which of these now have working win-98 drivers and which ones don't. I seem to recall that the only working controllers were the 2-port 3112 cards, not the 4-port cards and not the 351x cards, but maybe I'm wrong on that. And is there now a public-domain RLoew sata driver that works with these Sil controllers?
  9. I obtained the above SST files and ran the updroots thing - got no messages after each command (so I assumed no errors). Does this take effect immediately or is a reboot required? Is there any sort of on-line test or check to see if these certs are working correctly?
  10. Earlier in this thread someone posted a link to rzbrowser-tls12-20180504.7z. I had already downloaded and installed that package in Sept 2018 so I don't know if there's anything newer. I still use FF2 on my win-98 system and haven't really experienced any reduction in usefulness over the past year for the sites I visit. One thing that has been a downer for me is that I somewhat often use https: //bgp.he.net/ with Opera 12.02 and at some point a week or two ago that stopped working. I can bring that page up in FF2 but when I enter an IP to check I get a "this site requires javascript so pl
  11. Looking at web searches it's clear that I'm not the only one that has or would want to continue to use ghost 2003 to clone their windoze 7 drives but from one of my above posts it's clear that starting with vista and certainly with 7 that there is something about the ntfs boot or disk structure that ghost 2003 (and even newer versions) don't seem to know about or replicate correctly. Ghost is not a sector-by-sector copier so it has to know about the logical structure of the file system it's dealing with when it clones drives. It would be nice to find some instructions on what *exactly* to d
  12. Well I put the clone drive (as the only drive) in a PC with a CD rom drive and booted a win-7 CD and selected the repair and it did something very quickly and then put the drive back into the target pc and it booted up just fine. I would like to know how to "fix" a drive like this in this state by slaving it to a working win-7 PC and performing what-ever system-level task or operation to the boot records or what-ever but I have not seen any such instructions on how to fix a drive like that under those conditions. Happy new year, by the way. It must be new year somewhere in the world by
  13. Still reading your post, but just to comment: > Allow me to doubt that you had at any moment two partitions active, as this is - >besides not allowed - almost impossible to obtain with *any* "Normal" tool Ah, yes. I was wrong. Disk Management shows in real time that when using command line diskpart to mark partition 1 or 2 active that only 1 of them becomes active - the other one (if active) becomes non-active. So when the "system reserved" partition is Active, I get the first error in this thread upon boot (0XC000000e can't find required device). When the second (
  14. I attached the clone drive via usb adapter to a running win-7 system and used drive management to set the second partition to active. The drive has 2 partitions, the first one being very small (100 mb) named "System Reserved". I put the clone back in the target PC and tried booting it again, this time I got the message "bootmgr was missing. Press cntrl alt delete" I did the USB thing again with the drive and now set the first partition to active as well. So they were both set as active. Put it back into the target and booted - still got the bootmgr message. Maybe only the firs
  15. I've cloned XP dozens of times back in the day, with Ghost 2003, and the clone always booted. I've rarely cloned a win-7 drive, but it seems that every time I do, the damn thing won't boot and I have to putz with a setup CD or drive tool of some sort to "fix it", but I never figure or am never told what the hell the problem was. An example error is: 0XC000000e The boot selection failed because a required device is inaccessible. Why isin't Ghost cloning this thing so that it's bootable? Is this a known thing for ghost 2003 or is there some ghost setting that I don't have right? What bit
  • Create New...