Jump to content

stryd_one

Frequent Writer
  • Posts

    8,840
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by stryd_one

  1. Thanks mate you're very kind! Here are the quantities for the order: 3FTL6 300 (Standard 3F Thruhole, no LED) 3FTL6-Q 1300 (Quiet 3F Thruhole, no LED) 1D.16 800 (Translucent white) 1E.09.6 800 (Black with translucent window) 1E.03.6 350 (Grey with translucent window) 1S11.16.0 700 (Clear round)
  2. Correct, it's E(nable) not C(hip)S(elect)
  3. Yummmmm. Roo is a tasty animal. I like mine thick cut rump, medium rare with cracked pepper and cherry tomatos. Eat enough of it and you begin to smell like it. We call it being "of the wallaby".
  4. Organic rosin fumes ain't so great either...
  5. IIRC the ST vregs are also the ones that tend to be problematic, and/or the optos... ?
  6. Try virtualbox buddy. Just mount up the ISO file and run the installer as though it's a separate PC. Did you ensure you're runninng the latest BIOS versions on those machines? Check the BIOS config at boot time to see if it's an option? I had to do both..... Being as how the thing's connected to a PCI peripheral you might need to do something fancy with the card to enable booting from it...
  7. @anyone who doesn't know: You could electrocute or burn yourself rather badly doing this. Don't try this at home, kids.
  8. You're both wrong, they'll all be working 100% fine. And stolen when you go to buy a beer.
  9. You want Microchip PIC16 ASM, aka PIC ASM. I think that's not the right page for you :( Try piclist.com , that's always a good starting point. Also be sure to get the datasheet like I said. That's where it's all explained.
  10. Hah! I hang back cause I was going to see if you and Wilba wanted in.... Snooze, you lose!
  11. If it's old and crusty: Dremel.
  12. Nope. Try erasing your cache and cookies and restarting your browser.
  13. Keep in mind that the 1E and 1D caps I've listed here are not standard 1E/1D caps, the translucent white led hole is custom run... So it's not a massive difference... But those are really good prices on the switch and the 1S, normally they don't come that cheap even in bulk through a retailer with stock! If anyone overseas would be willing to fire off an email to their local distributor that would be great, but keep in mind that if we ship the full order to australia it will incur customs duties and that will sting. If we get them from overseas, we'll need someone overseas to break the order up and spread it around.
  14. Hi all, I got final pricing on these, and it's pretty much the same as I posted before. Alas I don't have a few grand lying around, so I'll have to take payment in advance, and there could be a significant lead time - I was told it's up to 12 weeks (we'll only know for sure after the order is placed). Also, the clicky version are only 10c cheaper than the custom silent ones, which is pretty expensive compared to retail I've seen... Kinda makes me wonder if I should try another distributor, but the one I've spoken to is the only one local to me... Sorry there's not much happy news happening there guys. Have a think about it all, and I'll post again soon with the exact pricing, and a wiki page to take firm orders.
  15. Darn right. MMA especially spent a rediculous amount of time, and explained lots of little details to me. He was freakin awesome, super patient - and knows a f#load about it all. What he told us enabled nils and I to take that info away and mull it over, apply our local knowledge of midibox, and come up with a solid gameplan, rather than something based on guesswork or blind faith. Yeh, there are instructions on modding up an existing installer and it's not tooo rough, but to do what we want, and keep it legal, means major changes, definitely way out of our scope.
  16. Noooooo man you're doing a goodthing. You're having some troubles because youre on the leading edge of this - guys at the frontline catch all the bullets. nILS and I and cimo had our share of worries too. but every one we run into we learn how we screwed up so we can avoid it next time. Well, no - you can boot to the CD and save the persistent data on your USB stick :) Also, you can put the grub bootloader on the hard drive so it can boot to there, and then continue on to boot windows, or your USB stick. The error message youre getting doesn't actually imply that it won't boot from USB - in fact it may well imply that it *will* boot from USB, but that the thing it's trying to boot isn't carrying a boot system. Try those pendrivelinux instructions, I think you'll get a pleasant surprise ;) As for virtualisation, I've been running ubuntu in a virtualbox machine on my laptop this week for packaging practice, works nicely!
  17. nils' script is an automated version of that document frailn linked. It's not a full install, but it does include everything: it's a persistent live install. that means it's still a 'live' boot, so it works on different hardware, but it also retains your changes for the next boot. A full install doesn't load all the hardware drivers, so it only works where you install it, but it's faster to boot. lyle: it appears that the bootloader isn't able to find the disk. That's something that can be avoided by following certain setup procedures, and it can be fixed but seeing as you haven't used this installation yet, i'd just nuke it and start afresh. heads up: nils' script does the partitioning on your drive for you. Use it with care :) Yes. Hey, if windows can get all the drivers on one disk why can't we? ;) All of the above examples are already supported in ubuntu, except firewire audio support which is part of a package that's already in our list. As for delivery of future drivers, we may need to borrow your time machine for that ;) Seriously though, most drivers will be released in the ubuntu distro anyway, and those that are reeded can be downloaded from the repositories. The reason we've gone with ubuntu is because it has excellent hardware support right out of the box. That was the most important milestone of all. Could be a problem... If the noise about this gets too heavy I'm sure we could work something out, like a new forum category as you mentioned. Sure, that's why its so great that so many people are getting involved now at this pioneering stage. As lyle has discovered, it's not always straightforward when you have no prepared documentation and automated procedures, but after a time this will become a lot easier. For example, the upcoming ubuntu release will (I have heard) be distributed not only as CD ISO images but also in images ready to write to a USB stick. Another example is the above procedure, which is an unfortunate outcome of a bug that slipped through into the release - intrepid will not have all that messing around to do, the graphical menus will work fine. Update: I had a four hour conversation with the ubuntu studio devs, who are fucking awesome, thankyou MMA and co! They cleared up a LOT of questions and really laid the options out for us. In fact, they tried to talk us out of a live disk saying it would not be worth it, and for different reasons than perhaps intended, I believe they were right, but I'll come back to that. It narrows down to this: Due to legal restrictions , we will not be able to distribute a modified ubuntu image. This means the end user will have to download the ubuntu ISO from ubuntu (or torrent etc) and get our modifications separately. That leaves us with the following options: 'Full' Install to writeable media (internal HDD, USB HDD, USB flash, etc) + Install packages from our repo* This is what you'd normally do for a non-portable setup anyway. Sweet 'Live' & Persistent install to writeable media (USB HDD, USB flash, etc) + Install packages from our repo* This would be normal for a portable setup. All good. 'Live' & NOT Persistent install to read-only media (CD/DVD, or also USB HDD, USB flash, etc) + Install packages from our repo* This introduces the problem - the installed software, and any other changes you make, will be lost when you boot. That means every boot will take maybe half an hour to do all the installs * That's a super-simple one-step procedure. Can be installed from a downloaded image, or online. This can be worked around by pre-installing the packages to the bootable CD image, but that means that the end user has to download ubuntu, boot to it, do some procedure (maybe scripted, but still....) and then save the image and burn it, to have a live CD. It's not al that hard, but it's not very "nice" for newbies I'd say. So here's the question: Is it worth it? We all jumped at the initial thought of being able to whack a CD in and go, but there are two new considerations: The added procedure to create the disk after downloading, and.... Would someone actually use something like that so often? I mean, think if it in a real-world example: Is the newbie going to boot, download the mios app, edit the files, compile, debug, compile debug, etc, upload, all in one session? Unlikely. Plus, what abou next time? They havo te go through all that hassle all over again. ugh! Given that a USB stick with plenty of space is only 10-20$... maybe persistent live or full install should be the default, and non-persistent live CDs should not be initially supported? I say "initially" because it's going to work out that way, anyway. The first step here will be to package up everything we need, and setup a repository. That repo will enable existing ubuntu installations and new full installations and persistent live installations to get setup easily, and will form the building blocks of anything that would follow from there.
  18. Yeh that was just a hack to make it work in the meantime - the next step is to fix it up so it uses the new structure completely and the j5io module can be used again :) Although, the whole module is not really needed, and the init functions can be 'borrowed' and they are portable to both ADC variants.
  19. I meant, blog it: http://www.midibox.org/ Or maybe wait till it's 100% ;) But it's sure getting there!!
  20. No, but you can learn it in reverse.... Write some simple C code and compile it, and look in the _output directory to see what the ASM looks like. The comments contain your original code. Use that in conjunction with the instruction set in the datasheet and it will help you to relate ASM to C :)
  21. haaaaaapppy birthday to ya haaaaaapppy biiirthday to ya haappy biiiirth daay My gift to you all: I will stop singing now.
  22. stryd_one

    DOG LCDs

    Ahh I do love these! Has anyone ever asked if they can do a run of 20 character displays? maybe we would be lucky :) Edit: nILS you shoulda just asked, I had a driver half written about two years ago when smash put me onto these :) It's just the 16 char thing that stopped me.... darnit :(
  23. dstamand you've got problems, and a few bits of round plastic are the very least of them
×
×
  • Create New...