Neuros Technology Forums

quote:Originally posted by Scanman

It is a standard Laptop 2.5 inch drive.  The drive that comes with the 442 is a Seagate Momentus OEM drive at 4800 rpm.  I got a new Seagate Momentus, 100gb 5400 rpm drive.  the power specs were identical, so I was not worried about battery life.  This drive has less vibration than the original, so that's a bonus.

Last night I copied about 30gb of TV to it from my MythTV box and charged it.  I am sitting here at work and it is just running through videos, so far I am at 3 hours and only have lost one block on the battery meter.  Good enough for me. My longest airplane flight is 5 hours, so this is plenty for me.

Was it rocket science? No.  4 screws on the outside, 2 small ribbon cables ad the front comes off (needs a little prying, there are tabs on the top black piece that hold to the metal sides.  4 screws and another ribbon cable holdng the main board down.  4 screws holding the HD holder down to the back of the case...  Pop out the old, put the new one in, put everything back together.  The 442 even formatted the drive for me!!  I thought that was cool.  I had about 95gb of formatted space available.  Pretty straight forward and easy for someone comfortable opening small devices.

Can't complain.

Here's a link to the drive I bought:
http://www.amazon.com/gp/product/B0006FS268/sr=8-1/qid=1154096486/ref=pd_bbs_1/102-5368700-3229731?ie=UTF8

Link to some guy who opened his 442:
http://devices.natetrue.com/442dissection/

Not sure if you could use a notebook drive adapter to a full size drive or not??  I don't have any adapters, and really no reason to, so I will leave that up to someone else to figure out.[][]

Glad I did it... I can live with the quirks of this device. I wanted something simple that would play and record standard video files, and this does that very well. [][]

Thanks for the info on this!! I didn't have the balls to try it myself. Since it worked for you I picked 2 120GB Seagate hard drives and replaced the one in my 442 and the other in N2. So far they both appear to be functioning normally. The N2 worried me but the unit formatted the new hard drive just fine. Needless to say...I'm fat, dumb, and happy!!

quote:Originally posted by peterskm

As for restoring playlists on DB rebuilds, you need to make sure you have the option selected to save playlists.
Options > Database > Save Playlists

This will create a playlists on your Neuros under /ndbm/playlists/.  When doign a rebuild, it will then read these in and recreate them in the neuros database.  I have been doing this for at least a year and have had no problems.  In fact, I only use NDBM for doing rebuilds.

I do the same thing. Everytime I add tracks I just do a rebuild. The problem is that I now have about 11,795 tracks and when I do a rebuild it freezes when during the "Writing Database" phase. I have to manually close that dialog box. The database is functional and I can play all tracks (as far as I know), it just doesn't load the playlist back in.

FYI - I usually delete the woid_db directory prior to rebuild so I don't have to wait for NDBM to read the database, it automatically starts the rebuild after checking for updates. I have tried it both ways (with and without the directory) and it still freezes.

When I move tracks off my Neuros and bring the track count to just over 11,000 then I have no problems rebuilding and it's re-creates the playlists without issue.

To me it seems like something can't handle the number of tracks (be it the database or NDBM itself)....just my thoughts.

quote:Originally posted by rocketman768

So, I decided to add a feature to NDBM, but I am unfamiliar with creating forks in development with CVS and all. I have so far added an "Import Playlist" feature to NDBM that acts just like the one in NSM, which was one of the most requested features, but I am unsure of how to get it to the rest of the world. Is anyone even alive on this project and do people care?

I'm not on the project but I care. NDBM seems to keep freezing up on me when I rebuild the database. It successfully copies the DB but unforutnately doesn't include any old playlists so I would have to recreate them everytime. I'm not real interested in doing that everytime but if they could be imported then I could just synchronize afterwards and be good to go.

quote:Originally posted by meest

11,000 MP3's Already have them loaded on the N2 80gig. Using USB2.0

It takes FOREVER TO SYNC! I'm talking about 45-1 hour of syncing.... Maybe I'm thinking of sync'ing to be the wrong thing. Even when i don't change anything except tell the neuros to delete some songs off of it and the database next sync... it takes forever to delete.... ARG!

maybe i'm missing something in NDBM or something but i just want to be able to have it scan for new music that i've put on my computer since last sync. and then add that music... Why can i not find this? Is this simple option not even available?

If i rip 2 CD's then want to sync them i don't want to have to dig through all my folders to add them....

I'm in the same boat (80 Gig / 10500 songs) it only takes about 15-20 min to sync up.

I manually add or delete albums (via windows explorer) onto the hard drive and then use NDBM to rebuild the database. Works like a champ as long as no other resource-intensive applications are running.

I actually didn't have any problems with the progress bar but the memory bar wasn't accurately reporting how much room was being used. That seems to be working correctly now...for what its worth.

Well it helped but definitely didn't fix it...specifically I:

1. Revived the bad blocks.
2. Formatted the NAND Disc.
3. Formatted the Hard Disc.
4. Formatted the Media File System.
5. Copied all my music back onto the backpack.

It happens more often while using Neurocast but it seems to have helped some while using the headphone jack. It's not totally gone but it has helped some, thanks.

All my files are encoded at Q6 and I still get an irregular periodic pause/hesitation/skip whatever you'd like to call it. I agree that I think everyone is just putting up with it in the hopes that it'll get fixed with the next firmware release. That's what I'm doing anyway...