Msi K8mm-v No Reconoce Sata
I am trying to make a bootable USB disk to install on a laptop. In the olddays, it was simple and can probably do it with less than 1G flash drive. I could build on sda1 and install on hda1 (PATA).But, in the name of progress, things are more difficult. It would take around 5G of flash. Booting 5M kernel and 30M ram disk takes several minutes.Building the kernel takes hours.
But the biggest problem is SATA.With a poorly made decision, IMHO, they named the SATA 'sd' as well. So, now i have to make sdb1 and install on sda1, if i am lucky. With both SATA and USB MSD fighting for the first 'sd' name, results are unpredictable. I get either sda1 UMSD and sdb1 SATA, or sdb1 UMSD and sda1 SATA.I am very tempted to, rip out the kernel and rename:1. 'hd' for SATA and 'sd' for UMSD2. 'sd' for SATA and 'ud' for UMSD3. 'hd' for SATA and 'ud' for UMSDWhat do you guys think?b.
I am trying to make a bootable USB disk to install on a laptop. In theold days, it was simple and can probably do it with less than 1G flashdrive. I could build on sda1 and install on hda1 (PATA).But, in the name of progress, things are more difficult. It would takearound 5G of flash. Booting 5M kernel and 30M ram disk takes severalminutes.
Building the kernel takes hours. But the biggest problem isSATA.With a poorly made decision, IMHO, they named the SATA 'sd' as well. So,now i have to make sdb1 and install on sda1, if i am lucky. With bothSATA and USB MSD fighting for the first 'sd' name, results areunpredictable. I get either sda1 UMSD and sdb1 SATA, or sdb1 UMSD andsda1 SATA.I am very tempted to, rip out the kernel and rename:1.
Aiwa Cx-na115 User Manual Software. View and Download Aiwa NSX-A115 operating instructions manual online. Panasonic Compact Disc. Call toll free 1-800-BUY-AIWA. (United States. Read the Operating Instructions carefully and completely before operating. CX-NA115 Compact disc stereo cassette receiver. Occasional care and maintenance of the unit and the software. PDF aiwa cx nma545 manual pdf (28 pages) - all categories stylessoftportal, aiwa cx na115 user manual free software, aiwa cx nma545. Need operating manual for aiwa digital audio system cx-na909. Stereo system user manual, guide aiwa nsx service manual aiwa cx na115 manual. AFTER EFFECTS CS3 PROFESSIONAL Software pdf manual download. Aiwa compact disc stereo system cx na303. Aiwa nsx sz900 cx nsz900 sm service manual 1st page. Goodwill find aiwa cx na115 stereo. Aiwa rc zas02 cd. Aiwa cx-na115 user manual software.
'hd' for SATA and 'sd' for UMSD 2. 'sd' for SATA and 'ud' for UMSD 3.' Hd' for SATA and 'ud' for UMSDWhat do you guys think?b.
I am trying to make a bootable USB disk to install on a laptop. In theold days, it was simple and can probably do it with less than 1G flashdrive. I could build on sda1 and install on hda1 (PATA).But, in the name of progress, things are more difficult. It would takearound 5G of flash. Booting 5M kernel and 30M ram disk takes severalminutes. Building the kernel takes hours. But the biggest problem isSATA.With a poorly made decision, IMHO, they named the SATA 'sd' as well.
So,now i have to make sdb1 and install on sda1, if i am lucky. With bothSATA and USB MSD fighting for the first 'sd' name, results areunpredictable. I get either sda1 UMSD and sdb1 SATA, or sdb1 UMSD andsda1 SATA.I am very tempted to, rip out the kernel and rename:1. 'hd' for SATA and 'sd' for UMSD2.
'sd' for SATA and 'ud' for UMSD3. 'hd' for SATA and 'ud' for UMSDWhat do you guys think?b. I am trying to make a bootable USB disk to install on a laptop. Inthe old days, it was simple and can probably do it with less than 1Gflash drive. I could build on sda1 and install on hda1 (PATA).But, in the name of progress, things are more difficult.
Msi K8mm-v No Reconoce Sata 4
It wouldtake around 5G of flash. Booting 5M kernel and 30M ram disk takesseveral minutes. Building the kernel takes hours. But the biggestproblem is SATA.With a poorly made decision, IMHO, they named the SATA 'sd' as well.So, now i have to make sdb1 and install on sda1, if i am lucky. Withboth SATA and USB MSD fighting for the first 'sd' name, results areunpredictable.
I get either sda1 UMSD and sdb1 SATA, or sdb1 UMSDand sda1 SATA.I am very tempted to, rip out the kernel and rename:1. 'hd' for SATA and 'sd' for UMSD 2. 'sd' for SATA and 'ud' forUMSD 3. 'hd' for SATA and 'ud' for UMSDWhat do you guys think?b. Click to expand.There is good reason why these are all labelled 'sd' these days - theyare all part of the same subsystem and are thus treated the same, withall the advantages that stem from that. But in all the many systems Ihave installed, I have never seen an issue with confusion about nameswhile installing.
Hard disks on SATA get enumerated first -installation media such as CD, DVD or USB come later. And yourinstaller knows fine which device it is running from.I don't know whether you are trolling, or if you've got so hung up in animagined 'better way' that you are making a mountain out of a molehill.But this is not a problem for anyone else. Click to expand.No, they are not separated - they make use of the same SCSI subsystem.Originally there was more separation, with PATA totally separate fromSCSI, but they were rationalised and collected together. Since the SCSIsubsystem was more advanced, PATA and SATA were moved into it and thenthe USB MSD devices joined in.Obviously they devices use separate transport layers (USB, SATA, etc.).But other than that, they are handled very much the same.There are many advantages in this. The most obvious example is when youhave a USB-connected harddisk - it can be treated like an ordinary disk,with the same kind of mounting, the same filesystems, the sameflexibility for swap partitions, use in RAID setups or LVM arrays, etc.In Linux, it is an important part of the philosophy that you havedistinct layers, and within each layer different devices are treated thesame when possible.
So block devices are treated the same, whether theyare hard disks, network disk blocks, file loopback devices, RAID arrays,etc. And disk storage is treated the same, whether it is a hard disk, aUSB stick, a network storage, etc.
Click to expand.If you are building your own installer, you can arrange for it to set upwhatever naming rules you want. Typically in a modern Linuxdistribution, you use udev rules for this. If you want, you can givedifferent types of devices different names - you don't /have/ to followthe standard ones used by everyone else.
Msi K8mm-v No Reconoce Satan
And if you want, you can giveadditional symbolic link names to devices - just as is typically donewith cdrom drives.If you don't already understand this, you are not ready to build yourown installer.So I recommend doing some reading about device drivers, device naming,udev, and other base parts of a modern Linux system. I recommendfinding an appropriate Usenet group or other source of information andadvice. Get a VirtualBox installation, so that you can practice yourinstallation.
Study existing installers such as the ones used by RedhatFedora, Debian, Mint, Ubuntu, Gentoo, and Arch Linux. Think long andhard about whether the world really needs a new Linux installer - or ifyou would be better off working with one of the existing ones andcontributing useful changes there.I don't want to discourage anyone from trying to learn by doing, or anyother sort of learning, but it sounds to me that you are out of yourdepth. Using the inevitable car analogy, you have come to this cycleclub to complain about the state of car lighting systems, when youapparently want to build a rally car but have not yet learned to drive.
Click to expand.My understanding of linux kernel compiles is that you are free to leaveout much of the stuff you don't need, and thus can often make a customkernel that is smaller (and faster) than one that includes everything upto the kitchen sink so it can work on any 'puter.Are you talking about the image or all the source you need to compile theimage? I just checked, my biggest initrd.img file on this machine is14MB and change.
Msi K8mm-v No Reconoce Sata 7
That's MB, not GB. And that's the initrd.img thatships with Ubuntu, not anything that's been slimmed-down. Click to expand.You probably have an older kernel.The released LinuxMint/Ubuntu is 3.8.0 with 30MB initrd.Linux 3.13 compiles 1G bytes of modules, compressed to 200M.It takes 20 minutes to boot on a modern laptop. Most of themodules are not used and they are immediately replaced by theroot file system anyway. I managed to stripe it to 20M and4 minutes to boot. But it's a headache to compile and movefiles back and forth.Perhaps there should be a 'b' option that build the boot modules,in addition to the 'm' option.All these work because i am trying to replace one line in the kernel.' Root drive is not ready, press 'S' to skip'.The USB root drive will be ready, just need a small delay.Pressing a key to skip is no big deal, except when there is nobodyto press it in an embedded system.
Yes, but the newest release is to compile everything as module.I have to move files away, build the ramdisk, then move themback to /lib/modules.You probably have an older kernel.The released LinuxMint/Ubuntu is 3.8.0 with 30MB initrd.Linux 3.13 compiles 1G bytes of modules, compressed to 200M.It takes 20 minutes to boot on a modern laptop. Most of themodules are not used and they are immediately replaced by theroot file system anyway. I managed to stripe it to 20M and4 minutes to boot. But it's a headache to compile and movefiles back and forth.
What a coincidence! I just inherited an MSI K8MM-V and was trying to decide if it's worth keeping.
I will be quite interested to hear the results of your build.As LSS10999 already mentioned, Win9x has a limit of around 127 or 128 GB. Most of my Win98SE systems use either 80GB or 120GB IDE drives. I've experienced no problems with them.I've had mixed results with SATA and Win9x.
One build of mine is an ABIT KT7A with a SYBA SD-SATA150R and 80GB drive running Win98SE. I haven't touched that machine in a few years now, but I don't remember having any problems with it.Another PC that I built for my brother is an MSI KM4M-V with onboard SATA controller and a 20GB IDE hard drive running Win98SE. For some reason, when the SATA controller is enabled in that PC, Star Wars Rogue Squadron stutters badly. Everything is fine with the SATA disabled in hardware manager. Weird.Oldbie Posts: 962 Joined: 2012-11-30 @ 19:21 Location: Chicago.
Very interesting! Despite having several V1, V2, V3, and V5 Win9x machines at my disposal, I chose to play it under WinXP SP3 using the Deus Exe mod with these specs:PC Chips M861G v1.6a motherboardAthlon 64 3400+ Venice S7541GB (2x512) RAMNVIDIA GeForce 6 6800 GTSB Audigy 2 ZSOn my LCD monitor at 75hz, max FSAA etc, I consistently got 75 FPS, except for when I first met with Helios. The poisonous green fog at the base of its 'pedestal' caused dips into the 30s.I was trying to compromise between keeping the game original vs getting maximum performance with some 3rd-party bug fixes. At one point, I did try running it in GLIDE mode but I couldn't tolerate the jaggies. Back in the day, jaggies didn't bother me. 20 years later and they really bother my eyes. So, 6800 GT it was with FSAA maxed out.Some games are still OK without FSAA.
Others, such as Deus Ex, benefit greatly from it.By the way, there shouldn't be a difference between 2.5' and 3.5' SATA drives. If you're having problems with 2.5' drives, you'll probably have similar problems with 3.5' drives. Make sure you're using drives with 512B sectors. Most modern drives use 4K sectors and may cause problems.
Try partitioning them using the original DOS FDISK included with Win9x. When it comes time to choose a size, use a percentage rather than a whole number. For example, on a 250GB drive, choose '25%' for a 62.5GB partition. And wait.A few years back, I wrote a Win98SE setup guide and posted it here:Oldbie Posts: 962 Joined: 2012-11-30 @ 19:21 Location: Chicago. Cyclone3d wrote:You might need to get a Promise S150 PCI SATA controller because they have Win9x drivers. The early VIA SATA controllers were very, very, very, very buggy. Chances are that it will not work properly with that large of a drive.
Or even detect it at all.That motherboard often came with a chipset that had a buggy SATA implementation which had trouble reading anything that was SATA2. This problem was reverted with the southbridge that uses the VT8237R Plus instead of the regular VT8237R.
I always tried to make sure I got one with a Plus southbridge as these would at least see the SATA 2 drives.