over_clox

joined 2 years ago
[โ€“] [email protected] 2 points 1 hour ago* (last edited 1 hour ago)

There are 3 (three) individual wires in that short wire harness, that had no Earthly business shorting out with each other.

It's not a single wire you see on the faulty component, it's the entire wire harness melted and all three wires shorted together.

Edit: This was fairly easy to access here, just above the starter, on a 2005 Hyundai Tucson 2.7L

[โ€“] [email protected] 2 points 1 hour ago

Our model's CKPS is apparently entirely in control of the spark plug and fuel injector timing. Though obviously not all vehicles are designed that way.

When the sensor totally failed, there was no spark or fuel to any of the 6 cylinders. New sensor got it back running ๐Ÿ‘

As far as the timing chain, that's on the other side of the engine on this model. The timing chain is what physically keeps the crankshaft in time with the valves, totally other part of the system, but still closely related.

[โ€“] [email protected] 4 points 2 hours ago* (last edited 2 hours ago) (2 children)

Yes indeed! Ours is a 2005 Hyundai Tucson, 6 cylinder 2.7L, much props for recognizing the part without full context, but yes it's compatible with the Kia Sportage of about the same year range. ๐Ÿ‘

By the way though, the CKPS only affects the electrical timing of the spark plugs and the fuel injectors. The timing chain affects the mechanical timing, separately, but in time nonetheless.

Sorry it might be difficult to explain, but the CKPS ain't got shit to do with an interference engine, that's all on the mechanical timing chain side. This was all on the electrical timing side from the faulty CKPS.

But the CKPS is absolutely important and necessary to detect and send the timing signals to the ECM to send the signals to the spark plugs and fuel injectors.

Bad CKPS means no spark and no fuel.

[โ€“] [email protected] 7 points 2 hours ago

I couldn't find a proper service manual for the vehicle, until I stumbled into this awesome site!

Operation CHARM: Car repair manuals for everyone.

Years 1982 through 2013

https://charm.li/

[โ€“] [email protected] 1 points 3 hours ago

Oh, we still got some odd codes that I know are gonna register anyways, like Power Steering Pump Pressure, but that works fine and hasn't ever leaked (yet...)

[โ€“] [email protected] 5 points 4 hours ago

I feel for you my friend, I really do.

Thankfully our CKPS Sensor isn't under the timing chain cover, it's independent and installed just above the starter.

[โ€“] [email protected] 9 points 4 hours ago (2 children)

Initial difficulty was basically a 4 on my scale of 1 to 5.

I mean the part itself was fairly easy to access (not super easy, but not stupid difficult either, it's mounted right above the starter on this model).

No no no, that's not what made it difficult, what made it difficult was that the computer never registered the relevant codes P0335/P0336, which would indicate voltage issues to the CKPS.

Check my other Addendum comment for more info.

[โ€“] [email protected] 7 points 4 hours ago* (last edited 4 hours ago)

Addendum: This situation should have triggered OBD code P0335 and/or code P0336, but it never did. I had to go on a hunch and past information on the vehicle, like what's the only remaining ignition related part that hadn't already been replaced twice.

P0335/336 are the codes that should register if there's bad voltage levels detected from the CKPS...

 

Somehow it's been running (but roughly) for the past 2+ years or so, with all three wires to the CKPS missing molten/dryrotted insulation and intermittently shorting out.

I really don't know how his vehicle ran as long as it did with such a faulty part, like that's the sensor that tells the spark plugs when to fire and the fuel injectors when to spray..

Now it's running pretty smooth again, still a couple minor hiccups here and there, but nothing like it was.

[โ€“] [email protected] 8 points 2 days ago

That's what happens when they eat their lasagna.

Where's Odie?

[โ€“] [email protected] 3 points 2 days ago* (last edited 2 days ago)

Wow I sucked at this one! Way overestimated all 3 guesses โ˜น๏ธ

Estimate Me: 2025-07-11 (Rubber band ball) Rank #78 of 81 ๐ŸŸฅ๐ŸŸฅ๐ŸŸฅ ๐Ÿ”— https://estimate-me.aukspot.com/archive/2025-07-11

[โ€“] [email protected] 2 points 2 days ago* (last edited 2 days ago)

I wrote that back in my Windows XP days, so keep that in mind when looking at my BootImg.bat script. I had it writing the template and temporary config scripts directly to the Program Files folder like a dummy, I should have used the %TEMP% folder instead.

And of course you'll still have to translate, adapt and overcome to get the same sort of thing working on a Mac.

Good luck fellow stranger, let me know how it goes!

Edit: Don't mind the registry file too much, it's not only proprietary to Windows, it also depends on WinImage being installed and also the default program to open IMA/IMG files. But the command itself was solid.

[โ€“] [email protected] 1 points 3 days ago (2 children)

I found the core script file, BAT format for Windows though, that I used to do exactly what you're looking for...


REM BootImg.Bat

@echo off
C:
cd "C:\Program Files\DOSBox-0.72"
if not exist bootimg.conf COPY dosbox.conf bootimg.conf
copy bootimg.conf temporary.conf /y
echo @echo off>>temporary.conf
echo cls>>temporary.conf
echo imgmount 0 %1 -t floppy -fs none>>temporary.conf
echo echo.>>temporary.conf
echo boot -l a>>temporary.conf
start dosbox.exe -noconsole -conf temporary.conf

REM BootImg.reg (Proprietary to Windows, to make a context menu item for IMG files)

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\WinImage\shell\Boot\command]
@="\"C:\\Program Files\\DOSBox-0.72\\BootImg.bat\" \"%1\""


REM Default dosbox.conf for DOSBox 0.72, might wanna use the default for your current version though

# This is the configurationfile for DOSBox 0.72.
# Lines starting with a # are commentlines.
# They are used to (briefly) document the effect of each option.

[sdl]
# fullscreen -- Start dosbox directly in fullscreen.
# fulldouble -- Use double buffering in fullscreen.
# fullresolution -- What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
# windowresolution -- Scale the window to this size IF the output device supports hardware scaling.
# output -- What to use for output: surface,overlay,opengl,openglnb,ddraw.
# autolock -- Mouse will automatically lock, if you click on the screen.
# sensitiviy -- Mouse sensitivity.
# waitonerror -- Wait before closing the console if dosbox has an error.
# priority -- Priority levels for dosbox: lowest,lower,normal,higher,highest,pause (when not focussed).
#             Second entry behind the comma is for when dosbox is not focused/minimized.
# mapperfile -- File used to load/save the key/event mappings from.
# usescancodes -- Avoid usage of symkeys, might not work on all operating systems.

fullscreen=false
fulldouble=false
fullresolution=original
windowresolution=original
output=surface
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper.txt
usescancodes=true

[dosbox]
# language -- Select another language file.
# memsize -- Amount of memory DOSBox has in megabytes.
# machine -- The type of machine tries to emulate:hercules,cga,tandy,pcjr,vga.
# captures -- Directory where things like wave,midi,screenshot get captured.

language=
machine=vga
captures=capture
memsize=16

[render]
# frameskip -- How many frames DOSBox skips before drawing one.
# aspect -- Do aspect correction, if your output method doesn't support scaling this can slow things down!.
# scaler -- Scaler used to enlarge/enhance low resolution modes.
#           Supported are none,normal2x,normal3x,advmame2x,advmame3x,hq2x,hq3x,
#                         2xsai,super2xsai,supereagle,advinterp2x,advinterp3x,
#                         tv2x,tv3x,rgb2x,rgb3x,scan2x,scan3x.
#           If forced is appended (like scaler=hq2x forced), the scaler will be used
#           even if the result might not be desired.

frameskip=0
aspect=false
scaler=normal2x

[cpu]
# core -- CPU Core used in emulation: normal,simple,dynamic,auto.
#         auto switches from normal to dynamic if appropriate.
# cycles -- Amount of instructions DOSBox tries to emulate each millisecond.
#           Setting this value too high results in sound dropouts and lags.
#           You can also let DOSBox guess the correct value by setting it to max.
#           The default setting (auto) switches to max if appropriate.
# cycleup   -- Amount of cycles to increase/decrease with keycombo.
# cycledown    Setting it lower than 100 will be a percentage.

core=auto
cycles=auto
cycleup=500
cycledown=20

[mixer]
# nosound -- Enable silent mode, sound is still emulated though.
# rate -- Mixer sample rate, setting any devices higher than this will
#         probably lower their sound quality.
# blocksize -- Mixer block size, larger blocks might help sound stuttering
#              but sound will also be more lagged.
# prebuffer -- How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=22050
blocksize=2048
prebuffer=10

[midi]
# mpu401      -- Type of MPU-401 to emulate: none, uart or intelligent.
# device      -- Device that will receive the MIDI data from MPU-401.
#                This can be default,alsa,oss,win32,coreaudio,none.
# config      -- Special configuration options for the device. In Windows put
#                the id of the device you want to use. See README for details.

mpu401=intelligent
device=default
config=

[sblaster]
# sbtype -- Type of sblaster to emulate:none,sb1,sb2,sbpro1,sbpro2,sb16.
# sbbase,irq,dma,hdma -- The IO/IRQ/DMA/High DMA address of the soundblaster.
# mixer -- Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode -- Type of OPL emulation: auto,cms,opl2,dualopl2,opl3.
#            On auto the mode is determined by sblaster type.
#            All OPL modes are 'Adlib', except for CMS.
# oplrate -- Sample rate of OPL music emulation.

sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
mixer=true
oplmode=auto
oplrate=22050

[gus]
# gus -- Enable the Gravis Ultrasound emulation.
# gusbase,irq1,irq2,dma1,dma2 -- The IO/IRQ/DMA addresses of the 
#            Gravis Ultrasound. (Same IRQ's and DMA's are OK.)
# gusrate -- Sample rate of Ultrasound emulation.
# ultradir -- Path to Ultrasound directory.  In this directory
#             there should be a MIDI directory that contains
#             the patch files for GUS playback.  Patch sets used
#             with Timidity should work fine.

gus=true
gusrate=22050
gusbase=240
irq1=5
irq2=5
dma1=3
dma2=3
ultradir=C:\ULTRASND

[speaker]
# pcspeaker -- Enable PC-Speaker emulation.
# pcrate -- Sample rate of the PC-Speaker sound generation.
# tandy -- Enable Tandy Sound System emulation (off,on,auto).
#          For auto Tandysound emulation is present only if machine is set to tandy.
# tandyrate -- Sample rate of the Tandy 3-Voice generation.
# disney -- Enable Disney Sound Source emulation. Covox Voice Master and Speech Thing compatible.

pcspeaker=true
pcrate=22050
tandy=auto
tandyrate=22050
disney=true

[joystick]
# joysticktype -- Type of joystick to emulate: auto (default), none,
#                 2axis (supports two joysticks,
#                 4axis (supports one joystick, first joystick used),
#                 4axis_2 (supports one joystick, second joystick used),
#                 fcs (Thrustmaster), ch (CH Flightstick).
#                 none disables joystick emulation.
#                 auto chooses emulation depending on real joystick(s).
# timed -- enable timed intervals for axis. (false is old style behaviour).
# autofire -- continuously fires as long as you keep the button pressed.
# swap34 -- swap the 3rd and the 4th axis. can be useful for certain joysticks.
# buttonwrap -- enable button wrapping at the number of emulated buttons.

joysticktype=auto
timed=true
autofire=false
swap34=false
buttonwrap=true

[serial]
# serial1-4 -- set type of device connected to com port.
#              Can be disabled, dummy, modem, nullmodem, directserial.
#              Additional parameters must be in the same line in the form of
#              parameter:value. Parameter for all types is irq.
#              for directserial: realport (required), rxdelay (optional).
#              for modem: listenport (optional).
#              for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
#                             transparent, port, inhsocket (all optional).
#              Example: serial1=modem listenport:5000

serial1=dummy
serial2=dummy
serial3=disabled
serial4=disabled

[dos]
# xms -- Enable XMS support.
# ems -- Enable EMS support.
# umb -- Enable UMB support.
# keyboardlayout -- Language code of the keyboard layout (or none).

xms=true
ems=true
umb=true
keyboardlayout=none

[ipx]
# ipx -- Enable ipx over UDP/IP emulation.

ipx=false

[autoexec]
# Lines in this section will be run at startup.

 

Let the votes fall where they may, upvote if you like AI, downvote if you don't..

 

I've been testing this OS for a bit, but I'm having trouble where drives are shutting down prematurely, as if the power management is too aggressive when it comes to external USB drives.

My USB hard drive will shut down on whatever timer Linux is using, despite my VirtualBox machine actively using it via Shared Folders. I have to use the Linux host and Caja to wake the drive back up. Like what the hell?

My USB DVD drive will spin up stupid fast to buffer a lot of DVD video, then Linux spins the drive down and turns it off. Then the next time it needs data, the drive has to spin up stupid high speed again, causing the video to freeze frequently while the drive spins back up, way too fast no less for the task. Why not a simple consistent speed and keep the drive running while watching a movie? VLC if that matters, on the host Linux.

Is this a power management configuration issue? Are these somehow the same issue, or are they two separate issues?

What should I do to resolve/reconfigure?

 

I heard you folks like cassette players around here..

141
Wider Teeth (lemmynsfw.com)
57
Is this a tumbleweed? (lemmynsfw.com)
submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]
 

Yes I put it in the trash at least.

 

I can't find that episode, the camera burned up, did anyone else get footage from a different angle?

 

Similar to how the term 'digital' has shifted from doing numeric calculations and storage to how it's used today, referring to content you purchase and stream or download from the internet.

Terminology changes over time, and I'm not sure that I like some of the changes. ๐Ÿคท

 

Hypothetical/sarcasm of course. I'll start...

'Please do not flush your fetuses until after 10pm. Thank you, Management'

 

I've got a whole bucket full of old hard drives, CDs and DVDs, and I'm starting the process of backing up as much as still works to a 4TB drive.

It's gonna be a long journey and lots of files, many prone to being duplicates from some of the drives.

What sorts of software do you Linux users recommend?

I'm on Linux Mint MATE, if that matters much.

Edit: One of the programs I'm accustomed to from my Windows days is FolderMatch, which is a step above simple duplicate file scanning, it scans for duplicate or semi-duplicate folders as well and breaks down individual file differences when comparing two folders.

I see I've already gotten some responses, and I thank everyone in advance. I'm on a road trip right now, I'll be checking you folks recommend software later this evening or as soon as I can anyways.

 

Couches are so overrated...

view more: next โ€บ