Welcome to GOFASTMOTORSPORTS.com ... ... ... Green Flag - Green Flag - Go Go Go ... ... Brought to you by Ricks Satellite - Where the Big Dish Rules!

Ricks Satellite Wildfeed and Backhaul Forum
Register Latest Topics
 
 
 


Reply
  Author   Comment   Page 2 of 3      Prev   1   2   3   Next
wejones

Avatar / Picture

Registered:
Posts: 5,641
Reply with quote  #16 
Quote:
Originally Posted by techjunkie02
I just read thru the links you provided, and I think this one is the key post;

I first made two partitions on an IDE hardrive.
I connected the IDE hardrive to the receivers motherboard.
I loaded the firmware onto a usb stick.Put it in the back of the receiver
and tuned it on.It will boot and ask if you want to load firmware.
It will put the operating system on the smallest partition by default.
Once firmware is loaded.It will reboot and you are good to go.
You can record programs to the second partiton on the drive.

I think you first need to know what kind of partitions those first 2 he created were.
Because, from what he said, I'm thinking that the AZ just went ahead and created it's needed file structure, Inside of that 1st partition. Irregardless of the normal partitioning rules! And, when it's done, you are able to use the SECOND partition as additional storage.

So, I would pull the DOM module and view it's physical structure using the GParted program, and see how it's created, and see if that gives me enough info to know what partitions to make on the HDD.

If I can't determine it. I'd just start making 2 basic linux partitons on the hdd, and try what he said and see what happens. If it works, great! If not, re-do to different partition type(s) and try again. You've got nothing but time to lose, because you can always just re-install the original DOM!!

Hope that makes sense to you [wink]


 That is basically what I did, but it wouldn't let me record to the second partition. 
Originally, the Azbox DOM had 4 partitions, ie:

/dev/hda1               135.6M    108.3M     20.3M  84% /MMP
/dev/hda2                15.5M      2.8M     11.8M  19% /PLUGINS
/dev/hda3                 7.7M      4.5M      2.9M  61% /DISK2
/dev/hda4                78.4M     54.3M     20.1M  73% /Download

I put 2 primary linux partitions on the hard drive, one small and 1 large. The small partition was about twice the size necessary to hold all 4 Azbox partitions.  After the Azbox booted, the drive had 4 partitions, ie:

/dev/sda1         135903  106776     21898  83% ......
/dev/sda2          22308    1885     19219   9% ......      I ommitted the long mount points here
/dev/sda3          14529    1966     11760  15% ......
/dev/sda4      157353196   49540 149308912   1% ......

All 4 were generic linux partitions, and as you can see, it basically deleted my 2nd partition and addded all the extra space to it's  hda4 or /Download partition. And the Azbox wouldn't record to this directory.

I was able to reduce the size of this 4th partition, but since there is apparently a maximum of 4 primary partitions, I wasn't able to create an additional partition to record to.

I then decided to try to delete the 4th partition and replace it with a smaller extended partition, and then add an additional partition.  This kind of worked, except that the 4th and 5th partitions overlapped.  Ie they started where I intended them to start, but they both ended at the end of the disk space, which just didn't seem right.  ie:

Device     Boot  Start       End   Sectors   Size Id Type
/dev/sda1            1    289169    289169 141.2M 83 Linux
/dev/sda2       289170    337364     48195  23.5M 83 Linux
/dev/sda3       337365    369494     32130  15.7M 83 Linux
/dev/sda4       369495 320173055 319803561 152.5G  5 Extended
/dev/sda5       658664 320173055 319514392 152.4G 83 Linux


I also tried to make the end of the 4th partition where I wanted it, as extended, and then create
the 5th partition, but fdisk insisted that the 5th partition must be inside the 4th partition, which again doesn't make sense to me. 

Anyway, I'm kind of out of ideas relative to putting everything on 1 disk.  I guess i'll have to buy some adapters to create 2 separate disks. 

One weird thing.  When I put the hard disk in the RPi, I didn't realize it at the time, but it must have automatically mounted the hard drive. Not knowing this, I mounted it manually on /mnt/az1 thru 4 .  Somehow, this worked, ie I had the hard drive mounted twice.  Everything worked OK, until I was done.  I then umounted the drive where I had manually mounted it, and then pulled out the usb plug, and everything went crazy with errors.
   I've hot swapped usb thumb drives before without errors, but it didn't seem to like me doing that with a usb hard drive for some reason.

I guess I'll put the DOM back in the Azbox for now. 



 
techjunkie02

Registered:
Posts: 2,310
Reply with quote  #17 
"Device     Boot  Start       End   Sectors   Size Id Type
/dev/sda1            1    289169    289169 141.2M 83 Linux
/dev/sda2       289170    337364     48195  23.5M 83 Linux
/dev/sda3       337365    369494     32130  15.7M 83 Linux
/dev/sda4       369495 320173055 319803561 152.5G  5 Extended
/dev/sda5       658664 320173055 319514392 152.4G 83 Linux


I also tried to make the end of the 4th partition where I wanted it, as extended, and then create
the 5th partition, but fdisk insisted that the 5th partition must be inside the 4th partition, which again doesn't make sense to me. 
"
--------------------------------------------
Because you already had 3 primary partitions, you can then EITHER create another primary, OR, create an extended that then acts as a CONTAINER for all the additional partitions within it. It, the extended partition, is not actually used for storage of any data itself, other than the partitions that it contains.

so, you can have 5, 6, 7, 8.... partitions, but all of them after 3, must reside inside the "Extended" Partition.

Did you ever post a "map" like the one above for the DOM itself just the way it comes out of the AZ??  I can't remember if I've seen one of those, has it been posted?

__________________
--- a collection of semi-functional equipment, backed-up by a pile of questionable items!
wejones

Avatar / Picture

Registered:
Posts: 5,641
Reply with quote  #18 
Quote:
Originally Posted by techjunkie02
"Device     Boot  Start       End   Sectors   Size Id Type
/dev/sda1            1    289169    289169 141.2M 83 Linux
/dev/sda2       289170    337364     48195  23.5M 83 Linux
/dev/sda3       337365    369494     32130  15.7M 83 Linux
/dev/sda4       369495 320173055 319803561 152.5G  5 Extended
/dev/sda5       658664 320173055 319514392 152.4G 83 Linux


I also tried to make the end of the 4th partition where I wanted it, as extended, and then create
the 5th partition, but fdisk insisted that the 5th partition must be inside the 4th partition, which again doesn't make sense to me. 
"
--------------------------------------------
Because you already had 3 primary partitions, you can then EITHER create another primary, OR, create an extended that then acts as a CONTAINER for all the additional partitions within it. It, the extended partition, is not actually used for storage of any data itself, other than the partitions that it contains.

so, you can have 5, 6, 7, 8.... partitions, but all of them after 3, must reside inside the "Extended" Partition.

Did you ever post a "map" like the one above for the DOM itself just the way it comes out of the AZ??  I can't remember if I've seen one of those, has it been posted?


Thanks.  That explains a lot, ie the container not actually holding data, only partitions.  So to actually get the 5 partitions I want, I need to make a small linux partition 5, and then a BIG linux partition 6, that will hopefully be the one to store recordings.
  Good... I'll give that a try later.

  Re the fdisk map of the DOM.  I never mounted it outside the Azbox because I need a female to female ribbon cable to do that, but it is pretty much identical to the hard drive, except that the DOM has a few more files on it I think.   Since I have the DOM in the Azbox now, and the Azbox has fdisk, I just ran that, and got:
Quote:

BJ-Azbox[~]$ fdisk -l

Disk /dev/hda: 256 MB, 256901120 bytes
16 heads, 32 sectors/track, 980 cylinders
Units = cylinders of 512 * 512 = 262144 bytes

 
Device Boot    Start       End    Blocks   Id  System
/dev/hda1               1         560      143359+  83  Linux
/dev/hda2             561         624       16384   83  Linux
/dev/hda3             625         656        8192   83  Linux
/dev/hda4             657         980       82944   83  Linux

Seems like the fdisk in the Azbox uses different units.  Not sure if it's caused by it being a DOM instead of real disk or just the version of fdisk.  I ran this list back when I had the hard drive in there, but I didn't think to save it.

Anyway, I have the DOM back in the Azbox now, and that's yet another story. I'm going to put that in another post.  


wejones

Avatar / Picture

Registered:
Posts: 5,641
Reply with quote  #19 
Well, as mentioned in the above post, I ran into other problems. 

As mentioned above, I decided to put the DOM back into the Azbox.
On turning it on.....booting...booting...booting....forever, nothing on TV. Reseated the DOM, same thing.  I figured I must have somehow zapped the DOM, even though I had kept it in a plastic bag after I removed it. 
So I decided to put the hard disk back in.
Booting...booting....booting.  Tried 2 different cables.  Same thing.
So I decided to put the thumb drive in there to re-load the firmware.
Booting...booting....booting.
I was about out of ideas, but I thought that maybe the power plug might be polarized, even though it goes in either way.  So I reversed the power plug.
Booting...checking checking.... came up with menu... told it to boot normally.... came up fine!?!?!?!
Turned it off. Pulled the hard drive, plugged in the DOM again..
Booting ... booting ...booting.  ???????   Tried it a few times, wiggling the DOM connection.  Same thing.
Then, for some reason, I decided to close the cover, even though it had been partly open when working with the hard disk.    Booted right up and worked fine.?!?!?!?!?!?
I'm just going to leave well enough alone for now, but I'm afraid that I might have put too much stress on the motherboard pulling that DOM in and out, and maybe generated an intermittant connection or something.  Can't believe that the things I was doing fixed it, but I don't have any better ideas other than a bad connection somewhere.
   Anyway, it's working now, so I'm just going to leave it alone for a while.


wejones

Avatar / Picture

Registered:
Posts: 5,641
Reply with quote  #20 
  Yesterday, after the explanation of extended partitions being a container, I thought I understood enough to do this. Nope.
So, again, using fdisk, I created the 4th partition as extended, and then created partition 5 and 6 inside that.
I thought that it had worked.  Ie after doing this, fdisk reported:

Quote:

Command (m for help): p
Disk /dev/sda: 152.7 GiB, 163928604672 bytes, 320173056 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x31f29db2

Device     Boot  Start       End   Sectors   Size Id Type
/dev/sda1            1    289169    289169 141.2M 83 Linux
/dev/sda2       289170    337364     48195  23.5M 83 Linux
/dev/sda3       337365    369494     32130  15.7M 83 Linux
/dev/sda4       369495 320173055 319803561 152.5G  5 Extended
/dev/sda5       371543    660712    289170 141.2M 83 Linux
/dev/sda6       662761 320173055 319510295 152.4G 83 Linux


Previously, when changing the size of partitions on my RPi, after creating them with fdisk, the procedure was to use a program called resize2fs.  After rebooting, I tried this, even though I don't have a clue of what this program does.  It didn't work.  Both before and after using it, my RPi would only recognize sda1, sda2, and sda3, even though as you see above, fdisk sees 4,5, and 6.
   I tried to mount /dev/sda5 and others, but got errors, such as:

Quote:
root@raspberrypi:/mnt# mount /dev/sda5 /mnt/az5
mount: wrong fs type, bad option, bad superblock on /dev/sda5,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
root@raspberrypi:/mnt# dmesg |tail
....
....
....
[48588.975223] F2FS-fs (sda5): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[48588.975239] F2FS-fs (sda5): Can't find valid F2FS filesystem in 1th superblock
[48588.975257] F2FS-fs (sda5): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[48588.975271] F2FS-fs (sda5): Can't find valid F2FS filesystem in 2th superblock
root@raspberrypi:/mnt# fdisk /dev/sda



   If this were Windows, I would format the partitions, but I can't remember how to make a generic linux FS.
I think I've used mkfs, or it's more specific versions, like mkfs.ext2 before, but I can't remember if I was sucessful, plus I could never decide which FS would be best to use.  Since the FS reported for the other Azbox partitions are generic "linux", I was looking for that, but it's not one of the options.  I'm wondering if ext2 is equivalent to generic linux, if not, what is?
   I'm also thinking that perhaps I will try to just use dd to send an image of that 4th partition over to the new sda5 partition.  Can't do that for the 6th partition, but I assume ext2 would be OK for a storage partition.
 
In any event, the DOM is back in the Azbox, but I'm trying to get together a list of adapters to order to be able to mount a couple sd cards in place of the DOM.  I've found a nice CF adapter for 40 pin IDE that will take 2 cards, but I'd really prefer to use SD cards, and small SD card adapters adapt to 44 pin IDE.  I do have a few 44pin-to-40pin adapters, but that sounds messy. a hard drive cable with connectors for 2 44 pin drives would be nice, but I've only found cables with space for one 44 pin drive.  I'm sure I'll find something.



wejones

Avatar / Picture

Registered:
Posts: 5,641
Reply with quote  #21 
Well, I used the dd command to copy an image of the hda4 partition on the Azbox over to the sda5 partition on the hard drive.  Then I used the mkfs.ext2 to format the sda6 partition.
   It seemed to work.  Now, at least while attached to the RPi, the RPi recognizes all 5 partitions, and I can read and write to/from them.
  Next step is to see if the Azbox can find it's 4th partition, which is now in the 5th partition.  If not, it was an interesting try. 



EDIT:  Well, it looks like the Azbox couldn't find it's partition 4 in the extended partition 5 position. I put the hard disk back in the Azbox.  At first, it was stuck on booting as before, but then, once again, I reversed the power plug, and it went from booting to checking, for a long time, then it came back with the menu telling me that the last update failed, and asked me whether the patch file was on USB or if I wanted to update by internet, etc.  So I'm pretty sure that this means that it couldn't find that partition, which just happens to be the partition where the patch file is stored.
So I'm guessing that I'll need to have 2 drives for this to work right.  But I'm real confused re how the other people got it to work.  Ie maybe they found another workaround whereby the Azbox could be tricked into storing recordings on that 4th partition, ie the /Download directory??

Anyway, back to running off the DOM again for now.


wejones

Avatar / Picture

Registered:
Posts: 5,641
Reply with quote  #22 
Quote:
Originally Posted by wejones
  ......
In any event, the DOM is back in the Azbox, but I'm trying to get together a list of adapters to order to be able to mount a couple sd cards in place of the DOM.  I've found a nice CF adapter for 40 pin IDE that will take 2 cards, but I'd really prefer to use SD cards, and small SD card adapters adapt to 44 pin IDE.  I do have a few 44pin-to-40pin adapters, but that sounds messy. a hard drive cable with connectors for 2 44 pin drives would be nice, but I've only found cables with space for one 44 pin drive.  I'm sure I'll find something.





I'm still tearing my hair out on this experiment, and I don't have that much hair left.

I ordered a couple adapters that sounded like they should work.
(1) I ordered a ribbon cable that was 40 pin where it plugs into the Azbox, and 44 pin so that it can accept a laptop style hard disk.
   Then I found and ordered two gadgets with 44 pin IDE connections to plug into the ribbon cable, but are adapters so that either
(2) an SD card (in one case)
or
(3) 2 CF cards (in the 2nd case)
will plug into it.
(4)  I then found, and ordered 2 CF card adapters that an SD card will plug into item (3).
I already had 40 pin IDE cables, 44 pin to 40 pin IDE adapters, an SD card to USB adapter, and an IDE to USB adapter.

I've attached photos of the above adapters.  First, item (2) plugged into cable (1).  Second, item (3) plugged into cable (1).  Third item (2) plugged into a 40 pin cable via an adapter. Fourth, item (3) plugged into a 40 pin cable via an adapter.  Finally fifth, an IDE to USB adapter used to test adapters 2 and 3, and a SD to USB adapter used to both program the SD cards with the Azbox file system, and to test the SD cards after programming.

I used dd to create an image of the DOM and then plugged the SD card in the SD-USB adapter into my RPi to copy the image onto the SD card.  I verified that the file structure was sucessfully copied to the SD card while still in the SD-USB adapter, and then later when plugged into the 44 pin IDE adapter, both when plugged into the RPi. 

   I then tried all 4 configurations shown in the first 4 photos while plugged into the Azbox.
      None of the configurations worked.
  In each case I eventually got an error saying that there was no disk.  Ie the Azbox didn't seem to detect the SD card.
    I noticed that when connected to the Azbox by either of the 4 configurations, that the SD adapters did not light up confirming power unless external power was connected to the power plug on the cable.   However, when connected to either PC or RPi, both adapters would light up confirming that they were being powered over the connection, without any external power. So for some reason, the Azbox drive connector doesn't provide power to the adapters.  This was expected when attached to the 40 pin cable, but I didn't expect it when connected to the 44 pin cable, however I guess it makes sense because my IDE to USB adapter apparently inserts the external power from the USB connection.
   The single SD card to 44 pin IDE adapter was recognized by both PC and RPi regardless of what file systems were on the SD cards.  The dual CF/SD card to 44 pin IDE adapter, however was not recognized when the Azbox linux file system SD card was in the Master slot, but WAS recognized when a FAT-32 formatted SD card was in the Master slot.
   Anyway, since neither of the 4 configurations worked, even with external power applied, it appeared that these adapters must be windows compatable, but not Linux compatable, or more specifically, it must not understand the ext2 or ext3 file system. So I started experimenting with the adapters both with my PC and with the RPi. 
   What I found was very confusing.  First, I found that I was wrong relative to the adapters not being Linux compatable, because i tried both adapters with a variety of SD cards, and found that the adapters worked perfectly with some cards, and didn't work with other cards.  All cards worked when plugged into my SD card to USB adapter. 
   I was happy to see that the dual CF card adapter worked fine, when there was an old RPi system SD in the Master slot, and an empty fat32 formatted card in the slave slot. It showed the two slots as separate SDA and SDB devices in the RPi.   It also worked when the two CF adapters were reversed in the 2 slots.  But it didn't work when a working fat memory card from a camera was tried, and most importantly, it didn't work when my new Azbox file system card was tried. 
   There is just something about the SD card with the Azbox data on it that the adapters didn't like.
Right now, I'm very confused.  The only thing I can think of right now is that the file system is on an older small 1 GB micro SD card plugged into a regular SD adapter.  The PC and RPi did recognize the same SD adapter with a 32 GB HC type micro SD card in it. 
    I think I'll try putting the Azbox file system on a 16GB HC micro SD card that I have.  I didn't want to waste a 16 GB SD card for 250K of data, which is why I used the older 1GB card, but that's the only thing I can think of for a reason that this card doesn't seem to be recognized properly. 

   Anyway, I'm still plugging away at this.  I really wish that these SD card adapters could be powered by the Azbox so I wouldn't need external power though. 

EDIT: Forgot to update this with the fact that I tried putting the file system on a newer HC SD card, but it still didn't work.  I think next step is for me to order yet another adapter, ie 40 pin to SD, instead of going through 40 pin to 44 pin adapters.

Attached Images
Click image for larger version - Name: 05-44mono_0716.JPG, Views: 59, Size: 233.78 KB  Click image for larger version - Name: 03-44-duo_0717.JPG, Views: 57, Size: 216.99 KB  Click image for larger version - Name: 04-40mono_0715.JPG, Views: 50, Size: 218.67 KB  Click image for larger version - Name: 02-40duo_0718.JPG, Views: 46, Size: 198.94 KB  Click image for larger version - Name: 01-pcadap_0721.JPG, Views: 45, Size: 215.30 KB 

merkin

Registered:
Posts: 770
Reply with quote  #23 
i havent been following the thread..what are you trying to accomplish?
wejones

Avatar / Picture

Registered:
Posts: 5,641
Reply with quote  #24 
Quote:
Originally Posted by merkin
i havent been following the thread..what are you trying to accomplish?


Basically,   50% just experimenting,  trying to see if I can get this to work with solid state device like CF or SD cards instead of actual hard disks.  The other 50% was that if it does work, it would turn my Elite into a Premium, allowing me to record directly to the solid state device without going through the slow USB port. This may not help with recording though, as I've read that the Azbox has built in speed limits for any recording process.  Not sure if that's true or not.

Also, going through the process has given me an image of the Azbox file system, so if my DOM gets corrupted, I can burn it back onto another DOM. 

   I know this can be done with hard disks, but all the problems I've been running into have now turned this into 100% that I'm determined to figure out why what I'm doing doesn't work.  In the process, I've learned a lot about how these imbedded systems work, compared to normal Linux systems, a lot about partitioning, and I'm finding out that there is a lot that I don't understand about these various adapters.   Also have gotten frustrated by the 40 and 44 pin connectors, some of which have pin 20 blocked, others that don't.  Ie had to bend the pin 20 back out of the way to get some to connect, and on others had to be VERY careful to not reverse the orientation of the plugs, since the pins are often not numbered.
   Anyway, it's just been a fun experiment, but getting frustrating that I haven't figured it out.

  I'm still very confused re whether I need that pin 20 or not.  There is something very different about how those adapters get power vs how the DOM gets powered.

mr3p

Registered:
Posts: 119
Reply with quote  #25 

I'm 6 months late on your experimenting but I found a couple of oddities regarding replacing the DOM as well.   Inserting an IDE to SATA adapter in the DOM IDE socket did not allow me to connect a 250GB SATA hard drive which I found perplexing.  I then plugged in a SATA to IDE adapter which initially didn't work either using the default "SATA to IDE" jumper setting however switching the jumper to "IDE to SATA" allowed the drive to be recognized and allow install of OFW or OpenATV.   Is it possible the "direction" of your adapters is why they aren't working?    My initial thought was to use a CF card with adapter as you attempted however decided I was better off just getting a new DOM which hopefully will arrive shortly.    


wejones

Avatar / Picture

Registered:
Posts: 5,641
Reply with quote  #26 
Quote:
Originally Posted by mr3p

I'm 6 months late on your experimenting but I found a couple of oddities regarding replacing the DOM as well.   Inserting an IDE to SATA adapter in the DOM IDE socket did not allow me to connect a 250GB SATA hard drive which I found perplexing.  I then plugged in a SATA to IDE adapter which initially didn't work either using the default "SATA to IDE" jumper setting however switching the jumper to "IDE to SATA" allowed the drive to be recognized and allow install of OFW or OpenATV.   Is it possible the "direction" of your adapters is why they aren't working?    My initial thought was to use a CF card with adapter as you attempted however decided I was better off just getting a new DOM which hopefully will arrive shortly.    



Re is the direction of the adapters the cause of the issue, that's an interesting idea.  I don't think so, but it's been so long since i tried this, that it's taking me a while to remember what's going on.  I did put everything in a box, hoping to get back to it, and I'm staring at all the adapters now.
  I really think my problem had something to do with getting power to the little CF or SD cards.  I think that the Azbox must be sending power out pin 20 of the 40 pin IDE socket, but my adapters that hold the CF or SD cards are 44 pin, so I have to use cable adapters that allow power to be inserted into pins 41-44 of the 44 pin devices.  It seems like this should work, particularly because my USB<-->IDE adapter works with the CF/SD adapters even though pin 20 is blocked.  But for some reason it doesn't work with the Azbox.  I was almost wondering if the Azbox uses current through pin 20 to determine if there is a card installed, except that real hard disks work even though pin 20 is blocked.  So I am still real confused. 
    Since I have my box of parts out though, I will probably take another stab at this.
   I am confused about what you say above though..... are you saying that you installed OFW or OpenATV on the Azbox?  While I'm not sure what they are, I assume that they'd have to be compiled for the Azbox hardware, but I didn't think you could compile on the Azbox?  Anyway, I'm confused what you did. 

mr3p

Registered:
Posts: 119
Reply with quote  #27 
OFW = AZbox original firmware.   I've been using last version released, azbox-0.9.5402-patch.bin

OpenATV =  E2 builds which support all AZbox HD models.    Nightlies are available here.    My receiver is still open while I await larger/faster DOM which was supposed to arrive today [frown]    I'm not sure if it will have any impact on performance given the the limitation of the IDE interface although the new DOM is probably 5-8x faster than factory module, similarly priced to CF with no adapter required.    Hopefully it will work.
wejones

Avatar / Picture

Registered:
Posts: 5,641
Reply with quote  #28 
Oh, OK.  Thanks for reminding me what OpenATV was.  I think there was another thread about recovering from that about 2 years ago.  I forgot about that.
mr3p

Registered:
Posts: 119
Reply with quote  #29 
I know you were focused on get the CF cards to work but the simplest solution for larger DOM is to plug in an IDE hard drive and pull power from the SATA cable with an adapter to 4 pin Molex.   In my experimenting last weekend I installed factory firmware on a 500GB IDE drive.
wejones

Avatar / Picture

Registered:
Posts: 5,641
Reply with quote  #30 
Yes, using a hard drive worked fine for me.  I plugged in a blank hard drive in place of the DOM, and loaded the firmware from a thumbdrive.   I've been trying to get CF or SD cards to work so that I could perhaps fit everything inside the Azbox case, since it's kind of messy having a couple hard drives and power supplies sitting on top of an Azbox.  My main goal, besides just trying to learn how this stuff works, is that if I could get this to work, would be to convert my Elite into a Premium, so that I could record onto a 2nd drive, since recording via the USB port has never worked very well for me.
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.

Fellow Members, your posts are welcome here! Do not worry about posting everything perfect. Different receivers and LNB's will give you different Frequencies and Symbol Rates. Some set top boxes, PCI cards and USB receivers, Do Not Require all of the same information that others may need. It is not Required to post everything that others may need to tune in a feed. It is just most important to share the find. We can always adjust the Frequency and Symbol Rates and try the various Modulations and FEC's on our own receivers until we get a lock and then give a polite reply with what works for your receiver, as that information might help others as well. We all appreciate the efforts and energy of the Posters!

Thank You for Visiting GOFASTMOTORSPORTS.com - Keep Your Eyes on the Sky and the Track!