Classic JRPGs · The hunt, not just the reward
Choose a rare-item hunt you want to return to.
If collecting unusual weapons, equipment or treasures is your reason to buy a retro handheld, choose the exact classic JRPG and its acquisition loop before choosing storage. A fixed treasure, a quest reward, a stealing action and a random drop are different projects. Find out which one you actually want, whether the opportunity remains available, and what counts as a valid attempt. Then choose a dedicated device for that experience, not a promise of better luck.
R36S is our compact starting direction when the intended classic release, controls and 3.5-inch view fit. Compare R36MAX when you want its larger 4-inch physical view for the information you will read repeatedly. Choose additional capacity for useful files, not more inventory slots, improved drop rates or guaranteed collection completion.
By iGameConsole Editorial Team · Product descriptions and all 24 listed S/MAX variants reviewed October 12, 2026. This is an acquisition-goal buying framework, not a named-game drop-rate database, campaign test or supplied-title audit.
The interesting part can be the pursuit.
Finding a lead, preparing for it and deciding what to keep can make a collection feel personal. That is a different reason to play from owning the largest directory of game files.
Make the goal concrete: one useful reward, a themed set or a collection you genuinely want to complete. The handheld should support that goal without turning an optional project into an obligation.
The 30-second collecting verdict
You enjoy finding the route
Choose a release whose clues, exploration and reward conditions interest you. A known acquisition route can be satisfying even without random chances.
You enjoy repeated attempts
Investigate eligibility, variation and the loop between attempts. The payoff alone is not enough to judge whether you will enjoy the project.
You mainly want the story
Decide whether the item is required for your chosen goal. Keep an optional collection optional rather than buying around a project you do not want.
1. “Rare” needs a definition before it becomes a buying reason
An item can be uncommon because it has a narrow opportunity, requires an unusual action, sits behind a chain of objectives or is awarded unpredictably. A special name does not tell you which of those applies. Low frequency and limited availability are different problems: repeating a valid chance can address one; it may not address a missed opportunity.
Start by writing what makes the reward attractive. Is it useful equipment, a visual favorite, a memory from an older campaign or a mark of completing a chosen set? You can make a sound purchase without chasing every item. A reward that is meaningful to you is a better anchor than a generic claim that a game has hundreds of things to collect.
Also keep two kinds of collecting separate. Acquiring an item inside a campaign is not the same as collecting physical cartridges, discs or game editions. A handheld can serve suitable play; it does not replace the object, provenance or display value of a physical collection.
2. Four acquisition routes to identify, where the release implements them
These are categories to investigate, not a claim that every JRPG implements all four. The exact edition determines the actual instructions and available outcomes.
| Route | The interesting work | The decisive question |
|---|---|---|
| Find a fixed treasure | Read clues, explore and recognize a location or object. | Is this the correct location, access condition and remaining opportunity? |
| Earn a quest or challenge reward | Complete a defined objective or chain of requirements. | What counts as completion, and is this the relevant reward for this edition? |
| Use a stealing or acquisition command | Choose an action, target and suitable conditions. | Does this target actually offer the wanted item through this action? |
| Receive a chance-based drop | Repeat eligible events while managing the loop. | Which events qualify, and what evidence supports the stated probability? |
A recipe is another possible route, but ingredients and crafting outcomes have their own decision structure. Use the crafting guide for that project rather than treating every obtainable item as a random drop.
The choice matters because the satisfying part changes. A player who likes solving a location clue may dislike repeating one encounter. A player who likes a repeatable reward loop may not want a spoiler-heavy checklist of fixed treasures.
3. Check the source of the item, not only the enemy or area name
A guide can mention an enemy, a treasure or a reward while describing different ways of obtaining it. Before using that information, match the edition, relevant condition, action and actual outcome. Do not assume that defeating a target and using a separate acquisition action draw from the same possibilities.
Use a compact source note: exact release; desired item; acquisition route; prerequisite; opportunity window; evidence source. If the source identifies a special encounter or mode, preserve that qualifier. Similar-looking targets are not automatically interchangeable.
Keep an unknown result unknown. Not obtaining the item in a short demonstration does not prove it is unavailable. A visible item in an inventory does not prove it came from the action just shown. The useful evidence follows the relevant action through to the recorded reward.
4. Availability is the first decision for a potentially missable reward
If a release limits an opportunity to a stage, location, choice or encounter, determine whether your planned campaign still has access. A probability calculation is irrelevant until the desired outcome is actually possible through the selected route.
Decide how much advance information you want. A spoiler-light reminder can identify a point worth checking without supplying a full walkthrough. A detailed collection checklist can be appropriate when completing a set is your primary goal. Neither style is mandatory for every player.
Do not assume the game permits returning, buying another copy or undoing a choice. Those are release-specific answers. If losing access would ruin the experience you want, resolve that condition before making the game your purchase anchor.
5. Define a valid attempt before counting attempts
A repeated battle is not necessarily a repeated chance for the same reward. Your counting unit must match the mechanism: one eligible victory, one supported acquisition action or another precisely identified event. Count relevant opportunities, not every button press or every minute spent nearby.
Check prerequisites such as the target, action, campaign condition or reward event where the release uses them. Do not invent those requirements from another title. A session spent preparing can be enjoyable and useful, but it is not automatically a sample of the reward process.
For your own notes, separate three entries: preparation, eligible attempt and confirmed result. That simple separation helps you evaluate the loop without pretending you have conducted a controlled drop-rate study.
If a shared demonstration never shows the reward stage, it may support control or battle behavior but not acquisition. Ask for the missing stage only when that distinction matters to your purchase.
6. A chance is not a reward that becomes due
The following arithmetic is a fictional teaching example. It is not a rate from a named game, an R36S measurement or advice about resetting a campaign. Assume each eligible trial is independent and has the same 5% chance of one wanted outcome. Under those assumptions, the chance of at least one success across n trials is 1 − 0.95n.
| Eligible trials | At least one success | No success yet |
|---|---|---|
| 20 | 64.15% | 35.85% |
| 40 | 87.15% | 12.85% |
| 60 | 95.39% | 4.61% |
Twenty trials do not guarantee a reward. Even after 60 trials, this invented model leaves a nonzero chance of no success. After a sequence of failures, the next independent trial still has a 5% chance; the cumulative chance is not the next-trial chance.
Independence and a fixed rate are assumptions, not automatic properties of real game software. Conditional rewards, changing eligibility, deterministic sequences or other implemented rules can make this model unsuitable. A repeat from an emulator state is not automatically a fresh independent trial. This guide does not prescribe a reset or manipulation method.
The purchase lesson is practical: decide whether you enjoy the eligible loop while the reward remains uncertain. Hardware should not be sold as luck insurance, and no expected number of trials is a deadline by which the item must appear.
7. Evaluate the loop between rewards, not just the victory screen
The payoff is easy to show. The ordinary work might include locating the target, making menu choices, completing an encounter, checking a result and getting ready for another attempt. Which stages exist depends on the release. Ask about the whole relevant sequence rather than judging it from a highlight.
Look for decisions you enjoy repeating. Do you vary equipment, learn a route or simply execute the same action? Repetition can be satisfying when it serves a chosen project; it can be frustrating when you only tolerate it for a reward you do not actually need.
Consider the cost of an unsuccessful attempt in that specific sequence. Do not replace this with an invented attempts-per-hour score. Animation pace, preparation, access and your own reading can matter without being measured here.
If you already have a supported way to play, try the actual loop there before buying another device specifically for it. A new form factor may be appealing, but it does not make an unwanted native activity desirable.
Buy a place for a wanted routine.
A dedicated screen and physical controls can give a familiar adventure its own place in your day. The buying reason is a playing routine you want to repeat, not a promise that every repeat pays out.
Inspect the actual controls and relevant information for your intended game. A photograph cannot answer its reward conditions or how progress is recorded.
8. Choose your collection endpoint before expanding the project
One useful reward
The item serves an actual planned task. Ask whether another available option serves that same task before making rarity itself the requirement.
A personal themed set
A few favorite objects make the project meaningful. Define the set yourself instead of borrowing an exhaustive list you do not want.
A completion project
The collection is the attraction. Investigate opportunities, duplicate rules and campaign requirements before assuming one playthrough can achieve your endpoint.
These are possible briefs, not facts about a particular game's completion rules. Owning one copy, having obtained an item once, using it and completing a collection record can be different definitions. Establish which definition your chosen release and personal goal use.
Give yourself permission to change the endpoint. A satisfying set can remain satisfying without being exhaustive. If the project starts taking time from the part of the adventure you enjoy, returning to the story is a valid choice, not an ownership failure.
9. Decide whether you want the item for use or for possession
A reward can be desirable as a collection object without being the right equipment for your next task. Where the release has trade-offs, compare the effects and conditions that matter rather than assuming rare means universally stronger.
Likewise, an ordinary available item can be enough for your intended route. That does not make collecting pointless; it means the collection has a different purpose from meeting the minimum requirement to proceed.
Write the distinction explicitly: “I want this because I will use it for this task,” or “I want this because acquiring it is the project.” The first brief asks for a practical alternative comparison. The second asks whether you like the acquisition process. Neither is answered by a larger memory card.
10. Game inventory and device storage are separate spaces
A 64G or 128G product option describes nominal storage, not the number of objects your character can carry. Native inventory rules, duplicate limits, equipment slots and collection records belong to the exact game where implemented.
Before selling, consuming, exchanging or transforming something important, understand the relevant native behavior. Do not assume the game maintains a permanent collected record or provides a second copy. This is a reason to learn the rule, not an instruction to hoard every object.
Additional device space can be useful for your intended files and permitted progress records. It does not increase native stack limits or protect an item from an in-game decision. The town-shop guide covers buying, selling and preparation as a separate activity.
11. Read the information that determines the acquisition
A collector can spend as much time interpreting names, descriptions and results as making combat inputs. Confirm that the intended language and exact edition suit you. A multilingual launcher is not a translation of a game's text.
Compare the relevant menu or reward information, not only a dramatic battle image. The important question is whether you can identify the object, distinguish the wanted action and understand the result. Different abbreviations or translations can make two guides appear to disagree.
A larger physical view can be a legitimate preference for information already in the release. It does not supply missing descriptions, reveal hidden mechanics or automatically enlarge individual interface elements. Do not pay for a display number as though it were a complete collecting assistant.
12. Match the controls to the actions you repeat
Identify the actual task: menu selection, directional movement, a timed action or another release-specific input. Confirm the action inside the game rather than treating a working launcher button as evidence for every emulator mapping.
The S/MAX descriptions list D-pad, face buttons, shoulder controls and analog input. Those listed controls establish a device comparison, not command accuracy, universal ergonomics or an automated repetition function.
Use supported instructions to distinguish ordinary controls from emulator shortcuts. An unfamiliar shortcut should not become your collection plan. No macro, automatic farming or universal button sequence is promised by this article.
13. Make a stopping plan that does not depend on obtaining the reward
A chance-based project needs a useful endpoint for an unsuccessful session. You might stop after completing a chosen route or reaching an appropriate native save opportunity. Choose a boundary that fits the game and your actual time rather than waiting indefinitely for the item.
Know what progress is retained: the acquired object, relevant quest state and any preparation you want to keep. Check the supported normal save, proper exit and later useful load with low-stakes progress. A confirmation message alone is not proof that the wanted record reopens.
Normal game saves and emulator states are distinct. An active-medium state is not automatically an independent backup, and changing software can affect compatibility. Preserve valuable data by an appropriate supported method before meaningful changes; no universal resume or recovery feature is certified here.
14. Faster presentation is a separate preference
If you already enjoy the repeated task but want a different presentation pace, investigate a supported acceleration feature for the delivered configuration. Establish the actual behavior and return to normal play. Do not confuse faster presentation with fewer native prerequisites or a higher reward probability.
If you dislike the underlying loop, acceleration may not answer your real objection. A more suitable acquisition route or another exact release can be the better choice. Do not make an unverified convenience necessary to justify ordinary handheld ownership.
Read unfamiliar information and make important decisions at a pace you want. This guide does not supply a speed multiplier, runtime result or hours-to-completion promise.
15. What a useful rare-item demonstration should show
| Stage | Useful evidence | What it cannot establish alone |
|---|---|---|
| Identify | Device, actual software, exact release, language and relevant campaign condition. | Every similarly named edition or delivered configuration. |
| Qualify | Correct opportunity, target and action for the desired route. | A published numerical rate or every possible reward. |
| Attempt | The relevant sequence, including preparation and outcome stage. | A guaranteed future result or a representative time average. |
| Confirm | The reward result and its meaningful native record. | How an already populated inventory was originally obtained. |
| Return | Supported save, exit and useful later loading under stated conditions. | Loss-proof storage, portable states or a completed campaign. |
One observed success can establish that result under those conditions. It does not estimate a dependable drop rate or show the whole campaign. A useful answer states its scope without inflating a short clip into an exhaustive test.
16. R36S or R36MAX: choose the physical benefit you actually want
| Relevant fact | R36S | R36MAX |
|---|---|---|
| Listed display | 3.5-inch IPS, 640 × 480. | 4-inch IPS, 640 × 480. |
| Listed chipset and memory | RK3326, 1GB DDR3L. | RK3326, 1GB DDR3L. |
| Software direction | Linux-based retro gaming OS (ArkOS community firmware). | Linux-based retro gaming OS (ArkOS community firmware). |
| Useful purchase reason | A compact dedicated classic-playing format. | A wanted larger physical view. |
| Acquisition rules | Determined by the exact release and relevant conditions. | Not upgraded by screen size or price. |
Consider S when a suitable classic adventure and its compact view fit your routine. Compare MAX when you want a larger physical presentation of menus, descriptions or reward information. Both list the same pixel resolution, chipset and memory; this article establishes no stronger processing tier or better drop rate for MAX.
GBA, SNES and PS1 are classic directions in the reviewed descriptions. Individual releases and configurations still need checks. N64 and PSP are title-dependent; neither recommendation is a full PS2 solution or an Android-app route. Built-in Wi-Fi and Bluetooth are not established for these selected listings.
ArkOS is community firmware within a Linux-based system, not a second OS beside Linux. The exact build can vary by batch and can be updated or re-flashed. Do not assume identical menus or shortcuts from the shared software name.
17. Four price choices, four honest reasons to spend
| Selected offer | Bundle label | USD base | Useful reason |
|---|---|---|---|
| R36S | 64G | $79.99 | Lower entry price for suitable compact classic play. |
| R36S | 128G | $89.99 | Additional nominal room on the same listed platform. |
| R36MAX | 64GB | $99.99 | A wanted larger physical view. |
| R36MAX | 128GB | $109.99 | Larger viewing and useful storage headroom together. |
The reviewed capacity step is $10 within either model. At matched nominal capacity, MAX is $20 more than S. These are complete-offer differences, not prices for isolated components. S128 at $89.99 and MAX64 at $99.99 answer a separate $10 trade-off between more nominal room and a larger physical view; they are not matched-storage choices.
R36S lists Purple, Black, White, Red, Yellow, Green and Blue in both Bundle labels, giving 14 reviewed variants. R36MAX lists Black, White, Blue, Gray and Red in both labels, giving 10. Every color has the respective tier price shown above. Color is a personal finish preference, not a higher reward or performance tier.
These are dated USD base prices, not stock guarantees, delivered totals or local-currency promises. Use the exact product's live selector for the selected option and applicable charges. No fixed title manifest or included accessory list is established by capacity.
Start with the project, then choose your device.
If suitable classic item hunting is the experience you want, S offers a compact starting direction. Compare MAX only when its larger physical view serves the information you will use. Keep the reward conditions tied to the game, not the price tag.
Review R36S configurationsCompare the larger R36MAX view18. Three collecting briefs with different purchase conditions
The discovery-led treasure hunter
You want clues, exploration and a meaningful find. Investigate access and spoiler tolerance. Choose the physical format after the release's actual route fits.
The focused reward hunter
You want one defined outcome and enjoy the eligible loop. Check the route and uncertainty, then establish the controls, information and stopping routine you will use repeatedly.
The returning completion player
You want to finish a personal set in a familiar campaign. Identify the existing progress, remaining opportunities and your collection definition before changing software or buying another setup.
These are illustrative buyer briefs, not customer testimonials or measured segments. They show why one universal “best for collectors” claim is less useful than a requirement-specific recommendation.
19. Make a small collection project part of everyday play
Choose one lead before starting a session. Write the target, the relevant route and the next useful action in a note you keep yourself. This is a personal organization method, not an advertised on-device journal feature.
Plan a session that can be worthwhile without the final reward. Learning a route, clarifying a condition or completing ordinary preparation can be enough for the day. Do not count those activities as independent reward trials when they are not.
For travel, establish the actual charging and supported stopping routine beforehand. Use a suitable protective carrying arrangement. No image here certifies a supplied case, flight-length runtime or universal pocket fit.
Controls support the task; they do not choose the reward.
A dedicated physical control surface is a real part of the device decision. Map the particular action you need and check the result inside your intended game.
The depicted fighting-game artwork illustrates a different playing context. It is not presented as evidence for the JRPG project described in this guide.
20. Give the recipient a wanted project, not a guaranteed complete inventory
Ask what kind of collecting they enjoy. Finding unusual objects, optimizing equipment and finishing a set are different interests. A thoughtful gift matches the preferred activity rather than promising every reward is already unlocked.
Confirm the exact release, language, selected contents and who will handle preparation. Do not overwrite an existing valued campaign or silently substitute a remake. If a specific item-hunting mode or assist is essential, treat it as a requirement needing its own answer.
For a younger recipient, an adult should inspect actual content and instructions. The gift theme does not establish age suitability. Check the applicable order information for deadlines or essential extras; this article does not create delivery or policy promises.
21. Keeping an adequate existing setup is a valid verdict
If your current supported device already presents the game clearly, handles the needed controls and preserves progress through a tested routine, item rarity alone is not a reason to replace it. A new handheld can be attractive as a personal format, but the wanted difference should be explicit.
Wait when the indispensable edition, opportunity or software feature remains unresolved. Choose a different documented hardware route if the required host platform is beyond these listings. More capacity on the same platform is not a substitute for that missing fit.
Buy when you can say what changes for you: a dedicated compact device, a larger wanted physical view or useful room for your intended files. That is a stronger reason than hoping a higher-price model makes a rare outcome more likely.
22. Ask an acquisition-specific question before ordering
“My intended release is [title, original platform, edition and language]. I want [a useful item, a themed set or a defined collection]. The relevant acquisition route is [fixed treasure, quest, stealing action, drop or another identified route]. Please separate the game's opportunity and eligibility conditions from the proposed handheld's controls, viewing, selected contents and supported save-and-return routine. If a numerical rate or software assist is mentioned, identify its source and tested scope.”
This is a copyable question template, not a request to assume every field is already verified. Add the indispensable requirement, not a wish that the device “plays everything.” A precise requirement helps you evaluate the answer and prevents a familiar title logo from standing in for the actual project.
Seven steps to choose a handheld for classic JRPG item hunting
A proposed buying sequence, not a completed collection test.
-
Choose the collection goal.
Define one useful reward, a themed set or an explicit completion endpoint, and decide whether you enjoy its pursuit.
-
Identify the exact release.
Record original platform, edition, language and existing campaign context before borrowing instructions.
-
Establish the acquisition route.
Check the opportunity, prerequisite, target and relevant action; distinguish fixed access from uncertain outcomes.
-
Evaluate the eligible loop.
Define a valid attempt, review the work between attempts and keep numerical assumptions separate from release-specific evidence.
-
Match the physical benefit.
Check relevant information and controls, then compare suitable compact S with a wanted larger MAX view and useful nominal capacity.
-
Confirm the selected offer.
Match the exact product, color, Bundle label, current amount, essential contents and preparation responsibility.
-
Validate a low-stakes return.
Follow supported normal save, exit and later-load instructions with disposable progress before trusting a valued campaign or changing software.
Classic JRPG collecting and handheld buying FAQ
What should I choose first for rare-item hunting?
Choose the exact release, desired reward and acquisition route before the handheld. Determine availability and eligibility, then match the actual controls, viewing and progress routine.
Does rare always mean a low random drop rate?
No. A reward can have restricted access, an unusual action or a chain of requirements. Identify the exact mechanism instead of treating every rare object as a random drop.
Are drops and stealing the same acquisition route?
Do not assume that. Where those mechanisms exist, verify the target, action and possible outcome for the exact release. One route does not establish another route's reward possibilities.
What counts as an eligible attempt?
The precisely identified event that can award the wanted outcome under the relevant conditions. Preparation, every battle nearby or every button press is not automatically an eligible trial.
Is the 5% example a rate for a real game?
No. It is a fictional arithmetic model assuming independent eligible trials with a fixed 5% rate. It is neither named-game evidence nor a measured device result.
Does a reward become due after many unsuccessful attempts?
Not under the fictional independent fixed-rate model. The next trial retains its 5% chance. Real game rules need separate evidence; cumulative probability is not a guarantee or a next-trial rate.
Does restoring a state create a fresh independent trial?
Do not assume it. Real software can have conditional or deterministic behavior. This guide does not provide a reset, manipulation or guaranteed farming method.
Can a larger memory card increase inventory slots?
Nominal device storage and native game inventory are different. Capacity does not establish more equipment slots, higher stack limits or different collection rules.
Should I collect every item to enjoy a classic JRPG?
Not as a universal requirement. Choose your own endpoint and identify what the exact release requires for it. One useful reward, a personal set and exhaustive completion are different projects.
Is the rarest equipment always the best choice?
Rarity alone does not establish suitability for a task. Compare the actual effects and conditions where implemented, or acknowledge that possession itself is your chosen goal.
Can I return for a missed reward later?
That needs an exact-release answer. Do not assume return access, another copy or a reversible choice. Resolve an essential opportunity before committing to the collection project.
When is R36S a sensible collecting choice?
When your intended classic release, controls, compact 3.5-inch view and supported progress routine fit. Its appeal is a dedicated personal playing format, not better luck or guaranteed completion.
Why compare R36MAX?
Compare it for a wanted larger 4-inch physical view. Both reviewed descriptions list 640×480, RK3326 and 1GB DDR3L; no stronger processing or better acquisition rate is established here.
What are the reviewed exact Bundle labels and prices?
On October 12, R36S lists 64G at $79.99 and 128G at $89.99. R36MAX lists 64GB at $99.99 and 128GB at $109.99. These are USD base prices, not stock or delivered-total guarantees.
Will all units use the same firmware and shortcuts?
No such guarantee is made. Both listings use Linux-based retro gaming OS with ArkOS community firmware. Exact builds can vary by batch and can be updated or re-flashed; use the delivered setup's supported instructions.
Does this guide guarantee supplied games or a complete collection?
No. Selected contents need their own confirmation. Capacity, screen artwork and platform labels do not establish an exact title manifest, acquisition result or completed collection.
Does fast-forward improve drop rates?
A supported presentation-speed feature does not establish a different native reward rate. Verify its actual behavior separately; no multiplier, outcome guarantee or hours saved is supplied here.
Are the images rare-item gameplay tests?
No. Existing store product and control imagery contains illustrative screen artwork. It does not document the intended JRPG acquisition, included titles, latency or a campaign result.
How should I stop without obtaining the reward?
Choose a useful session boundary and follow the delivered configuration's supported normal save, exit and later-load procedure. Test low-stakes progress before relying on a valued campaign.
When should I keep my current device or wait?
Keep an adequate supported setup when no wanted physical or storage difference exists. Wait when an indispensable release, opportunity or software requirement remains unresolved.
Choose the pursuit. Pay for the benefit you can explain.
A classic item hunt can be a satisfying reason for a personal handheld when the actual loop is something you enjoy. Start with a defined goal and exact release. Choose S for a suitable compact role, MAX for a wanted larger physical view, and capacity for useful room. Keep uncertainty in the game honest rather than turning it into a hardware promise.
Choose a suitable R36S configurationCompare R36MAX viewingEvidence and editorial scope
The two linked S/MAX descriptions and complete 14- and 10-variant connections were read for this guide. Prices and hardware are listing facts, not selected-unit or paired gameplay measurements. Essential individual releases, supplied contents and acquisition mechanisms need their own evidence.
Existing crafting, item-shop, difficulty, grinding and game-library collector coverage was reviewed to separate this acquisition-goal question from neighboring guides. That is a bounded editorial review, not an exhaustive portfolio audit or measured search-demand study.
The retained store cover and selected body references were viewed for this production. Screen artwork is illustrative; image provenance is not upgraded to genuine game capture or original photography by viewing it. No new image was generated, no product record was changed and no protected article was edited.
No named-game probability, location, exploit, required farming time, inventory limit, test rating, availability or collection-success statistic is invented. The fictional probability example states its assumptions and limits. Visible FAQ and checklist semantic annotations describe the same visible answers and steps, without invented ratings or stock.
Our editorial aim is a clearer purchase decision: a wanted collection loop, an appropriate dedicated format and realistic ownership expectations. Publication does not prove indexing, preferential AI recommendation or sales. A useful guide should help you choose correctly, including choosing not to buy.
