Organizing project folders

Hi
While developing large Flex projects, I often find myself wanting to organize the project folders so that everything is neat and logical.
One of my main concerns in doing so was that the bin-release folder had only whatever necessary items there were to run the project, and nothing extra. Therefore, I found I should place any assets loaded at compile time NOT in the src folder, but in a separate folder somewhere outside the src (any non-code files in src or subfolders seem to be exported in the bin-release).
This raised one minor issue: Whenever I embed something into my code, using @Embed directives, I need to specifiy the location starting with "../", as to get out of the default src folder. I really hate this, for one it reminds me I could always use "../../" to look for stuff even outside the whole project folder, which is ugly to do; plus I think "../" is bad practice in any code and should always be worked around.
What I would prefer is a way to mark folders as being part of the compile-time library path, but not to be exported in the bin-release. Is there such an option in Flash Builder? I needn't mention I prefer not to delete the assets from the bin-release folder myself.
Thanks,
Liviu

asuch:
Terence may have a good idea there about replacing the alias files with the original "source" files. I'd do it for one small roll first to see if it will work satisfactorily. If so then proceed folder by folder, checking as you go along.
The fact that the source file does not get deleted when you delete in iPhoto is one of the caveats of that system. One way to find and delete the source file before deleting from iPhoto is to Control-click on the thumbnail and select Show File or Show Original File if it's been edited. That will take you to that file already selected in the Finder and all you'll need to do is type CommandShiftDelete to move it to the Trash. Then go back to iPhoto and delete it from the library.
I suppose an Applescript could be written to do that from iPhoto. If you want to keep the alias system ask in the Applescript forum if anyone has one or can write one.
If you keep that system you might get some helpful tips from my Tutorials that I've written. The are primarily for converting to one but there may be something that will be of interest.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
G5 Dual Core 2GHz, 2G RAM, 250G HD; G4 Dual 1Ghz, 1.5G RAM, 80G HD,   Mac OS X (10.4.8)   QT 7.1.3, 22 LCD, 200 & 160G FW HDs, Canon S400, i850 & LIDE 50, Epson R200

Similar Messages

  • Organizing with Folders vs Projects vs Albums vs Stacked Photos

    Question - Longtime Apple user, but relatively new to Aperture. Working on organizing a large collection of photographs, and am debating whether to organize by Project and grouping similar Projects into folders, or whether to use Projects as my major subdivisions, and organizing within projects using Albums or Stacks.
    I realize that there's probably no right answer, so I'm hoping that anybody reading this note could take a quick minute to share the philosophy they apply to organization, as well as any concrete advantages or drawbacks to Projects, Folders, Albums, or their own method.
    Thanks for sharing!
    Mark

    Projects are, imho, badly misnamed. Aperture was designed with the general plan that one shoot would be one Project. Projects have one salient characteristic (which separates them from other ways of grouping images) -- each Master must be in a Project, and can be in only one Project. Because of the above, you should conceive of Projects as the master (small "m") and enduring holding bin of your shots. I think of them as boxes, or as binders ("binders" implying, somehow, something more long-term than "album").
    However you end up organizing your collection in Aperture, the one method I recommend against is using Projects as your major subdivisions. They weren't designed to be used this way, they shouldn't have more than a few hundred Masters in them, and you are likely to outgrow that system of organization.
    I stick with "one shoot = one Project". If I have three separate shoots on one card, I import the files in three separate sets, each with the Masters specially re-named, into three separate Projects. I then use folders to organize my Projects. I use Albums for sub-sets of Projects with more than 60 or so images -- I do a lot of my processing by Project, and I find 60 images is about the most I can easily handle at once. I use Albums also for actual projects (small "p") -- e.g.: a series of cards for sale, or work for a client.
    All images are keyworded (again, a per-Project task). I use color labels to indicate the level of development of an image. I use stars to indicate the value of an image (rejected, not yet rated, best of stack, worth keeping, among the best in Project, worth publishing, excellent).
    Keywords, color labels, ratings, and Project names give me enormous specificity in creating Smart Albums, which I do extensively.
    Additionally, I do three things which I think are uncommon.
    . I move my Projects according to the status of their development, and
    . I separate my intake, storage, and processing areas from my output areas, and
    . I never use Folders to organize by date.
    I do this because for me Aperture's two overall functions are best treated separately. Those two overall functions are, generally, Intake and Output, or to be more specific, "Import, Develop, and Store" and "Gather for export, Prepare for publication, and Export". The top-level folders in my Library are
    . Administration Smart Albums
    . Raw (inputs)
    . Cold Storage
    . To Serve
    Admin Smarties includes "5-stars", "Managed Masters older than 45 days", "Masters Missing", "Printed 17x22", "Re-take", and the like.
    "Raw" is the top-level of a folder tree which includes "Just Imported", "Described not Stacked", "Stacked not Keyworded", "Keyworded not Picked", and "Picked not filed". I move my Projects into the appropriate folder. Note that this works well in Projects view -- one can drill down to any level of the Library tree and see at a glance which Projects are where.
    "Cold Storage" is where I put all fully-processed Projects (and remember, for me "Project" just means "Shoot" -- if you ever used a non-digital camera, same as a box of slides or a sleeve of photos). I organize these as I see fit. I try to put Projects where I think I will look for them. Clients have their own folder(s). Other photographers have their own folders. On the personal side, I have folders for Portraits of friends, Family, Events, Trips, Indoors, Urban outdoors, Rural outdoors, Close-ups, Test shots, etc. Each of these is further subdivided. I have an entire folder sub-branch just for fine art still-lifes.
    The last of the top-level folders holds a large sub-set of folders for output. None of these folders have Projects in them (Projects, for me, are +storage containers+, not output containers). I create a folder for each output project (small "p"), and use Albums as needed. In theory, every image that shows in the output side of my Aperture structure should already have been selected ("picked") and optimally developed as an image (the rating and label tell me the status of the image). What is left for me to do is final selection, pre-press, and export.
    No where in my Library structure is any accommodation made to date (other than the "one shoot = one Project rule). The is no reason to organize an Aperture Library by date -- date organization is hard-coded into Aperture at both the Project and the Image level. Since it is already hard-coded into Aperture, I prefer to use the Library organization tools to create a storage and output structure which gives me a level of utility on top of date organization.
    In general, I keep my Projects view (the Viewer, not the Inspector) grouped by Library folders and sorted by date (most recent first). If I want to view all my shoots (Projects) by date, I simply ungroup them in Project view. If I want to view them by year, I click the "Year" grouping icon. I find Project view, and the built-in grouping options, quite useful.
    When I need to view all of my photos in date order I simply use "Photos" view. Note the sophisticated filtering options available using the "Date" and "Calendar" rules. In general, I set Photos view to sort by either "Import Session" or "Date -- Descending". I regularly use List view when in Photos view.
    I complete my set-up with specific file-naming and Project-naming conventions. The important thing here is consistency -- set it up right from the get-go, and stick to it rigorously, and you won't have to second-guess your searches or filters.
    Hope that helps. It's a lot of overhead -- but I have and take a lot of shots, I work in spurts, and I valued a system which would let me start and stop at nearly any time and always let me know +by structure+ the status of any shot or image or Project or project -- while remaining flexible and expandable.
    My example should at least give you some ropes to use as you simultaneously shape and climb your Aperture mountain. I strongly recommend setting up a practice Library using, say, 10% of your images, and using to for a couple of weeks, tweaking it as you go, before "casting it in stone" and importing your entire collection. Aperture is broad and powerful -- take the time to know and understand it, and you will find your use of it immensely rewarding.
    Good luck.

  • Organizing for stock library. Projects, folders or albums?

    This may have been talked about to death, but I cannot find a thread that fits my question.
    I have a growing library of images in Aperture. I am also a stock photographer by living. My library in Aperture is somewhat haphazard and I'm trying to organize it so that I can have it make sense. I do not sell my photos as stock myself (I submit to several agencies) so I'm not sure that I need to file my images so that I can get to them if a client needs a shot. That's what the agencies are for.
    My work flow is something like this:
    1 - shoot pix
    2 - import and edit (read: delete) images in Aperture
    3 - prepare and submit images to agencies
    4 - next....
    I do find myself taking pix of many of the same subjects, so I do want to organize them in Aperture.
    My main question is, what is the best, or most efficient, way to organize major subjects in the library, with Projects, Folders, or Albums?
    For instance, I shoot a production with models. That could be a project titled " August 14 production." When the submission is done, i could archive the entire project to save space. But, suppose I want to keep some around to submit to a different agency. Is a project the best way to store this?
    Also, I find myself shooting a lot of NYC landmarks. Should each landmark be in its own project, or have it be an album in a project called NYC, or should it be a project in a folder called NYC?
    I'm really not sure what the most efficient filing method is for my business.
    Any discussion and/or advice is GREATLY APPRECIATED!
    Antonio

    gustavus:
    n attempting to relocate a folder it did not end up where intended and I cannot find it.
    I hope you are referring to doing the relocation from within iPhoto and not in the Finder and the library package. Any moving, renaming of files and/or folder inside the iPhoto Library Package while in the Finder is tantamount to the cardinal sin of iPhoto, Don't tamper with files in the iPhoto Library folder from the Finder. That will mess up your library to where you may have to start over with a new library.
    Can you describe where these folders and albums were located when you were moving them?
    Do you Twango?
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • Project Manager screws up well organized project

    Take a completed PP project nicely organized with folders for content (sequences, clips,  audio, ae, graphics,etc). Use Project Manager to trim size so it can be archived for future use at a WAY smaller size then the original (which has lots of unused media in it).Reopen a month later for client changes.The folder that PM created is a bloody mess, because in just  takes all clips and dumps them in 1 folder during the trimming process. Very sloppy and unprofessional.

    I realize what you mean. I was simply saying that maintaining folder structures and file names on your PC is the workaround I use. That way I only need the project/raw footage archived instead of my whole project. Since I keep all my elements in the same folders/structures no matter what. Then if one of my co-workers needs to edit something I worked on I simply give them my project file and since they have all the elements file names and folder structures the same as me.
    They simply re-link the raw footage by getting it off one of our network servers. Then they are ready to begin editing.
    Which allows you to also archive or re-edit old projects with ease compared to project manager being sloppy with all your stuff.
    However I totally agree it would be better if the project manager allowed you to do this to begin with. I realize project mananger slops everything into one giant mess.
    That is why I started doing it the way I mentioned. It's not a perfect solution but it beats using project manager in its current state.
    So I apologize if I came accross in the wrong way.

  • HT200183 If I wanted to include apple loops in the assets of Logic project folders that are part of a tutorial available for download on a paid educational website would that be ok?

    If I wanted to include apple loops in the assets of Logic project folders that are part of a song that follows a tutorial available for download on a paid educational website would that be ok? No one would be paying for the file itself that's part of the membership. I don't want to get into any copyright problems. I understand that they are royalty free and you can include them in your music no problem but the individual loops would be in the audio folder if I saved all the assets to the project file.
    Also, would it be ok to include screen shots I take myself of apple programs in my downloadable content?
    Just trying to figure out exactly how I should go about it to avoid any legal issues.

    Hi
    trainedmind wrote:
    No one would be paying for the file itself that's part of the membership. I don't want to get into any copyright problems.
    My gut reaction is that you may well run into © issues if you re-distribute the original AppleLoops.If your customers are paying for the training, they are also paying for the content you provide, so I feel that you would be re-selling the loops.
    Given that anyone who has a copy of Logic would likely have installed all the loop content, there should be no need to distribute them with the project files. Alternatively, make your own loops.
    CCT

  • I have 300 apps organized in folders on my ipod touch 4th gen, and connected my iphone 4, these apps have copied over but none have been placed in folders, any ideas how to replicate folders from ipod to iphone...?

    I have 300 apps organized in folders on my ipod touch 4th gen, and connected my iphone 4, these apps have copied over but none have been placed in folders, any ideas how to replicate folders from ipod to iphone...?

    What may work is to restore the iPhone fom the backup of the iPod.  However, if the two devices ahve different apps that come with the device, that may mess up some of the folders.

  • I use a browser application called Changepoint...a project time recording tool. It does not navigate to the project folders or interact at all using Firefox, only IE. What do I need to ask the tech team to troubleshoot why it doesn't work with Firefox?

    See question. I'm assuming that I or them are missing something with the handshake once the basic appl is launched. The Changepoint appl does launch in the browser...it just doesn't function when you get into it, e.g. clicking on a hyperlink on the screen doesn't launch a sub-appl/module to show project folders. It doesn't crash the browser or window, it just doesn't do anything.

    Check with Changepoint support and ask if that application is made to be compatible with Firefox, and which versions of Firefox it has been tested with.

  • Iphoto library transfer not organized in folders

    My Mac book pro HD was full and I wanted a larger 500GB HDD. I had Best Buy swap out the old drive for a new HDD.
    I needed to transfer my iphoto collection to my computer ( with the new high capacity HDD ). I used a adaptor to conncect the now externalized HDD to the mac book pro. It was recognized. I was able to then tranfer my photos from the library to the desktop of my mac book pro (all 12000 pictures and videos ). I then dragged this to iphotos and all 12000 pictures transferred sucessfully. The problem is that I had all of these pictures organized by folders with event names and dates. They did not transfer over like this. All 12000 came over into a single event folder arranged in random order.
    HELP! Is there a way to fix this. I need all of these 12000 pictures organized like they were ...in about 200 or so event folders.
    The externalized HDD is now unreadable! Dont know what happened to it but now when I connect it, the mac book does not recognize it and it is unreadable..maybe this can be fixed and it still has all of my folders on it with my pictures organized.
    I still have the photos sitting in my desk top as well ( from the original tranfer as I did save then to the desk top thankfully )
    Any advise is appreciated
    Thank you

    You do not provide details of how you transfered the iPhoto library - the correct way is
    Moving the iPhoto library is safe and simple - quit iPhoto and drag the iPhoto library intact as a single entity to the external drive - depress the option key and launch iPhoto using the "select library" option to point to the new location on the external drive - fully test it and then trash the old library on the internal drive (test one more time prior to emptying the trash)
    And be sure that the External drive is formatted Mac OS extended (journaled) (iPhoto does not work with drives with other formats) and that it is always available prior to launching iPhoto
    And backup soon and often - having your iPhoto library on an external drive is not a backup and if you are using Time Machine you need to check and be sure that TM is backing up your external drive
    You do not transfer photos and you do not import anything - just drag the iPhoto library package accross and open it with iPhoto
    LN

  • HT203167 Why do files that I have organized into folders not stay in their folders after closing and reopening iTunes? And Why does the renaming get undone? I do this in iTunes Media/ Music.

    Why do files that I have organized into folders not stay in their folders after closing and reopening iTunes? And Why does the renaming get undone? I do this in iTunes Media/ Music.

    I recently had to reinstall my software for a
    dell computer a dell latitude d 830, then after installing all of my software and such including itunes the player did well even record to disks with no problems now that my system has done alot of updating of system files....now the itunes does not burn to my cd...error message 2131 this time
    The 2131 usually indicates firmware needs to be updated on a drive.
    Head to your drivers and downloads page for your latitude at Dell, and check for updates to your firmware for your optical drives. If you're behind and you update, does that clear up the 2131?

  • Deleting Project Folders in X5

    Please Help.
    I'm using RH X5 with SVN as my source control software. I
    cannot delete top level project folders after I have created them.
    How can I delete them?
    Thank you.

    Thanks for your help. In another thread, Peter G. also
    suggested checking your local directory (outside of RH) to make
    sure there are no files in the folder you are trying to delete. To
    add, I found images that were still in the folder. I forgot to move
    them. Finally, Peter G. suggested to use the Unused Files report. I
    still have to try that.

  • Keeping Synced Backup of Library - In Project Folders

    Can't find a way to do this online - probably because I can't think of the right way to get any sensible results from a search.
    Basically, I have my Aperture library which is ~100GB (which is already backed up in a couple of places). I also want JPEG versions of everything in my library so I can keep a copy online (ideally via iDisk, part of MobileMe - but I can do that as a separate step if necessary), and want photos kept in their project folders.
    Any ideas how I can do that? Looks like i'll need a plugin or automator to do it, but there may be a function I've missed somewhere. Seems like it should be simple enough, but I'm struggling (bearing in mind I don't want a complete re-export each time, just export whatever was updated since the last export)...
    David

    Hi christian,
    For future reference, backup the entire iPhoto Library folder. You need all the data files in there for it to work correctly.
    For your situation now, there is no way to relink originals with the modified versions.
    You can manually go through the modified folder and see if you want the modified version of a photo instead of the original. If you do, drag the modified version into the same roll in the Originals folder and it will replace the original as they have the same name.
    Then create a new library and import just the Originals folder.

  • Are the iMovie Events and iMovie Projects folders needed?

    I'm using version 10.0.6 of iMovie and moved some of my projects to an external HD using File > Move Events to Library.  I noticed in my Movies folder in my home directory that the related project folders under iMovie Events and iMovie Projects weren't moved.  It seems that these are left over after upgrading iMovie and that it just uses the iMovie Library and iMovie Theater bundles.  Can the iMovie Events and iMovie Projects folders be safely deleted?

    Yes they can be deleted if you have moved all the projects you want to work further on to iMovie 10, have checked that they are working OK, and are happy with switching permanently to iMovie 10.  (There's no going back).
    On the other hand if you leave them you can still use the earlier version of iMovie.
    Geoff.

  • Portlet content organized with folders

    I would like to create a portlet that is similar in functionality to the Favorites portlet. I was able to do this using content areas and URL items in 9.1, but am unable to figure it out using 10g.
    Here's what I would like to do:
    Create a portlet that contains URLs, organized within folders. I want the folders to open up inside the same portlet (instead of opening a new page).
    I have been trying page groups, pages, subpages, categories - but cannot achieve the results I am looking for. Any suggestions? Thanks! -- Rhonda

    hi rhonda,
    do you want to display something like the browser favorites ?
    if yes i suggest to use an HTML portlet. save your favorites as html file and display it as an iFrame in the HTML portlet. this ensures that if you clicke a link it is displayed in the same portlet area.
    if misunderstood your requirements it would be great if you could describe in more detail what you are trying to achieve.
    regards,
    christian

  • FC Events & Projects folders on external HD, and some clips missing.

    Hello there,
    Searched for an answer, but nothing seems to be exactly my experience.
    To help my MBP perform better, I moved my FCP X "events" & "projects" folders to an external LaCie HD. Folks here say they should be at the "root". Unsure how to check that, but I do know they are at the lowest level of folder on the drive, with no other folders above them.
    Most clips show up in all the projects when FCP X is opened. But some don't; modifying event references with Inspector leads to the event not showing up at all, so I can't even move it to the top.
    Then tried to "import from camera" and open the LaCie drive as an archive. But when clicking on the proper event folder, the message appears, ""Intrvw-WendyEllen_20Jun11" contains unsupported media or has an invalid directory structure. Please choose a folder whose directory structure matches supported media."
    Original media files on HD are all still there from when I first imported into FCP X. Now the same files are duplicated in the FCP X "events" folder, which also got moved to the external HD. Choosing either folder gets the same message.
    According to the manual, the yellow alert triangle showing in the timeline means the event is missing.
    <complaint> FCP X isn't very intuitive or user friendly on directing it to see the proper files. If something is missing, why can't I just pick where FCP should look for those files? Why can't I recreate a new path to those files, of the original one was broken? I'm not keen on the Events & Projects folders _having_ to be _set in stone_ on the MBP's harddrive. Where those files lie should be a choice.</complaint>
    My system is 2.2GHz Intel Core i7, 8GB RAM w/ Mac OS X 10.6.8. 
    Please let me know what I'm missing that FCP can no longer find the proper files. I'm sure it's something super easy, too obvious to figure out. In fact, if there's a way to ditch the "events' folder altogether & just have FCP X pull/render from the external HD files all the time, I'd love to learn that solution.
    Thanks in advance!

    You are correct about root ... no other folders above the FCP X folders is the way it's supposed to be.  I noticed that FCP X can get confused if you first opened up or created a project with the Final Cut Pro folders on your system drive then you try to make a copy of them on an external drive.  That is what I did at first also.  I would recommend moving your system drive Final Cut Pro X folders to a safe backup drive such as usb, etc then ejecting that drive.  Make sure they no longer exist on the system drive.  Then go to your external drive where you first copied them to and go into the Final Cut Projects folder. Then go into a folder that has the name of your project, or if you created "Folders" in FCP X to put your projects in then go into the folder that has the name of the folder you created within FCP X.  Within one of those will be a folder named after your project name you had assigned it in FCP X.  Inside that will be a file called CurrentVersion.fcpproject. Double click on that file, and Final Cut Project X will open with that project. In your Project Library window on the lower half of the display, over against the left you will see Macintosh HD, or whatever your system drive is called.  Under that will be the name of your external drive. Indented to the right slightly under your external drive will be the name of the project you have just loaded.  Just keep working in that one from now on without moving the old FCP X folders backing onto the system drive.  If you get some clips that are red meaning that FCP X can no longer find them, copy them from your original system drive or the Final Cut Events folder to the event name you had placed them in when you imported them into your project.  You can also simply find them and re-import them into FCP X and be done with it.  It has been my observation that you do not want to have two Final Cut Project or Events (or any of the other) FCP X folders on two drives that are active at the same time.  Best practice is to leave them off your system drive and put them on an external Firewire drive.  If you need to make a backup of them periodically, put a usb drive or another Firewire drive on your system WITHOUT GOING INTO FINAL CUT PRO X, and use Finder to simply copy the folders to the other drives as a backup ... then eject the backups.  You can then continue working in FCP X.  Sounds detailed, but the bottom line is FCP X does not seem to like two FCP X file systems on two attached drives at the same time.  At least that's the way it has seemed in my experience.  Hope this helps.
    stephen

  • I have several pdf files in my computer which are organized in folders. I want to transfer them to IBooks (in my Ipad) and keep the folder structure I use in my computer. Is it possible to do it? Do I need any other app?

    I have several pdf files in my computer which are organized in folders. I want to transfer them to IBooks (in my Ipad) and keep the folder structure I use in my computer. Is it possible to do it? Do I need any other app?

    By design, the organizer (and any other database management systems) is there to prevent you from duplicating your media files. The catalog management allows you to have the same image in different categories or albums. Duplication in different folders is to be absolutely avoided.
    The same image file can have multiple tags like 'family', 'vacations', 'birthdays' and be present in three different albums with the same names. On obvious advantage is less disk space. Another one with your present folder system is that if you edit one of your duplicates, the other ones are unchanged.
    I don't see an easy way to make your present folder structure simplified for the organizer ...

Maybe you are looking for

  • Getting lots of strange people on my account????

    hi  it's been a while that I get messages from strange people requesting adding me up . I am just so scared that I think my account has been hacked.One of these people called me the other day .please help me and tell how I can get rid of people. Than

  • Performance overhead

    Hi, I have a quick question. There is part in the project where we need to update information in SAP which we gather from the user. I am getting a series of name from user and updating it. For that I am using insert statement. If user tries modify th

  • HFM Role

    Hello - I'm looking for the definition of different HFM roles in shared services. I went through most of the HFM documents but couldn't find the definitions. Can you please guide me on this? Thanks in advance... Some of the role are: Advanced User De

  • Problema con nuova ram

    Ho installato nuova ram nel mio mac, ma a me pare che la nuova ram (2 x 2gb) sia molto più lenta dell'originale (1 x !gb). come posso fare un confronto più specifico? Grazie ciao

  • Faulty hard drives and recovery sets

    Regarding having a faulty hard drive (no recovery partition), if you and a friend have the same computer model you could buy a new hard drive (maybe 120GB) and clone the good one from one computer to use in the one that had a bad hard drive then make