Jump to content

Molly Dawn

Member
  • Posts

    35
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by Molly Dawn

  1. True, but most ideo cards which officially support windows 7 will work with either boot option.

    I didn't know that about the bitness of uefi not being hard coded, but as I said I only researched the technology reading on places like Toms Hardware and here and googling things.
    My fx9350 AM#* board has the uefi option (hence the researching) but ultimately I went with legacy bios as the boot option as that is the option most familiar to me. (and my SSD's on this system are all smaller than 2tb so MBR works just fine).  R9 390x and 1050TI Nvidia work fine in legacy bios mode and still run 1080p with no issues.

    Yeah probably a lot of if not all Ryzen and similar generation intel stuff is uefi only, didn't test any of it as I typically buy hardware based on windows 7 compatibility, and all my researching of such systems has shown it to be hit or miss if it will work or not. and een moreso if it will work stable and trouble-free or not.  I'e read success stories on here and watched youtube ids of it working too, but for eery succesful ryzen/win7 build I usually see an equal number of horror stories with unsupported drivers and even failed installs that can't detect any disk to install to and other problems.  From what I seen its actually easier to try and get 98/ME running on AM3+ than to get 7 working /properly/ on Zen/ZenII, etc. and modern intel.

     

     

  2. I hae tested the keyboard and rec. on another windows 7 machine and it has no problem. I also tested the keyboard from a known working system and it has the same issue on this system.
    It could possibly be an issue related to MS. office or another program that uses hotkeys, I'll look into that next.  Something is definately remapping the key though as I tried a few different keyboards wired and wireless, and een an older PS/2 type (with a known good usb adapter) and the issue persists, yet the original keyboard has no issues whatsoeer when booting linux lie distros, or when used on another pc for windows 7.   I will check the registry key you listed and check programs for hotkeys that could be affecting it and report back. Thanks :)

  3. the 600E chip, the "E" indicates it is a slot type PIII using the newer 'coppermine' core, which in my experience is less stable with win9x, It /may/ be an undocumented integer bug, or some other error related to changing to a new smaller die for the processor, as the earlier 'Katmai" core chips (and the PII Deschutes from which they were  deried) didn't exhibit this problem, but whateer the reason, the 'bug' appears to be fixed in the later 'tualatin' core P3.  Despite their win9x issues, these chips are good for OC headroom, and run puppy linux quite well.
    All soket type PIII chips were either coppermine or Tualatin, as the earlier 'katmai' core was a slot 1 only part. 
    THe 600E has its L2 cache on the chip itself like modern CPU's instead of separate but on the same card as it was with the PII and earlier PIII. 

    THis ON-Die cache helps with OC headroom, but it (or the new manufacturing process) may well be responsible for the win9x issues as well, which would explain Tualatin not haing the problem, as by that time they'd refined the engineering process and motheboard manufacturers had improed chipset designs as well.
    FOr a linux system (or windows NT) the 600e is superior to the standard 600 and 600B (both Katmai core) PIII slot type processors, and has a better fully implemented SSE instruction set..
    Only for win9x is the older Katmai core desireable though the newer Tualatin core (which can run on some slot type boards using a slotkit adapter) is superior to both in either win9x or NT, and lacks the 9x stability bug of coppermine.
    THis bug affects both 98SE and windows ME on coppermine processors, and usually results in Kernel32.dll errors, frequent bluescreens, and program crashes as well. THis increases exponentially if using more than 128mb of ram on a coppermine cpu in windows 98se or windows ME.

    No issues with linux, but users should be aware of the win9x issues.

    Apologies for dragging up such an ancient thread, but the information is relevant,

  4. Win ME will boot fine when you swap the motherboard.  Win XP, probably not.  Unless you can find EXACTLY the same motherboard, or at least the same exact chipset then MAYBE XP would boot as well. NT operating systems are REAL picky about this sort of swap so the chances of it working are extremely slim, but 9x will usually work just fine . you /may/ need to uninstall things in device manager to resolve resource conflicts, but most of the time it just works.  Just this morning I used the HDD out of a socket 462 athlon machine to boot an old deschutes PII machine for testing purposes and win ME booted right up.  It didn't have drivers for the oddball S3 graphics card in the PII but that didn't matter as all I needed was to verify that the machine would boot (to ensure it was the hdd in the PII and not the ATA controller that was dead).

  5. 0.7amps @12 is more than enough to handle the average fan no problem. Only high performance fans like those made by delta electronics (the mini jet engines like I use on my FX9350 radiator) are going to draw more power than the motherboard can supply.  Thats why Delta fans come with molex power connectors or bare wires instead of 3/4pin fan headers (usually).  at any rate the fan amp ratings are printed on a sticker on the back of the fan, so its easy to see if one will work or not.  THere are a lot of good fans in your amp range, and even some of the lower powered Delta's are right at 0.7@ and thus compatible as well.  (the 25mm thick ones) the 35mm thick ones like the 9xxx series FX chips need pull anywhere from 1.5 to 4a each, and thats when you need to plug them into molex connectors directly.

  6. I never used uefi personally and always set legacy bios mode, but from what I read on the matter, uefi and OS must be bit compatible, but it /is/ compatible with 7.  it just has to be win 7 64 bit as 32 bit win 7 doesn't support uefi (and there are only a few 32 bit uefi systems anyway.)  WHy use uefi anyway (just curious)  Unless you are needing to use gpt hdd or ssd (disk larger than 2.2TB).  legacy bios mode works just fine with MBR disks (2tb or less).  THis is just based on researching UEFI so someone who has actual experience can probably clarify things better, though.

  7. Corsair H60i is cheap and a huge upgrade from stock cooler.  use a good thermal paste like Artic silver creamique or a close compeditor, and you should be good.  also if the vrm chips are hot you can get generic "GPU ramsinks" and some thermal adhesive and add cooling to the vrm mosfets. DONT use thermal tape. they get way too hot for that.

    H60i should be more than enough for stock settings, and probably enough for a mild OC as well. (3.6ghx MAYBE 3.7 if you got a good chip).

  8. It /MAY/ be as simple as setting SATA mode to IDE if its set to AHCI or AHCI if its set to IDE. Assuming both machines are similar architecture (both AMD64 or both P4 or later Intel) assuming its a NT based OS.  In the eent that changing the Sata mode in bios gets it to boot (and setting boot to legacy instead of uefi if thats applicable) you want to copy the data on that first boot and do NOT restart when prompted until you are finished copying the data to another HDD.. 

     

    The reliability of simply plug and play hdds and only needing to install new software for the new machine is sketchy at best with nt based systems.  with 98/ME it would generally work, but this is one case where windows 7 (and any nt based windows) is actually inferior to windows 9x.    copying a hdd to a new one for the same computer requires 3rd party software on NT systems but on 9x you could just boot in safe mode and with windows set to show hidden and system files simply copy the contents of C: to D: or whatever letter the new disk was assigned.  This simply does not work with windows NT family Os'es, without special cloning software.

  9.  lately the "v" key (and only that key so not weak batteries) on my logitech keyboard stopped registering input in windows. (the key is working as it functions when booting lie USB linux) but on windows it does nothing.  OS is Windows 7 Pro x64, and this is on a FX9350 (temperatures are well within tolerances ) keyboard recieer is attached to a USB2.0 port with legacy usb support enabled, and as I said works fine in linux lie distros.  worked fine in windows until the other day too, and now nothing no v key (copy and pasted that letter) whatsoeer in windows.

    Its not a ram issue, as I tested with memtest boot cd, and also tried ram from another win 7 system with a full working keyboard. 
    Keyboard is clean and key is functioning it just doesn't register in windows.  Wondering if maybe somehow some windows shortcut or other could accidentally got enabled and caused this, and if theres any way to fix it short of reinstalling windows or rolling back to a backup from before it started acting up.  Maybe some form of accessibility options or something acting up

     

    apologies for grammar atrocities, typing with one key not working is a pain. needing to substitute words without that letter and such makes for bad grammar..

  10. depends on the context.   If its to make money off the pirated product then absolutely, I'd report them in a heartbeat.
    On the other hand, if its just someone doing it occasionally for personal use either because they can't afford the product, or want to 'try before they buy' then its hard to say, but most likely I would look the other way.

  11. more 4g towers.    out here in the middle of nowhere Kentucky, signal is a real problem (but the only broadband option aalible, and only verizon seres this area and unofficially at that. (closest 'official' location is Paducah. and thats a good 20 miles away.

  12. one per computer, but several computers. from old legacy systems (some of which predate the 8086) to high end win 7 gaming machines and pretty much everything in between.  386 and slower machines are pure dos or some earlier OS that predated dos (BASIC and the like for pre 8086 stuff),
    80486DX to K5/pentium 100 - it depends.  slower than DX2-66 and its pure DOS, DX2-66 and higher, its Win ME or some lightweight linux distro.

    Pentium 100 - PIII (Katmai) always win ME

           PIII (coppermine) P4 wilamette/early Athlon Linux distros.  I had bad luck with win9x on coppermine/celeron and early athlon

         PIII (Tualatin)/P4 (Northwood/prescott)/ AthlonXP/early Athlon64 -Win ME (sometimes with Debian linux dual boot)

    S939 Athlon64/S775 Intel to AM3+  Almost always Win 7, unless the specific chipset happens to hae drivers for ME (There are a handful of them that work surprisingly enough)
    If its a supported system then dual-boot win ME and win 7 otherwise dual boot win 7 and KDE linux.

    There are some things you just can't get away from native win9x for, and virtualixation/hypervisors just won't work for. (Though the LLE project 86box is certainly trying to get natie win9x running as it should in an emulated eniornment. albeit slowly (best my Fx9350 will do is a mobile pentium MMX @166 and voodoo 3 graphics) so currently native win9x is still the best option.

  13. not really.  it is /redundant/ and has been since the introduction of zip disks, cf cards and usb flash memory, but there will always be a use for a floppy drive, especially hen working with legacy systems that predate usb1.0 or IDE thus making flash drives, zip disks or cf cards unusable in those cases). and no not all such systems suppor adding an IDE or USB controller card.  (MFM RLL and ESDI come to mind.  Most won't boot from LPT1 but many do support disks using paralell port, so once booted to dos via floppy all thats needed is a LPT1 zip250 to transfer the data to another machine. (or a LPT1 cdrom if you're trying to install winME on such a system (original 95 and the floppy version of 98 can be squeezed onto a zip250 so no cd drive needed and only the one ME boot floppy rather than the dozens of install floppies). but 98se and ME will require a LPT1 cdrom (or scsi if you're /really/ lucky and the board supports it.)

  14. Mechanical dries? then definately western digital.  either the black series or velociraptor series depending on the system.

    for SSD then crucial as micron chips seem to hae the best reliability/durabillity.  a bit slower than the really high end samsungs, but with the bus limitations of AM3+ the difference is marginal at best, so the longer lasting crucial ssd's are the better choice.

  15. worst, 10, then 8.1 then 8 in that order.

    best Windows 7 and second best, windows ME.  Also gotta throw vista in there as one of the 'good' ones too, as what little experience I had with it showed a lot of potential. it just had driver issues on my old hardware, which ran fine and blazingly fast on ME.

    I know a lot of people love XP and so compare 7 to XP, but I never messed with XP so I can't really comment, but there are certain things I still use windows ME for to this day (on real hardware not vM)

  16. A lot of the bad reputation was attributed to trying to run it on underperforming hardware, like the early celerons and durons.  Also trying to run ME without some form of 3d accelerator be it on the main gpu itself, or as a separate (voodoo type) card, is just asking for trouble.   windows ME GUI is 'heavier' than 98se, and that little bit of eyecandy comes at a price.  It needs a better GPU to be stable.
    (nothing too fancy, just either at least a voodoo 1 alongside a decent 2d card, or something like the ATI rage pro 128 or Nvidia riva/tnt as a dedicated one-card gpu as bare minimum for stability.

    K6-III+, PIII (Katmai) or better (Only "Tualatin" core or later celerons or S754 or later Semprons though) and at least 128mb if your ram is PC100/133.  64mb is the minimum for stability if its DDR.

    ATA controller should be at least ATA100, preferrably ATA133.  Minimum disk speed 7200RPM,  (5400 if its an XP era HDD with a big buffer cache)

    L2 cache is a must, whether its on the motherboard, or on the CPU itself doesn't matter, but a L2 cacheless system is not going to play nice with win ME, especially if you do anything cpu intensive with it.

    Most other issues were printer driver related.

  17. for emulation I recommend 86box as its a LLE and thus better suited set it to emulate a pentium 150 with 128mb ram and install to a .IMG (raw) disk. then just use a usb 'burning' tool that supports dos mode MBR booting and burn the .img to a physical HDD.  obiously that would require an OS to be installed on the system, but you could always use a 30 day trial (dont enter a cd key) of win 7 on a different hdd just to boot the machine and run 86box to do the install and then burn the image to the HDD you actually plan to use.  complicated yes, but it does work.

  18. Ok Thank You.   I wasn't sure since it uses relatively high performance 3d nand flash but crossreferencing with Toms Hardware I saw the release date of the drive was welll befpre the end of official MS support for 7 so I just wanted to be sure.   Ordered tonight. hopefully it works with no issues.   On a related note, would Aomei or gparted be better to clone a MBR partitioned boot drive. I know the acronis software included with the drive in question has issues with win 7 and with MBR disks in particular.

×
×
  • Create New...