Jump to content

AtomikNoize

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by AtomikNoize

  1. Okay, So i recently acquired a USB 2.0 powered hub, the wall adapter for it was 5vdc @ 500Ma , and me being too curious i had to modify it to be self powered. I ran the 5v- and 5v+ from the USB to PC connection and routed those two pins two the respective Positive and negitive terminals of the dc adapter jack on the other side of the hub. I then plugged it in and bang! it worked right away, i later un-soldered all the leds, and then un-cased all the usb devices i planned to attach to this hub. Afterwards the entire unit contained 1 Bluetooth adapter, 1 4GB flash drive, and a logitech wireless remote transciever. all of this is only 3 MM thick !, just thin enough to jam inbetween the case of a laptop / netbook. Im gonna take some pictures and make a better post , but i was too excited to keep this too myself. I wouldnt doubt if its been done before, but definalty a first for me.
  2. I will definitely try that on my friends dell boxes. But i was thinking mabe its a problem with KonBoot its self and the way it injects its self into the RAM , because if the system boots without Konboot, well then i would assume KonBoot is the culprit in this situation , but either way im really confused, it would be nice if there were a little more documentation on using konboot, as well as using it conjunction with grub/grub4dos. Anyone got ne links ?? Either way I ain't gonna give up until i figure this out lol..
  3. After Reading your last post Ekoh, I decided to go and try mine on a couple different pc's , a few at my friends house and my G/F's laptop. Now im stumped as well because the three new machines i tested this on all failed to work. it did work in Halo's VM , and both my Desktop, and Laptop. My G/F's laptop was afflicted with the same "Filesystem is NTFS" than hangs. The other two at my friends house are both dell boxes, both restarted right after the Windows bootloader executed. Not a clue why .. Its only so strange because i Had it work on Two other computers and on the VM. Maybe this has to do with certain hardware configurations , or some sort of limitations of certain BIOS's. Hope somebody can figure this out, three days of messing around and i just realized it only works on my machines. I'm to get frustrated lol :)
  4. Glad My post possibly helped a little bit, but it seems strange your still having so many issues. As Far as I am aware, after the KonBoot splash screen , and after it loads it should in fact loop back to the Grub boot menu, this is how you then tell it to boot off the Actual Hard drive (windows) on the PC, To boot Windows after loading Konboot, you\'ll need a second Menu entry such as title Boot Windows off First Hard Disk after Konboot root (hd1,0) chainloader (hd1,0)+1 boot If you Boot konBoot , then when your returned to grub , boot Windows it should work. I just tryed again and it still works. (on my system anyway, and on Halo\'s VM ) Hope this helps. This is what my whole menu.lst looks like , all entries work on my setup. color green/black red/blue timeout 120 title ---===KonBoot (Inject Konboot into Ram)===--- kernel /boot/memdisk initrd /boot/konboot.img title ---===Boot from HardDisk after KonBoot===--- root (hd1,0) chainloader (hd1,0)+1 boot
  5. If you but the small MEMDISK file from syslinux package into the /boot folder on your usb drive, you can use this following code in your menu.lst to boot KonBoot and any other floppy disk image , no chainloading or root commands needed. :) title KonBoot kernel /boot/memdisk initrd /boot/konboot.img just be sure to put the floppy disk image in the /boot folder as well , it should work , just tested on three diff pc's. You can find syslinux package using google or from a linux distro with memdisk in the boot folder.
×
×
  • Create New...